How about setting a longer retention
period and _expiring_ backups if
the conditions you’re looking for have happened?
As long as I’m at it, I think a two
week retention period is crazy. You should always have AT LEAST three
full cycles. (IOW, if you’re doing a full backup every week, I
think you should have at least a three week retention period.) My
preference would be at least a month for database backups and 90 days for
filesystem backups.
As to what other products do…
NetWorker won’t expire a full backup
if there are incremental backups based on it. In your case, they would/could
have expired too and the oldest full might have expired.
TSM doesn’t expiration like this. It
keeps versions, and does not think the way these products think unless you
force it to. I therefore think that TSM wouldn’t have done what NetWorker
did.
Did I mention that a two week retention
period is too short? ;)
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Brandon Zermeno
Sent: Thursday, July 19, 2007 3:51
PM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] retentions
We
had an issue where was server was down for over 2 weeks and the last full
backups expired. The retention for this environment is 2 weeks. After the tapes
expired the App team decided they wanted to restore. Now management wants
Veritas to extend the retention period automatically if a full is not
successfully run. I do not know of any company that has this capability so I am
looking for ideas. I do not think it would be possible for a person to manually
track all the servers and their last full and then manually bpexpdate the
images. I have pushed back with the question of why was this server allowed to
be down for 2 weeks but nobody is answering.
CONFIDENTIALITY NOTICE: This email may contain
confidential and privileged material for the sole use of the intended
recipient(s). Any review, use, distribution or disclosure by others is
strictly prohibited. If you have received this communication in error,
please notify the sender immediately by email and delete the message and any
file attachments from your computer. Thank you.