I know the answer is really “it depends”, but if customer says “what would you recommend” ..as they tend to do, what would be your go-to recommendation. Feel free to offer other options.
What would you consider a "standard" / recommended retention policy? (see poll)
Userlevel 7
+9
Userlevel 7
+17
As I’m on the Customer side and never get asked this kind of question, I can only provide what I would “think” would be appropriate, with a balance between “current’ restore points to ‘quickly’ restore from and viable long-term retention to be able to recover in the event of some mishap.
Personally, I’d go with your middle option Craig. A week’s worth for short-term is generally the timeframe of an org’s “operational restore window”; and, the 4Ws, 3Ms, 1Y gives the biz a good amount of long-term points from which to recover, without utilizing too much storage...assuming they’d be implementing a block clone filesystem.
Good question!
Userlevel 7
+20
This one will be subjective for sure based on the person answering and where they work. I selected the last one as it seems like a good policy and one I would implement. It will be interesting to see how the answers on this one go.
Userlevel 7
+9
chosen last option for me the best
7D/4W/12M/1Y
Userlevel 7
+7
I’m going with the second last option as that one works for us. However, it is also job dependent depending on the type of jobs being backed up and balances out our storage infrastructure too.
Userlevel 6
+2
I know the answer is really “it depends”, but if customer says “what would you recommend” ..as they tend to do, what would be your go-to recommendation. Feel free to offer other options.
From what I've seen, customers running in the cloud typically take daily backups and keep them for 14 days. They generally don't want weekly or annual backups unless necessary. (What I mean by "necessary" is that there are people who do it for reasons such as audit processes.)
Userlevel 7
+10
Hi
my choice about 7D/4W/0M/0Y is only to VM backup related. I love to explain to the customer there are no reasons to have a lot of backup data for VM. I think 14 days for performance tier backup data is a good time to retain the VM if they have immutable repository and a very reactive support team.
Different idea is for unstructured data where can be needed more restore point.
Userlevel 7
+8
Mine is very different, but I chose the middle as it seems reasonable.
With tape I actually keep a few yearly jobs offline.
I try to have 14-30 daily’s if I can for file servers at my primary site. At other sites I’ll start doing weekly/monthly jobs.
I have a few jobs that run multiple times a day so I go by how many restore points instead of days.
I also run snapshot jobs every few hours to capture the state of VM’s between the backup jobs if I need to restore something.
Userlevel 7
+6
Great pool
Comment
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.