This apar was recently opened will be fixed in an upcoming fixtest. The problem can occur when a client session is interrupted in the middle of a journal based backup.
There several other PMR's dealing with error recovery in both the client and journal service which will be fixed as part of this apar. This apar not withstanding, I still believe that Journal Based Backup in the 5.3+ client is more stable and reliable than older client versions, and I would still recommend upgrading to it if possible. Pete Tanenhaus Tivoli Storage Manager Client 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 07/27/2005 11:15 AM --------------------------- Please respond to "ADSM: Dist Stor Manager" <[email protected]> Sent by: "ADSM: Dist Stor Manager" <[email protected]> To: [email protected] cc: Subject: Re: Another Journalling Question Hi, But with a 5.3 client and journaling you can get hit by APAR ID: IC46791 Subject line: TSM client crashes during journal based backup And, in our case it was at client level 5.3.0.8 Regards, Karel -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Pete Tanenhaus Sent: woensdag 27 juli 2005 15:52 To: [email protected] Subject: Another Journalling Question It is possible to limit the size of the journal db file with the JournalDBSize setting but I strongly recommend that you upgrade to the latest version of the client as many enhancements/fixes to journal based backup have been added in the 5.3+ level client, including: - multiple journal based backup support, that is the capability of doing concurrent jbb sessions based on the client ResourceUtilization setting - rewritten file system monitor which reduces the frequency/occurrence of notification buffer overflows, and also fixes problems dealing with moved/renamed directories -new journal database implementation which improves performance and reliability, better utilizes disk space and is no longer limited to 2 gig in size You can also expect to see additional platform support (other than Windows) in a future release. Hope this helps ..... Pete Tanenhaus Tivoli Storage Manager Client 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 07/27/2005 09:40 AM --------------------------- Please respond to "ADSM: Dist Stor Manager" <[email protected]> Sent by: "ADSM: Dist Stor Manager" <[email protected]> To: [email protected] cc: Subject: Another Journalling Question Hi Environment:- Server Version 5.2.2.0 on W23k Server. Client Version 5.2.2.0 on W2k Server. I have journalling enabled on this client and it works fine. However the size of the journal files(>2gb) are a cause of concern due to lack on disk space on the C: drive . The F: drive is 176gb with about 10gb of free space. Is it possible to limit the size to say 1.5 gb, midstream ? Or would I have to disable and re-enable journalling ? And would I end up with another full backup ? T.I.A Bill
