-
- Novice
- Posts: 7
- Liked: never
- Joined: Nov 16, 2016 4:03 am
- Full Name: c0utta
- Contact:
File archive strategy
Hi guys,
I’m seeking some advice for creating file archives, just trying to make sure I’ve got the right strategy.
Veeam 9.0 is running on Windows 2012 R2 and are also using backup tape.
I want the ability to keep a backup archive of file changes for an extended period of time. User data is stored on one drive on Windows guest and only that data drive is being backed up by Veeam. This file data doesn’t change very often, so apart from the initial seed, we are seeing a minimal amount of data copied across the WAN to offsite storage.
The backup job is a reverse incremental with 90 restore points, which gives the ability to restore file changes. We have conducted numerous tests and find that it works well, and we have restored a file that was 8 weeks old that we needed.
Is this strategy sound? If so:
- Should I “Enable guest file system indexing” for the job?
- How many restore points are safe? Is it feasible to have a yearly archive (365 restore points) ?
- What steps should be taken at the end of the period? Copy the archive to tape and then consolidate so that the next period starts afresh?
Thanks in advance!
I’m seeking some advice for creating file archives, just trying to make sure I’ve got the right strategy.
Veeam 9.0 is running on Windows 2012 R2 and are also using backup tape.
I want the ability to keep a backup archive of file changes for an extended period of time. User data is stored on one drive on Windows guest and only that data drive is being backed up by Veeam. This file data doesn’t change very often, so apart from the initial seed, we are seeing a minimal amount of data copied across the WAN to offsite storage.
The backup job is a reverse incremental with 90 restore points, which gives the ability to restore file changes. We have conducted numerous tests and find that it works well, and we have restored a file that was 8 weeks old that we needed.
Is this strategy sound? If so:
- Should I “Enable guest file system indexing” for the job?
- How many restore points are safe? Is it feasible to have a yearly archive (365 restore points) ?
- What steps should be taken at the end of the period? Copy the archive to tape and then consolidate so that the next period starts afresh?
Thanks in advance!
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: File archive strategy
Hi c0utta and welcome to the community!
Thanks!
How often do you want to copy backups on tapes? Generally it`s not recommended to use reverse incremental for backup jobs if you copy the backups to tape because you will always copy full backup instead of increments.-What steps should be taken at the end of the period? Copy the archive to tape and then consolidate so that the next period starts afresh?
Some users successfully use 365-points chains, but note that restore from the far backup will take significant amount of time.-How many restore points are safe? Is it feasible to have a yearly archive (365 restore points) ?
That`s up to you. Guest file indexing allows you to search for VM guest OS files inside VM backups and perform 1-click restore in Veeam Backup Enterprise Manager, but that is optional.-Should I “Enable guest file system indexing” for the job?
Thanks!
-
- Novice
- Posts: 7
- Liked: never
- Joined: Nov 16, 2016 4:03 am
- Full Name: c0utta
- Contact:
Re: File archive strategy
Nice to be here. Been using Veeam for a while, but now getting serious!Shestakov wrote:Hi c0utta and welcome to the community!
I'm not sure of the terminology, but at the end of the "period" (whether it be 90 days or 365 days), is it possible to roll all the changes into a single backup and just back that up to tape? This backup then provides the seed for the next backup series.Shestakov wrote:How often do you want to copy backups on tapes? Generally it's not recommended to use reverse incremental for backup jobs if you copy the backups to tape because you will always copy full backup instead of increments.
OK, no problem on the time it takes to restoreSome users successfully use 365-points chains, but note that restore from the far backup will take significant amount of time.
Consider it done!That`s up to you. Guest file indexing allows you to search for VM guest OS files inside VM backups and perform 1-click restore in Veeam Backup Enterprise Manager, but that is optional.
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: File archive strategy
If you backup all the chain to tape let`s say once in 90 days having 90 days retention of the primary backup job, reverse incremental method is a good choice.I'm not sure of the terminology, but at the end of the "period" (whether it be 90 days or 365 days), is it possible to roll all the changes into a single backup and just back that up to tape? This backup then provides the seed for the next backup series.
-
- Novice
- Posts: 7
- Liked: never
- Joined: Nov 16, 2016 4:03 am
- Full Name: c0utta
- Contact:
Re: File archive strategy
Hi Shestakov,
Thanks for your advice - most appreciated.
Here's my plan:
- create a yearly archive (365/366 days of retention)
- on 1-Jan, backup the archive chain to tape
- consolidate the backup (not sure how to do this, so would appreciate some direction)
Sounds too easy!
Thanks for your advice - most appreciated.
Here's my plan:
- create a yearly archive (365/366 days of retention)
- on 1-Jan, backup the archive chain to tape
- consolidate the backup (not sure how to do this, so would appreciate some direction)
Sounds too easy!
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: File archive strategy
What is the purpose of the backup consolidation in your case?
When you have 365 points long backup chain and backup job makes a new restore point, the oldest one will be automatically deleted. So you will have 365 points in the main chain all the time.
When you have 365 points long backup chain and backup job makes a new restore point, the oldest one will be automatically deleted. So you will have 365 points in the main chain all the time.
-
- Novice
- Posts: 7
- Liked: never
- Joined: Nov 16, 2016 4:03 am
- Full Name: c0utta
- Contact:
Re: File archive strategy
Now that you've asked the question - I don't know! The backup would take up less space but then continually grow throughout the year.
BUT, the consolidated backup would be useless for a few months so it would be best to leave 365 days.
Thanks for your help.
BUT, the consolidated backup would be useless for a few months so it would be best to leave 365 days.
Thanks for your help.
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: File archive strategy
yep, I would not consolidate the backup chain. Since it`s recommended to have 2 copies of backups + disk restore is much faster.
Thanks!
Thanks!
-
- Novice
- Posts: 7
- Liked: never
- Joined: Nov 16, 2016 4:03 am
- Full Name: c0utta
- Contact:
Re: File archive strategy
This then leads me to my next question - what would be the best method to verify the backup chain isn't corrupted?
Is this where SureBackup is used, or is that only useful for whole VM's?
Thanks!
Is this where SureBackup is used, or is that only useful for whole VM's?
Thanks!
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: File archive strategy
You are correct, Surebackup is the best recovery verification.
Thanks!
Thanks!
Who is online
Users browsing this forum: AdsBot [Google], Google [Bot], Kirassant, Majestic-12 [Bot] and 173 guests