Your environment seems like an idea candidate, journal backup is most useful for very large file systems in which only a small percentage of the objects change.
I would strongly suggest upgrading to the latest 5.32 client as many jbb changes and fixes have been made since 5.2. Keep in mind that after the journal daemon is configured to journal the file system, a full incremental backup of the file system will have to complete before subsequent backup will be able to use the journal. 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 02/24/2006 10:59 AM --------------------------- Please respond to "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> To: ADSM-L@VM.MARIST.EDU cc: Subject: Journaling Happy Friday! I'm trying to determine if a particular client is a candidate for journaling. The client is a fileserver with about 9 million objects to inspect. However, only about 65,000 objects actually get backed up. If I start using journaling for this client, what is the downside? Server 5.2.4 Windows Client 5.2 Brett
