>> For arguments sake lets say it is, although I turned journaling on last week >> so I would have thought it would have done its thing by now, unless I was to >> forcefully do something I didn't.
The Last Backup Completion Date of the file space must be set on the server, and the backup must have been completed while the file system was actively being journaled. Note that some backup commands which have the effect of backing up the entire file system don't update this date on the server. For instance, dsmc incr c:\ -subdir=yes and dsmc incr c:\*.* -subdir=yes will not update the completion date, but dsmc incr c: will. Issuing the command dsmc query filespace will display this date (it will be all zero's if it isn't set). As long as the full backup completed while the file system was being journaled and the next backup should be journal based provide that the back up is being done to the same server. Another possibility is that the file system is generating more change activity than the specified notify buffer can handle. If this is the case the buffer overflows and the journal will be invalidated (if this is the case you should see messages in jbberror.log and/or the nt application eventlog). If this is happening you may want to increase the size of the notify buffer via the NotifyBufferSize setting. Please continue to post questions or email me directly if you continue to have problems. Pete Tanenhaus Tivoli Storage Solutions Software Development email: [EMAIL PROTECTED] tieline: 320.8778, external: 607.754.4213 "Those who refuse to challenge authority are condemned to conform to it" ---------------------- Forwarded by Pete Tanenhaus/San Jose/IBM on 11/02/2002 01:00 PM --------------------------- "Gill, Geoffrey L." <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 10/31/2002 01:50:00 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: Subject: Re: Journaling Again Andy, A few comments; > 1) Was this the first incremental backup you ran after turning on > journaling? If so, then this is normal: the first backup will be a full > incremental (not to be confused with full backup) so that the journal > database(s) and server can be synched. Or did you do anything else (like > reboot) that may have caused the journal to require resynchronization? For arguments sake lets say it is, although I turned journaling on last week so I would have thought it would have done its thing by now, unless I was to forcefully do something I didn't. > 2) Do you have all desired drives configured to use journaled backup, via > the JournaledFileSystems parameter? What does your tsmjbbd.ini file look > like? Initially I did the largest drive only but went back in today and changed it to all drives. Here is what is active in the file. [JournalSettings] Nlsrepos=dscameng.txt Errorlog=jbberror.log JournalDir=E:\Program Files\Tivoli\TSM\baclient [JournalExcludeList] %SystemRoot%\System32\Config\* %SystemDrive%\Adsm.Sys\* %TEMP%\* %TMP%\* %USERPROFILE\*\index.dat *:\pagefile.sys *:\*.crmlog *:\hiberfil.sys %SystemRoot%\csc\* %SystemRoot%\System32\DTCLog\MSDTC.LOG %SystemRoot%\netlogon.chg %SystemRoot%\schedlgu.txt %SystemRoot%\registration\*.clb %WINDIR%\debug\* %SystemDrive%\Documents and Settings\NetShowServices\ntuser.dat %SystemDrive%\Documents and Settings\NetShowServices\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat %USERPROFILE%\ntuser.dat %USERPROFILE%\Local Settings\Application Data\Microsoft\Windows\UsrClass.dat [JournaledFileSystemSettings] JournaledFileSystems=C: E: G: JournalDBSize=0x00000000 NotifyFilter=0x0000015b NotifyBufferSize=0x00100000 PreserveDBOnExit=1 [JournaledFileSystemSettings.E:\] JournalDBSize=0x00000000 [JournaledFileSystemSettings.G:\] JournalDBSize=0x00000000 [JournaledFileSystemSettings.C:\] JournalDBSize=0x00000000 Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154