While the journal service is down, any file system changes are not 
tracked. If a file changes while the journal service is down, it will not 
be backed up until either another full (non-journaled) backup runs, OR the 
file changes again and the journal service is able to track it at that 
time.

If the journal service is not shut down cleanly (e.g., a cluster failover 
in a cluster setup, or something else that causes the journal to not shut 
down cleanly), the journal database might be in an inconsistent 
("corrupt") state, after which behavior is unpredictable. "Unpredictable" 
could run the gamut of files not getting backed up when they should or a 
journal service crash when the corruption is encountered.

So PreserveDbOnExit=1 should only be used when you know you can stop the 
journal service cleanly and you expect it to start shortly thereafter 
(like in a controlled reboot scenario).

Best regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page: 
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 07/09/2008 
08:09:54 AM:

> Yes, that's it. You set it to 1 if you want it to retain/preserve after 
going
> offline.
> 
> I wonder why IBM recommended I keep it to zero in my situation?
> 
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Erwann Simon
> Sent: Wednesday, July 09, 2008 9:38 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] Journaling database retaining upon reboot?
> 
> Hi Charles,
> 
> Look at the PreserveDbOnExit parameter of the tsmjbbd.ini configuration 
> file.
> 
> As a general reference about JBB, read the FAQ :
> http://www-1.ibm.com/support/docview.wss?uid=swg21155524
> 
> -- 
> Best regards / Cordialement / مع تحياتي
> Erwann SIMON
> 
> Bell, Charles (Chip) a écrit :
> > I have a machine that has 36 NTFS Mount Points, each with millions of
> files.
> > Since they are all hosted on the same machines, TSM Support highly
> > recommended setting up a node for each, and to have TSM journal each. 
Now I
> > am running into a situation where every time that machine is rebooted 
for
> > patches/etc., the incrementals have to rebuild the journal database. 
Is
> there
> > a way to avoid that, as I am only 1/3 of the way through the Mount 
Point
> > Usage (They have only used 12 of the 36 thus far).  Please help.  J 
> > 
> > 
> > 
> > God bless you!!! 
> > 
> > Chip Bell 
> > Network Engineer I
> > IBM Tivoli Certified Deployment Professional (ITSM)
> > Baptist Health System 
> > Birmingham, AL 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > -----------------------------------------
> > Confidentiality Notice:
> > The information contained in this email message is privileged and
> > confidential information and intended only for the use of the
> > individual or entity named in the address. If you are not the
> > intended recipient, you are hereby notified that any dissemination,
> > distribution, or copying of this information is strictly
> > prohibited. If you received this information in error, please
> > notify the sender and delete this information from your computer
> > and retain no copies of any of this information.
> 
> --------------------------------------------------------------
> Ce message ne contient aucun virus connu. http://www.astaro.fr
> 
> 
> --------------------------------------------------------------
> Ce message ne contient aucun virus connu. http://www.astaro.fr