How to change backup job after full VM restore

[pkelly_sts]

Full restores isn't something we do very often so I've never really nailed down 100% correct way to deal with the resulting change from the backup jobs perspective. So, if you restore a VM from a 2 day old restore point, what should/shouldn't you do to the backup job to deal with it as obviously the VM is now out of sync (but not completely) with the backup repository?

At the very least I expect it to have to do a full block examination so equivalent timescale of a full backup, but what would the resulting backup SIZE be, will it copy out a fresh full copy of that VM now?

Advice appreciated before a kick off the job as I had it disabled overnight to allow the migration into production to complete...

Paul

[veremin]

The restored VM that you will add to the existing job will have a new MorefID and will be treated as a completely new VM. Thus, full backup will be performed for it. Thanks.

[pkelly_sts]

OK, thanks for the confirmation, so remove original & add the restored one to the job then expect a full size backup?

[veremin]

Correct.

[pkelly_sts]

Many thanks!

[foggy]

In case of reverse incremental backup method, however, backup file size will not increase much, since VM data blocks that are already there will be deduped. For forward incremental, though, you will get huge first increment, however, the next active or synthetic full should return you back to the original backup size.