I would agree, if you haven't gotten a Dbbackup in months... then, you
aren't serious about DR, or even day to day backups really.

But to answer the expire question...  set the ExpInterval option in the
dsmserv.opt file to 0, or do "setopt ExpInterval 0" from the command line.

------------------------------------
David N. Reiss          407-736-3912
TSM Support Engineer
david.reiss AT siemens DOT com
...one of God's own prototypes -- a high-powered mutant of some kind who was
never even considered for mass production. He was too weird to live and too
rare to die.

-----Original Message-----
From: Steve Schaub [mailto:Steve.Schaub AT HAWORTH DOT COM]
Sent: Friday, September 19, 2003 1:29 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM and DR


If someone has not taken a TSM DB backup for 3 months, they weren't
really serious about DR in the first place.

Steve Schaub
Systems Engineer
Haworth, Inc
616-393-1457 (desk)
616-412-0544 (numeric page)
4120544 AT Archwireless DOT net (text page)
WWJWMTD


-----Original Message-----
From: Gerald Wichmann [mailto:gwichman AT ZANTAZ DOT COM]
Sent: Friday, September 19, 2003 1:19 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: TSM and DR


Say for a moment you're faced with recovering a TSM server in a DR
situation. You have your DB backup and copypool tapes and perform a
database recovery. If that DB was created back in January and it's now
March, isn't there a potential for objects getting expired the first
time you start the TSM server? E.g. when the TSM server is started it
typically performs an expire inventory as part of that sequence. I would
imagine that now that it's 2 months later, would it therefore start
expiring objects that you probably don't want to have expired?

If not, why not?
If so, whats the appropriate step to take before starting the TSM server
(or perhaps even before recovering the DB) to ensure expire inventory
doesn't ruin your recovery? I recall there being an option in
dsmserv.opt that allows you to turn off automatic expire inventory. That
seems like a good idea.. but what if there was an admin schedule that
runs expire inventory back then and you happen to start the recovery
while in the schedule's window?

I think you can see what I'm getting at with all this. I want to make
sure all my bases are covered..