Thanks for your response. Jounaled backups appear to be a service needed when the backup window is restricted (better than a partial backup but not as comprehensive as an incremental) . This could be a reason to move to 4.2. I included the following section from the TSM for Windows Using BA Client for others to get a feel for what it does.
If you install the journal engine service and it is running, then by default the incremental command performs a journal-based incremental backup on any journaled file systems. Tivoli Storage Manager does not use the journaling facility inherent in Windows NTFS 5 file systems or any other journaled file system. The journal engine service records changes to an object or its attributes in a journal database. During a journal-based backup, the client obtains a list of files that are eligible for backup from the journal database. Journal-based backup can increase backup performance because the client does not scan the local file system or contact the server to determine which files to process. Journal-based backup also reduces network traffic between the client and server. Tivoli Storage Manager filters the list based on the current include-exclude list and processes, expires, and updates the resulting files according to policy constraints, such as serialization. You can use the copy frequency attribute during a traditional full incremental backup. However, Tivoli Storage Manager ignores this management class attribute during a journal-based backup. The journal engine service does not record changes in specific system files, such as pagefile, registry, etc., in the journal. Therefore, journal-based backup will not back up these files. See the journal service configuration file tsmjbbd.ini in the Tivoli Storage Manager installation directory for excluded system files. See the Appendix in Tivoli Storage Manager Installing the Clients, SH26-4119, for more information about the journal service configuration file tsmjbbd.ini. To support journal-based backup, you must install the journaling engine service background process as a service on Windows NT and 2000 using the dsmcutil command or the client GUI setup wizard. See Tivoli Storage Manager Installing the Clients, SH26-4119, for more information about using the dsmcutil command to install the journal engine service. To install and configure this service using the client GUI setup wizard, perform the following steps: Select the Utilities menu> Setup Wizard item. Select the Help me configure the TSM Journal Engine checkbox. Follow the instructions on the screen to configure and use the journal engine. See Incremental for more information about journal-based backup. Notes: The Journal Service is not supported in a Microsoft Cluster Server environment. Only one Journal Service may be installed on a machine and the Journal Service cannot dynamically start or stop monitoring shared disks. When using anti-virus software, there are limitations to journal-based backup. Refer to the README file that is shipped on the product installation media for more information. Al ----- Original Message ----- From: "Malbrough, Demetrius" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, December 21, 2001 3:19 PM Subject: Re: 4.2.1.15 NT Journal Service FILLING EventLog > First of all, you can start by looking in the following: > > Tivoli Storage Manager for Windows Using the Backup-Archive Client 4.2 > http://www.tivoli.com/support/public/Prodman/public_manuals/td/TD_PROD_LIST. > html > > Tivoli Storage Manager (TSM)README WINDOWS NT/WINDOWS 2000 Backup-Archive > Client > Version 4 Release 2, Level 1 > ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintenance/ > client/v4r2/Windows/WinNT/LATEST/IP22373_READ1STC.TXT > > Regards, > > Demetrius Malbrough > UNIX/TSM Administrator > > -----Original Message----- > From: Al Narzisi [mailto:[EMAIL PROTECTED]] > Sent: Friday, December 21, 2001 1:48 PM > To: [EMAIL PROTECTED] > Subject: Re: 4.2.1.15 NT Journal Service FILLING EventLog > > > I am not familiar with Journal Services. Where can I find out more about > it? > > ----- Original Message ----- > From: "Pete Tanenhaus" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, December 21, 2001 1:46 PM > Subject: 4.2.1.15 NT Journal Service FILLING EventLog > > > > In general, only basic error messages should be written to the NT > Eventlog, > > detailed error information should be written to the TSM error log. > > > > The 4.2 Journal Service incorrectly logs two messages which it shouldn't. > > > > One is generated when access to an object which has changed but is > excluded > > via the > > journal exclude list fails. > > > > The other is generated when an object changes and is deleted before the > > journal > > service can process the first change notification (apparently this is > > somewhat common > > when applications create and remove temp files). > > > > Both these problems (and many others) will be fixed in the 5.1.0 Journal > > Service. > > > > The next version of the Journal Service will also allow adding or removing > > file systems without stopping > > and restarting the service, and will have enhanced support for running in > a > > Cluster environment. > > > > > > 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 > > 12/21/2001 12:09 PM --------------------------- > > > > "Malbrough, Demetrius" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on > 12/21/2001 > > 10:25:37 AM > > > > Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > > Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> > > > > > > To: [EMAIL PROTECTED] > > cc: > > Subject: 4.2.1.15 NT Journal Service FILLING EventLog > > > > > > > > Happy Holidays, *SMers! > > > > Just a FYI! We have upgraded some of our NT 4.0 clients to 4.2.1.15 to > take > > advantage > > of the Journal Based backups, but it seems to be more of a BURDEN! The > > Journal Service > > seems to be accessing the clients every second for files to process, > > backup, > > skip, etc... > > (this is normal), but it is filling up the EventLog with a message EVERY > > SECOND! That > > is not acceptable because if there was ever a real problem on one of the > NT > > boxes then > > the EventLog would be flooded with these Journal Messages! It would > prevent > > the CRITICAL > > messages from revealing themselves! > > > > Anyone else noticed this??????????? > > > > So, we have decided to just STOP all Journal Services & disable them until > > Tivoli comes > > up with a better solution! The Journal Service needs more tweaking!!!! > > > > > > Regards, > > > > Demetrius Malbrough > > UNIX/TSM Administrator > > >
