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
I keep 14 restore points at most of the remote sites with some of the larger ones only holding 7 restore points.
I use GFS to keep 14 daily, 9 weekly (to cover roughly a two month period), and 6 monthly.
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.