Feature request - Backup Copy

[roaima]

Hello,

I've been sent here from my support ticket 01898741. I use VB&R to take backups to an off-site datacentre. I also use VB&R to archive some of those backups to long-term storage. I use Backup Copy to take these archives, with the Monthly, Quarterly and Yearly options set appropriately.

I would like to request a small enhancement: to allow me to chose NO restore points when archiving. At the moment I have to take a minimum of two restore points but these are of little use to me in an archive scenario. I don't use them to build the archives and I wouldn't use them for restores, so they are simply discarded. I would prefer not to have to create them at all.

Illustrative image (hopefully) available at https://drive.google.com/open?id=0B6-e1 ... TV0ckhwWVU

Thanks

[Shestakov]

Hello Chris,
Indeed by the nature of backup copy job minimal number of restore points to be kept is 2. Increments are needed to write only VMs` changes on the secondary disk. Having no increments, but fulls only will cause copying the whole .vbk
However if you use Active full for backup copy job the request definately makes sense, so it`s taken into account.
Thank you!

[veremin]

However, you can leverage those restore points as weekly full GFS ones without any increments created.

In order to do that set a weekly sync interval and specify the following settings:

- Simple retention policy: 2 (or whatever number you want to)
- Weekly GFS policy: 2 (or whatever number you want to)
- Read the entire restore point: Enable

Thanks.

[foggy]

Not so simple for the monthly fulls though.

[Pat490]

the latest blog entry finally explained perfectly the functionality.
https://www.veeam.com/blog/backup-copy- ... -copy.html

I was also always wondering what numbers I have to set (restore points, archives)...

[foggy]

I was also always wondering what numbers I have to set (restore points, archives)...

This solely depends on RPO requirements adopted in your company.

[Pat490]

yes of course!

[roaima]

However, you can leverage those restore points as weekly full GFS ones without any increments created.

My archive backups go to OVH Cloud Storage, where I get charged for storing and retrieving data, but not uploading. (In this respect it's much like Amazon Glacier.) For this scenario it makes no sense for me to utilise the incrementals to build an archive full backup.

Thanks,
Chris

[veremin]

Got it. In this case those two restore points are something you will have to leave with, as there is no way to avoid that.

Thank you for the feedback, though; much appreciated.