
UNSOLVED
VBA backup/clone scheduling best practices
Hello,
I’m wondering about best practices regarding VBA backup scheduling.
Our VBA policies perform a daily backup using “incremental forever” schedule, followed by a clone.
To make it clear, our VBA policies have 2 actions
1-backup, incremental forever schedule
2-clone, incremental forever schedule
Important: backups are stored on one Data Domain, clones on another one.
Backups work great but clones fail almost everytime!
As mentioned in VMware Integration Guide:
When you select a schedule for clone actions, EMC recommends a weekly or
monthly schedule, depending on your requirements, due to the time required to
complete this action. Since save sets are synthesized on the source Data Domain
device after performing an incremental backup, a scheduled clone will clone the
entire save set chain, including data from previous backups.
My understanding is that clones ain’t working so well since we’ve been doing ”incremental for ever” backups since the beginning. It must take ages to rebuild/clone the entire saveset chain.
My question is:
If I want daily backups on one Data Domain + daily clone to another Data Domain (so we have the data on 2 different sites), what kind of policies/schedule should I use?
Any thoughts about this?
Thanks.
Responses (0)
Solutions (0)
