Comprehensive data protection for all workloads
Post Reply
hongman
Influencer
Posts: 16
Liked: never
Joined: Apr 18, 2012 3:35 pm
Contact:

Is this viable?

Post by hongman » May 17, 2013 2:36 pm

Hi

Just double checking this is going to work as I think it will.

If I set a job as Reverse Incremental with a retention of 90 days.

Every 90 days I copy the entire backup folder to an external HDD and lock it up. The backup then overwrites from day 91 as per retention and after another 90 days, rinse repeat.

Does this sound feasible to retain a historic backup?

Have I missed any gotcha's?

foggy
Veeam Software
Posts: 18278
Liked: 1564 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Is this viable?

Post by foggy » May 17, 2013 2:57 pm

Yes, works as you describe it.

hongman
Influencer
Posts: 16
Liked: never
Joined: Apr 18, 2012 3:35 pm
Contact:

Re: Is this viable?

Post by hongman » May 17, 2013 2:58 pm

Thank you! :D

veremin
Product Manager
Posts: 16901
Liked: 1439 times
Joined: Oct 26, 2012 3:28 pm
Full Name: Vladimir Eremin
Contact:

Re: Is this viable?

Post by veremin » May 20, 2013 8:10 am

Every 90 days I copy the entire backup folder to an external HDD and lock it up.
The corresponding .vbk, as well as, .vrb-files can be copied via simple PS script. So, if I were you, I would implement something like this:

Code: Select all

$SourcePath = "Backup repository"
$TargetPath = "External device"
$BackupFiles = Get-ChildItem $SourcePath;
Robocopy $SourcePath $TargetPath $BackupFiles; 
If you’re after GFS rotation scheme, you might want take a look at the existing discussion.

Should any other questions arise, don’t hesitate to let us know.
Thanks.

Post Reply

Who is online

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