Designing a backup strategy
-
Our infrastructure is:
- On premise xcp-ng production server (Windows VMs)
- On premise xcp-ng DR server
- DSL broadband connectivity (100/40)
- Wasabi account for offsite storage
My goals are:
- Hourly backups (8am till 8pm)
- Offsite storage to Wasabi
I have an idea of how to implement but I would appreciate any input.
My thoughts are:
- Hourly CR to DR server (@ 8am till 8pm) - Retention 84
- Weekly full to DR server (@ Sunday 8pm) - Retention 1
- Daily delta to Wasabi (@ 8pm) - Retention 90
- Quarterly full to Wasabi (Jan, April, July Oct 1st day @ 8pm) - Retention 4
Should 1 & 2 be part of the same backup job and have 3 & 4 part of a separate backup job?
Does having 2 & 4 as full backups jobs reset the chain length to avoid potential chain corruption?
Due to bandwidth constraints can I restrict the upload to after hours?
-
Pinging @florent
Also you should know a cool backup feature arrives this week, and it might be useful in your case
-
We have some interesting thing in the works, but I think a chain of 84 snapshots for the CR/DR is quite long
you can mitigate the risk of chain corruption by setting the full backup interval, this will transfer a full from time to time
-
What are your thoughts on my last three questions please.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login