In an effort to find a way to archive to a remote site, without 2 backup jobs for the same 1 VM, I have thought of a way to do it, but not sure if its possible.
Production site runs a nightly incremental backup with synthetic full creation to local backup storage.
Remote site is for DR and LTA. Ideally we just want to retain 1 full (synth is fine) at the DR. It would be checked weekly with surebackup to verify, prior to deleting last-week's backup.
I have the obvious choice of course, which is to run a second job at the production site, weekly, that does an incremental, and builds a synth on the remote site. Downside is, VMs are being backed up twice.
But could i instead, once the backup is seeded, just copy the incremental files, each week, and then with a remote instance of veeam, build a synthetic?
Basically, this once running:
Production produces nightly incremental to local storage.
Weekly, incremental files are uploaded to remote DR/LTA storage.
Remote site, is running veeam to produce a synthetic full.
New full is verified.
Increments are deleted.
wait a week then repeat.
So can a remote Veeam instance manage creating synthetic fulls from a set of backup files it did not create?
Does it need to be imported like a new backup each time if so? (because that remote veeam doesnt have the new incrementals in its database)
Any way to automate it, if it is even possible?
reason for creating a synth full and only keeping it, is that 52 increments seems EPICly dangerous and slow. Or am I antiquated in that thinking?
It seems like there are quite a few bloggers out there who are frustrated by this as well, and they just give up and go to the solution of having veeam run two jobs, one local and one for remote. Seems silly to me if that is the only solution really.
THanks guys, Any thoughts are appreciated.