Veritas-bu

Re: [Veritas-bu] retentions

2007-07-20 19:32:55
Subject: Re: [Veritas-bu] retentions
From: "Brandon Zermeno" <Brandon.Zermeno AT pulte DOT com>
To: "Curtis Preston" <cpreston AT glasshouse DOT com>, <veritas-bu AT mailman.eng.auburn DOT edu>
Date: Fri, 20 Jul 2007 16:18:09 -0700

There are certain environments here that require only a 2 week retention, no matter what. In this environment we run full backups everyday and when the data set is in the 80 TB range, well that just more then I need to deal with. We have been running this way for years with no major issues. Leave it up to Oracle to take 2 weeks 4 hours to try and fix RAC.

 

From: Curtis Preston [mailto:cpreston AT glasshouse DOT com]
Sent: Thursday, July 19, 2007 9:10 PM
To: Brandon Zermeno; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] retentions

 

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? ;)

 

---

W. Curtis Preston

Backup Blog @ www.backupcentral.com

VP Data Protection, GlassHouse Technologies


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.

 

 

 
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.
 
 
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
<Prev in Thread] Current Thread [Next in Thread>