Vitaliy S. wrote:George, have you considered using rsync in this case? We recommend using rsync to sync backup files offsite. You can search this forum for offsite and rsync for more information on this.
We're using rsync now, but it's not ideal. The problem is that rsync is most effective when you're doing reverse incremental backups, because that's the only way you end up with a file with changed blocks so you don't have to replicate the entire full backup over the wire again, which is key, because we don't have a super-fast link to our offsite. This is also why we'd want to keep a local copy of the backup. However, in our opinion, reverse incremental isn't the safest backup mode, because we'd prefer to not touch our VBK if we don't have to.
Synthetic fulls are great, because if the process to create one fails in the middle, you still have the original full VBK and incremental VIB backup files intact and untouched. If we had a standalone utility capable of creating a synthetic full from a full and a series of incrementals, then we could do one full backup when we bring a new VM online, sneakernet it over to the offsite, and then just replicate the smaller nightly (or more often) incrementals to the offsite over the wire, creating synthetic fulls at the main site and the offsite once a week or so, independently, without the need to ship a massive amount of data across the wire. This is ideal because the data we need to do this is already there at the offsite
, it's just not in its most useful form without the requested utility.
Personally, I have a Veeam B&R server installed at both the main and offsite locations, so I could even get away with a new job type inside B&R: a standalone "Create Synthetic Full" job. However, I still think it would be easier to just have a standalone utility for most people.