Saving a specific restorepoint for retention purposes

VMware specific discussions

Saving a specific restorepoint for retention purposes

Veeam Logoby Peejay62 » Sun Nov 29, 2015 9:11 pm

Hi,

This is the case, every now and then there is a demand for freezing/saving a specific restorepoint of a VM. For example a vm is not functioning well and one knows that at a specific moment it did (so the backup of that moment, let's say the version of 2 weeks ago, is very usefull). So I am asked to freeze that backup (even till further notice).
What I would really like to have is an option to easily perform that freeze. Changing the retention within the complete backupjob (map based backup) isn't preferred, I don't want to mess up the backupchain. Nowadays I save the vmfiles to a location and keep them there until no longer needed. But then you have some administration and in the case that you have to put the VM back tot that version (and the original backup has already expired in the meanwhile) that gives some additional work to do.
Actually, what I am looking for is an additional option within disk/restoreoptions. Actually a "quickbackup" of a restorepoint. That function would extract the specified restorepoint out of the backupset and store it again as a self contained backupimage. Within VeeamB&R for easy management and usability. Can something like that be done?

Thanks, Peter
Peejay62
Expert
 
Posts: 171
Liked: 21 times
Joined: Tue Aug 06, 2013 10:40 am
Full Name: Peter Jansen

Re: Saving a specific restorepoint for retention purposes

Veeam Logoby chrisdearden » Sun Nov 29, 2015 9:17 pm

Sounds similar to a "litigation freeze" kind of functionality.
chrisdearden
Expert
 
Posts: 1529
Liked: 225 times
Joined: Wed Jul 21, 2010 9:47 am
Full Name: Chris Dearden

Re: Saving a specific restorepoint for retention purposes

Veeam Logoby Peejay62 » Sun Nov 29, 2015 9:24 pm

yes... you're not hinting are you? I just could imagine this being available in a upcoming release...
This would be a great feature as I am probably not the only one in need of such a function.
Peejay62
Expert
 
Posts: 171
Liked: 21 times
Joined: Tue Aug 06, 2013 10:40 am
Full Name: Peter Jansen

Re: Saving a specific restorepoint for retention purposes

Veeam Logoby chrisdearden » Sun Nov 29, 2015 10:08 pm

Its a request I have heard before :) makes since to me to do with an adhoc copy job or similar
chrisdearden
Expert
 
Posts: 1529
Liked: 225 times
Joined: Wed Jul 21, 2010 9:47 am
Full Name: Chris Dearden

Re: Saving a specific restorepoint for retention purposes

Veeam Logoby Peejay62 » Sun Nov 29, 2015 10:14 pm

Yes, instead of restore complete vm or restore vmdk files write the appropriate blocks, a restore reads those blocks anyway, into a repository as a new, extracted backup that lives on it's own.
Peejay62
Expert
 
Posts: 171
Liked: 21 times
Joined: Tue Aug 06, 2013 10:40 am
Full Name: Peter Jansen

Re: Saving a specific restorepoint for retention purposes

Veeam Logoby dellock6 » Mon Nov 30, 2015 9:45 am

Or another idea could be to have VeeamZIP using an existing backup as a source instead of a running VM.
Again not a hint, but a suggestion for a possible feature request.
Luca Dell'Oca
EMEA Cloud Architect @ Veeam Software

@dellock6
http://www.virtualtothecore.com
vExpert 2011-2012-2013-2014-2015-2016
Veeam VMCE #1
dellock6
Veeam Software
 
Posts: 5047
Liked: 1330 times
Joined: Sun Jul 26, 2009 3:39 pm
Location: Varese, Italy
Full Name: Luca Dell'Oca

Re: Saving a specific restorepoint for retention purposes

Veeam Logoby Peejay62 » Mon Nov 30, 2015 10:03 am

thanks for thinking along. I hope this ends up at the r&d department for further evaluation.
Peejay62
Expert
 
Posts: 171
Liked: 21 times
Joined: Tue Aug 06, 2013 10:40 am
Full Name: Peter Jansen

[MERGED] Long Term Legal Hold: Specific Restore Points/Files

Veeam Logoby George_Lenzer » Tue Jan 26, 2016 5:31 pm

I've been searching the forums for an answer to my question, and the closest QUESTIONS I've found are:

http://forums.veeam.com/veeam-backup-replication-f2/more-questions-on-backup-retention-and-archive-t20084.html

and (even closer):

http://forums.veeam.com/veeam-backup-replication-f2/long-term-data-archiving-with-veeam-t27439.html

But neither answer works for what I've been asked. My current set up:

-Multiple remote sites with Veeam repository/proxy/WAN accelerator sets
-Central storage site (DR site) with repo/proxy/WAN that all remotes perform backup copies to
-Central management site (main data center) that coordinates the Backup and Backup copy jobs for remote and central sites

Remotes:
I keep 14 restore points at most of the remote sites with some of the larger ones only holding 7 restore points.

Central Storage:
I use GFS to keep 14 daily, 9 weekly (to cover roughly a two month period), and 6 monthly.

The question:
If a legal hold on a particular user (file servers are part of the backups mentioned above) is requested, that particular user's data may need to be kept for up to two years, beyond the half a year of backups we retain with GFS. It seems it would be inefficient to change the GFS retention of that particular backup copy job just to hold onto the data for two years. The solutions I've come up with so far:

1. Restore the data from the oldest backup when requested and save it to the restored files location (which is our usual approach) as well as storing the restored data in some secondary location for the two years required (outside of Veeam). The reason to keep it is that we might be asked to restore the data again within the two year period. Pro: This is simple. Con: It might not be the most efficient use of disk space if many legal holds are in effect over time.

2. Make a new backup copy job just for the server that this user's data is on and set the retention period for that single VM to meet the two year requirement. Pro: It stays within Veeam. Con: It doesn't look like we can make a backup copy of a backup copy, so we'd only be able to go back 14 restore points with the new backup copy since that's all we keep at the remote site, and... the bandwidth needed to make a new backup copy especially if the file server is huge. Some might need seeding to even work.

3. Somehow determine which backup file(s) in the backup copy job that contains the data will be needed long term and copy those backup file to another location for later import if a restore is needed again at a later date. Pro: It stays in a format easily usable by Veaam. Con: It would require much more storage than the required data itself. One of the restores I had to perform was only a few kilobytes in size. Keeping a 900 gig backup for a few K is extremely inefficient.

We are moving away from tape, otherwise I'd probably go with saving off the backup copy data to tape for these situations.

I'm a newbie to Veeam, and I've used whatever free time I have to try and read the documentation, but I'm sure there are abilities I'm not yet aware of. I only recently learned about GFS for example. Any suggestions would be greatly appreciated.
George_Lenzer
Novice
 
Posts: 5
Liked: never
Joined: Wed Oct 28, 2015 1:22 pm
Location: Ohio
Full Name: George Lenzer

Re: Long Term Legal Hold: Specific Restore Points/Files

Veeam Logoby btmaus » Wed Jan 27, 2016 2:43 am 1 person likes this post

"2. Make a new backup copy job just for the server that this user's data is on"

You can tell Veeam where to get the data from for that backup copy job, so for example, you can tell your 2nd backup copy job to get the data only from the 1st backup copy job repository location (check the job settings), that way it will only pull data from those retention points.

In v9, you can exclude files for example (or only include certain files) from the backup, so perhaps you can setup a 2nd backup copy job for the user data in question, and exclude everything else, reducing the size on the disk? You could also use the VeeamZIP function to take a once off backup and store that for 2 years.
btmaus
Expert
 
Posts: 128
Liked: 9 times
Joined: Fri Jul 17, 2015 9:02 am
Full Name: Glenn L

Re: Long Term Legal Hold: Specific Restore Points/Files

Veeam Logoby George_Lenzer » Thu Jan 28, 2016 1:54 pm

Thank you btmaus. I wasn't aware of the VeeamZIP functionality and I appreciate your sharing that information. That approach will work for instances where a lot of data needs to be held. My concern is more around the requests for long term hold of only a few megs of data (user's home dir for example) out of a large VM (many gigs in size). So far, it looks like my best option for small sets of data is to do a file restore for that user's home dir from Veeam and save it in a location dedicated to legal holds outside of Veeam.
George_Lenzer
Novice
 
Posts: 5
Liked: never
Joined: Wed Oct 28, 2015 1:22 pm
Location: Ohio
Full Name: George Lenzer

Re: Long Term Legal Hold: Specific Restore Points/Files

Veeam Logoby dellock6 » Thu Jan 28, 2016 6:11 pm 1 person likes this post

Or if you use the new v9,you can leverage file exclusions and create a manual backup of just the folders you want, and store that small backup file.
Luca Dell'Oca
EMEA Cloud Architect @ Veeam Software

@dellock6
http://www.virtualtothecore.com
vExpert 2011-2012-2013-2014-2015-2016
Veeam VMCE #1
dellock6
Veeam Software
 
Posts: 5047
Liked: 1330 times
Joined: Sun Jul 26, 2009 3:39 pm
Location: Varese, Italy
Full Name: Luca Dell'Oca

Re: Long Term Legal Hold: Specific Restore Points/Files

Veeam Logoby George_Lenzer » Thu Jan 28, 2016 6:18 pm

Luca and Glenn, thanks again. That point hadn't quite settled in with me when I first read through Glenn's response. This sounds like the right solution. Now to find out about upgrading to v9... :)
George_Lenzer
Novice
 
Posts: 5
Liked: never
Joined: Wed Oct 28, 2015 1:22 pm
Location: Ohio
Full Name: George Lenzer

Re: Long Term Legal Hold: Specific Restore Points/Files

Veeam Logoby larry » Thu Jan 28, 2016 9:40 pm 1 person likes this post

I copy them off to a USB drive which I seal and handoff to legal, in two years they can return. Cost $99. For exchange I create a database for retention and place on its own drive, move user to new DB. then backup just that database drive, the Veeam explorer for exchange can pull mail out. If Legal wants me to hold just in case I seal in the bag, sign it and lock the usb drive in the tape vault. Just be sure and label with the end date so you know when to recycle,
larry
Expert
 
Posts: 372
Liked: 89 times
Joined: Wed Mar 24, 2010 5:47 pm
Full Name: Larry Walker

[MERGED] Saving a specific restore point from being deleted

Veeam Logoby dspjones » Tue Feb 02, 2016 9:34 pm

We run incremental forever backups currently set to store 85 restore points. The job inlcudes all production servers in one job. At the current rate we typically have about 2-3 weeks of restore points on disk at any given time for most servers.
Now, our database team is going to be deploying a new sql failover cluster. The servers have been built and on turned over to them on 1/22/2016. Backups started on 1/18/2016.... and is considered the pristine state of the machines.
They are building the databases and doing testing on those server to iron out the upgrade and deployment process for an application we use. What they want to do is revert those servers back to that state the night of go-live so that they can implement the production deployment on the same servers beginning at their pristine state. This will occur on 3/1/2016. By that time, that restore point will have gone away due to the retention. I don't want to change the retention of the job for just this one event so, my question is... Is there a way to prevent that 1 restore point from being deleted so that I can restore the machine to that point at a later date?
dspjones
Enthusiast
 
Posts: 40
Liked: 16 times
Joined: Fri May 04, 2012 2:51 pm

Re: Saving a specific restore point from being deleted

Veeam Logoby foggy » Tue Feb 02, 2016 9:41 pm

You can temporarily restore VMs from that specific restore point (Instant Recovery, for example) without powering them on and backup them into a separate backup files.
foggy
Veeam Software
 
Posts: 14718
Liked: 1075 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Next

Return to VMware vSphere



Who is online

Users browsing this forum: Bing [Bot], Exabot [Bot], stehei and 29 guests