You are correct and I agree with your logic.  I was more or less stating the
standard which is 0 for primary pools.  However, if you require a trip back
in time on a regular basis, then your approach is sound.  For trips back in
time, I'd be tempted to use the copy storage pool and restore to another
server.  I don't think I'd want to take my production *SM server back in
time, do my restore and then move forward again.  Pretty much a hassle.

Finally, if I ever did this more than once in my life, I'd seriously
question my ability to set up *SM correctly in the first place (along with
my sanity).  In the cases where adequate planning wasn't done, I can see
where a retention might have been shorter than necessary.  But how long are
db backups kept anyway?  I've seen few sites where it was longer than a
week.  Usually when you realize retentions aren't right is about six months
too late, not a week.

What about a corrupt db backup?  This might make it necessary to go back and
in that case you could have a problem.

I guess if you have slots to burn in the library, and I know I don't, I'd
set reusedelay and db retention to be the same just to be safe.  Otherwise,
I'd probably stick with 0 and take my chances.


Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80919
(719)531-5926
Fax: (719)260-5991
www.storsol.com
lipp AT storsol DOT com