This is what the REUSEDELAY sequential media storage pool option is for.

Of course, as others have already noted, hopefully your last database
backup is a lot more recent than a month ago. You should be doing TSM
database backups on a regular basis, ideally once a day.

Regards,

Andy

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

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




Ray Baughman <rbaughman AT NATIONALMACHINERY DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
09/19/2003 10:51
Please respond to "ADSM: Dist Stor Manager"

        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Re: TSM and DR


One other thing to consider.  Does the data still reside on the tapes
today
that it resided on one month ago?  With tape reclamation taking place, and
tapes being reused.  The tape which contained data in a storage pool one
month ago, may contain data from another storage pool today.


Ray Baughman
TSM & Engineering Systems Administrator
National Machinery LLC
Phone 419-443-2257
Fax 419-443-2376
Email rbaughman AT nationalmachinery DOT com


> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Gerald Wichmann
> 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..
>
>
> This e-mail has been captured and archived by the ZANTAZ Digital
Safe(tm)
> service.  For more information, visit us at www.zantaz.com.
> IMPORTANT: This electronic mail message is intended only for the
> use of the
> individual or entity to which it is addressed and may contain
information
> that is privileged, confidential or exempt from disclosure under
> applicable
> law.  If the reader of this message is not the intended recipient, or
the
> employee or agent responsible for delivering this message to the
intended
> recipient, you are hereby notified that any dissemination, distribution
or
> copying of this communication is strictly prohibited.  If you
> have received
> this communication in error, please notify the sender immediately by
> telephone or directly reply to the original message(s) sent.  Thank you.
>