Backup Copy Job Retention Question

VMware specific discussions

Backup Copy Job Retention Question

Veeam Logoby justdoit_ » Mon Sep 19, 2016 3:53 pm

Hello!

My question is around the use of a Backup Copy Job for keeping offsite backups.
What I am looking for is the following:

I want to keep 4 weeks of retention on an offsite appliance and have it look like this:

Week 1: Initial Full (Saturday) + 5 Incrementals (Monday - Friday)
Week 2: Synthetic Full (Saturday) + 5 Incrementals (Monday - Friday)
Week 3: Synthetic Full (Saturday) + 5 Incrementals (Monday - Friday)
Week 4: Synthetic Full (Saturday) + 5 Incrementals (Monday - Friday)

The thought here is that as time progressed, week 4 would become week 1 and it would continue like forward like this.
The configuration we have tried is 7 Restore Points and 4 Weekly backup restore points for archival purposes.

Is this possible? How would I set up the Restore points and archival restore points?

Thank you for reading.
justdoit_
Influencer
 
Posts: 13
Liked: 2 times
Joined: Mon Sep 19, 2016 3:45 pm
Full Name: justDoit_

Re: Backup Copy Job Retention Question

Veeam Logoby foggy » Mon Sep 19, 2016 4:18 pm 1 person likes this post

Backup copy jobs do not have synthetic fulls. Such retention is possible with regular backup jobs. With backup copy you can do it with active fulls ("Read the entire restore point from source..." check box) or have 30 restore points in the incremental chain starting from the first full and 4 weekly GFS fulls set aside for archival purposes (separate from the incremental chain).
foggy
Veeam Software
 
Posts: 14743
Liked: 1081 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Backup Copy Job Retention Question

Veeam Logoby justdoit_ » Mon Sep 19, 2016 5:25 pm

Thank you for the reply.

So the target backup copy job screen would look like this:

Restore points to keep: 7
Check the box to Keep the following restore points for archival purposes
Set Weekly backup to 4
Check the box to Read the entire restore point from source backup instead of synthesizing it from increments

This will keep the offsite backup copy job looking like my initial post?
What we are trying to accomplish is have 4 weeks of offsite backups that have a shorter block chain.
For example, if we wanted to restore from Wednesday on Week 2, we would need the Week 2 full + only the incrementals up to Wednesday, which would result in a very short block chain.

Thank you again for your reply.
justdoit_
Influencer
 
Posts: 13
Liked: 2 times
Joined: Mon Sep 19, 2016 3:45 pm
Full Name: justDoit_

Re: Backup Copy Job Retention Question

Veeam Logoby v.Eremin » Tue Sep 20, 2016 9:58 am

Restore points to keep: 7

Everything looks good besides the quoted setting. If you want to keep increments in between those full backups, you will need to set this option to 28. Thanks.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 969 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Re: Backup Copy Job Retention Question

Veeam Logoby foggy » Tue Sep 20, 2016 10:25 am

Just keep in mind, that entire VM data will be copied from source site to create weekly full.
foggy
Veeam Software
 
Posts: 14743
Liked: 1081 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Backup Copy Job Retention Question

Veeam Logoby justdoit_ » Tue Sep 20, 2016 12:51 pm

v.Eremin wrote:Restore points to keep: 7
Everything looks good besides the quoted setting. If you want to keep increments in between those full backups, you will need to set this option to 28. Thanks.



Thank you for the reply.
Does this mean that my block chain will go back 28 days?

What we are trying to accomplish is have 4 weeks of offsite backups that have a shorter block chain.
For example, if we wanted to restore from Wednesday on Week 2, we would need the Week 2 full + only the incrementals up to Wednesday, which would result in a very short block chain.
justdoit_
Influencer
 
Posts: 13
Liked: 2 times
Joined: Mon Sep 19, 2016 3:45 pm
Full Name: justDoit_

Re: Backup Copy Job Retention Question

Veeam Logoby foggy » Tue Sep 20, 2016 12:53 pm

When backup copy active fulls are enabled, it behaves just like regular forward incremental job, so you will see the behavior you're requiring.
foggy
Veeam Software
 
Posts: 14743
Liked: 1081 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Backup Copy Job Retention Question

Veeam Logoby justdoit_ » Tue Sep 20, 2016 1:14 pm

So we would leave the restore points at 7, and not adjust them to 28, correct?
justdoit_
Influencer
 
Posts: 13
Liked: 2 times
Joined: Mon Sep 19, 2016 3:45 pm
Full Name: justDoit_

Re: Backup Copy Job Retention Question

Veeam Logoby foggy » Tue Sep 20, 2016 1:31 pm

No, to achieve 28 restore points on disk, you need to set it to 28. This way you will have 4 weekly fulls with increments in-between.
foggy
Veeam Software
 
Posts: 14743
Liked: 1081 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Backup Copy Job Retention Question

Veeam Logoby justdoit_ » Tue Sep 20, 2016 1:38 pm

Ok, so from a block chain perspective:

Week 1: Full (1) + Incrementals (2-7)
Week 2: Full (8) + Incrementals (9-14)
Week 3: Full(15) + Incrementals (16-21)
Week 4: Full(22) + Incrementals (23-28)

So, if we wanted to do a restore from Week 3, Wednesday, assuming that the Full's are on Sunday, we would need:
The Week 3 Full (block chain 15) + Monday, Tuesday, Wednesday incrementals (block chain 16, 17, 18)

Correct? We would not have to read from block chain 1 all the way through block chain 18?
justdoit_
Influencer
 
Posts: 13
Liked: 2 times
Joined: Mon Sep 19, 2016 3:45 pm
Full Name: justDoit_

Re: Backup Copy Job Retention Question

Veeam Logoby foggy » Tue Sep 20, 2016 1:39 pm

Correct.
foggy
Veeam Software
 
Posts: 14743
Liked: 1081 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Backup Copy Job Retention Question

Veeam Logoby justdoit_ » Tue Sep 20, 2016 2:16 pm

Sorry for the back and forth, but we sure that is the case? From this document:
https://helpcenter.veeam.com/backup/vsp ... cycle.html

Step 5 states:
The primary full backup file remains on the target backup repository. Veeam Backup & Replication sets it aside and marks it as a weekly full backup. The weekly backup is no longer used in the backup chain.

This is stating that it removes the weekly backup from the chain, so if we needed a restore like the example above it would have to pull from block chain 1 up until block chain 18? Or am I misunderstanding?
justdoit_
Influencer
 
Posts: 13
Liked: 2 times
Joined: Mon Sep 19, 2016 3:45 pm
Full Name: justDoit_

Re: Backup Copy Job Retention Question

Veeam Logoby foggy » Tue Sep 20, 2016 3:26 pm

This is the case for synthetic fulls, however doesn't apply to active fulls. I will let documentation team know so that they update the page, thanks.
foggy
Veeam Software
 
Posts: 14743
Liked: 1081 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Re: Backup Copy Job Retention Question

Veeam Logoby justdoit_ » Tue Sep 20, 2016 8:18 pm

So I just had a call with the VVEEAM Integration Team around this.

Backup Copy Job was not designed to do what we want it to do.
It is not meant to take Daily Incrementals for a long period of time. It was meant to keep Weekly/Monthly/Quarterly/Annually for long periods.

What we want to do is not possible.
The solution that they provided me with is to create two Backup Jobs, one replicating to each set of storage (Onsite/Offsite) or have the existing one Backup Job and replicate it at the storage level.
justdoit_
Influencer
 
Posts: 13
Liked: 2 times
Joined: Mon Sep 19, 2016 3:45 pm
Full Name: justDoit_

Re: Backup Copy Job Retention Question

Veeam Logoby v.Eremin » Wed Sep 21, 2016 8:37 am 1 person likes this post

Backup Copy Job was not designed to do what we want it to do. It is not meant to take Daily Incrementals for a long period of time. It was meant to keep Weekly/Monthly/Quarterly/Annually for long periods.

That is not true. Otherwise it wouldn't be possible to specify daily synchronization interval for backup copy job. And by no means can you consider 28 days to be a long period of time.

What we've recommended in this thread should work fine and without any issues.

Thanks.
v.Eremin
Veeam Software
 
Posts: 13266
Liked: 969 times
Joined: Fri Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin

Next

Return to VMware vSphere



Who is online

Users browsing this forum: Bing [Bot], SyNtAxx and 25 guests