In Version 5.1, a new parameter was introduced in the tsmjbbd.ini file named PreserveDbOnExit . If this is set to a value of 1, then the journal is preserved across journal service restarts and reboots. It defaults to 0, which means invalidate the journal across restarts and reboots.
At 12:14 PM 10/31/2002 -0600, you wrote:
If you stop and restart the service, then tonight's backup will be a full incremental. The journal service has to be running continuously between 2 backups or TSM will always default to a full incremental. Ryan Miller Principal Financial Group Tivoli Certified Consultant Tivoli Storage Manager v4.1 -----Original Message----- From: Gill, Geoffrey L. [mailto:GEOFFREY.L.GILL@;SAIC.COM] Sent: Thursday, October 31, 2002 11:57 AM To: [EMAIL PROTECTED] Subject: Re: Journaling Again > 1. First of all, look in the dsmsched.log file and look to see if > you have the message: > > Using journal for '\\xxx-yyyyyyyy\c$' It's not there but the service is started. > If you see this message, a journaled backup has taken place for > that filespace. You should see this message > at the start of the backup. > > 2. Verify that the journal size is adequate. If you see a message > like the following in the jbberror.log, your journal size (specified by > parameter JournalDBSize in tsmjbbd.ini) is set too low. If you take the > default (as specified by Pete Tanenhaus > in previous posts as a recommendation) you should not have this problem. This is set to the default and there is no error message in this log I guess I'll stop and restart the service and see what kind of reports I get tonight. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
Dave Canan IBM Advanced Technical Support [EMAIL PROTECTED]
