GFS Copy job to manage retention on the same repo.

Availability for the Always-On Enterprise

GFS Copy job to manage retention on the same repo.

Veeam Logoby motoxrdr21 » Wed Jan 11, 2017 1:31 pm

To keep a long story short, a Veeam Support Engineer recently suggested that we could handle our backup file retention using a GFS copy job rather than running a separate annual job.

I like the idea, so I setup a GFS backup copy job this morning to test it, however the job won't run because the source and target repositories are the same. This job is only being used to handle file retention, more specifically to satisfy our requirement to keep an annual backup, so pointing it at a different target repository isn't really a requirement for our use case. I'm sure a separate source & destination repo would perform better, but everything from the backup server to the repository storage is outside of our production environment so the only effect that will have is a decreased backup window.

Is there a registry flag to configure the copy job to ignore this warning, or would we have to setup another repository in order to use GFS-based retention?
motoxrdr21
Influencer
 
Posts: 13
Liked: 1 time
Joined: Wed Apr 30, 2014 10:52 am
Full Name: Steve Galambos

Re: GFS Copy job to manage retention on the same repo.

Veeam Logoby PTide » Wed Jan 11, 2017 4:51 pm

Hi,

Did I get it right - you basically want to use a copy job to make copies of backup files produced by a simple backup job and place them on the very same repo thus managing the backup files retention, is that correct?

Thanks
PTide
Veeam Software
 
Posts: 3019
Liked: 246 times
Joined: Tue May 19, 2015 1:46 pm

Re: GFS Copy job to manage retention on the same repo.

Veeam Logoby sethj » Wed Jan 11, 2017 7:59 pm

I actually came here looking for the same thing: I just want an 'end of month' that is kept for a year. Backup Copy won't allow source/target to be same repo. Do I really have to setup a separate set of jobs for my month end?
sethj
Lurker
 
Posts: 1
Liked: never
Joined: Wed Jan 11, 2017 7:55 pm
Full Name: Seth J

Re: GFS Copy job to manage retention on the same repo.

Veeam Logoby motoxrdr21 » Wed Jan 11, 2017 8:52 pm

Yes PTide,

We would run a simple backup job as the source which would keep the minimum number of restore points, and from that a backup copy job would run to manage an annual grandfather restore point along with regular father/son restore points. All restore points from the simple backup job & the copy job would be on the same repo...ideally the simple backup job would be configured to handle the GFS rotation, but it seems like that type of restore point retention is only available with copy jobs.

Thanks
motoxrdr21
Influencer
 
Posts: 13
Liked: 1 time
Joined: Wed Apr 30, 2014 10:52 am
Full Name: Steve Galambos

Re: GFS Copy job to manage retention on the same repo.

Veeam Logoby jdavidson_waters » Wed Jan 11, 2017 8:56 pm 2 people like this post

You can setup two repositories on the same underlying storage volume.
E.g if you are using F:\Backups as your main backup job repo then you can create a new repo called F:\GFS and use that as a target for the Backup Copy job.

It's the same underlying disk, but has two Veeam repos on it.

Obviously if you lose the disk then you've lost your recent backups and long term retention so this doesn't meet the 3-2-1 best practice.
@jam_davidson
jdavidson_waters
Service Provider
 
Posts: 33
Liked: 12 times
Joined: Tue May 07, 2013 2:50 pm
Location: Northeast UK
Full Name: James Davidson

Re: GFS Copy job to manage retention on the same repo.

Veeam Logoby motoxrdr21 » Wed Jan 11, 2017 9:26 pm

jdavidson_waters wrote:Obviously if you lose the disk then you've lost your recent backups and long term retention so this doesn't meet the 3-2-1 best practice.


We also go to tape stored on-site & to offsite rotating disks, so we still hit 3-2-1.
Right now we run an additional VMWare Backup job once a year to create an annual backup, the GFS copy job would replace that by maintaining an annual grandfather.

Honestly this would be much easier if the source VMware backup job supported GFS-style retention, because all we're doing is using a backup copy job to supplement the simple retention policy that we're restricted to in the source job.
motoxrdr21
Influencer
 
Posts: 13
Liked: 1 time
Joined: Wed Apr 30, 2014 10:52 am
Full Name: Steve Galambos

Re: GFS Copy job to manage retention on the same repo.

Veeam Logoby PTide » Thu Jan 12, 2017 1:39 pm

James is spot on - you can create another repo folder on the same volume.

Honestly this would be much easier if the source VMware backup job supported GFS-style retention
There is an existing thread for that feature request, feel free to post there.

Thanks
PTide
Veeam Software
 
Posts: 3019
Liked: 246 times
Joined: Tue May 19, 2015 1:46 pm


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Bing [Bot] and 16 guests