I only want to keep 1 backup offsite but...

[jbarrow.viracoribt]

So, I'm trying to configure a job for our offsite backup location. This location is only going to be used if both of my buildings are gone (think tornado). If both buildings are wiped out, want the latest possible copy of all systems at an offsite location I can restore from. I'm wondering how I should configure my job's retention schedule? I have about 9.5TB worth of Backup Data (For all my VM's) and I have a 100Mbps pipe I'm looking at using. My thought is to just set it at one but I fear the upload of a full backup won't complete (even over a 100Mbps pipe) before the following days backup runs and changes the file it was in the middle of uploading. Any suggestions or thoughts?

[Vitaliy S.]

Hi Jonathan,

I would suggest using reversed incremental backup mode with retention policy set to 1. If you have an ability to ship existing backup file containing all VMs (9.5 TB worth of data) to the offsite location, then after doing this just use backup mapping feature to point backup job to existing files to start running incremental passes only.

Thanks!

[dellock6]

If your backup window is long enough, I would suggest doing two separated jobs. Apart the usual one you are already doing locally, I would setup a remote Veeam repository to help reduce traffic during the reverse incremental backup (as Vitaliy suggested). In this way only the changed data would be shipped to the remote location. Copying the local backup remotely would be less efficient, unless you do not us a replication software about to replicate at byte-level, otherwise with reverse incremental each day the full backup would be replicated from scratch.

Luca.

[jbarrow.viracoribt]

If your backup window is long enough, I would suggest doing two separated jobs. Apart the usual one you are already doing locally, I would setup a remote Veeam repository to help reduce traffic during the reverse incremental backup (as Vitaliy suggested). In this way only the changed data would be shipped to the remote location. Copying the local backup remotely would be less efficient, unless you do not us a replication software about to replicate at byte-level, otherwise with reverse incremental each day the full backup would be replicated from scratch.

Luca.

Interesting. I'm looking to use TwinStrata and their Cloud Array as my offsite storage. I wonder how I would configure their appliance as a remote Veeam respository.

[Vitaliy S.]

I wonder how I would configure their appliance as a remote Veeam respository.

If target can be Windows or Linux machine, then you should add it as a regular repository.

[veremin]

I'm looking to use TwinStrata and their Cloud Array as my offsite storage.

Furthermore, you might want to review this topic or this document which is primarily concerned with VB&R/CloudArray best practise.

Hope this helps.
Thanks.

[jbarrow.viracoribt]

Hi Jonathan,

I would suggest using reversed incremental backup mode with retention policy set to 1. If you have an ability to ship existing backup file containing all VMs (9.5 TB worth of data) to the offsite location, then after doing this just use backup mapping feature to point backup job to existing files to start running incremental passes only.

Thanks!

Where can I learn more about Backup Mapping? The manual talks about replica mapping but does not mention backup mapping. Am I missing something?

[veremin]

Where can I learn more about Backup Mapping?

For more information about backup mapping functionality, please, see corresponding User Guide (p.118).

Hope this helps.
Thanks.