Reconnecting backup chain after VM restore

[crond]

Hi All,

I had to do a full VM restore, and reconnecting backup chain to restored VM.
From other posts it looks like as long as "per machine" backups chain is not enabled I should expect close to 100% dedup rate for new backup.
What other options should I check in the backup job to make sure backup of restored VM will not eat space on backup repository and reuse available blocks ?

[HannesK]

Hello,

From other posts it looks like as long as "per machine" backups chain is not enabled I should expect close to 100% dedup rate for new backup.

per machine chains should always be used. Per job-chains have so many downsides (I posted pros and cons multiple times on the forums)

It will use about the same space for per-job or per-machine chain (it's not worth for me to argue about small amounts of data, because it's irrelevant for the "big picture")

If you restored the VM to the "same location", then the new backup will only consume space for a new incremental backup. If you restored to a "different location", then it's a new VM (new ID in the background) and consume full space. For VMware, there are some database hacks described on the forums to avoid the full (keyword is "morefID". But for one VM, I would recommend to just let the software do its job.

Best regards,
Hannes

[crond]

It's a single VM Job,
I restore VM to the "same location" but I see that new incremental backup size is 100% of VM size, so I guess software didn't do the job ?

[HannesK]

what's the support case number for that? I tested it out before writing the answer...

[crond]

#05863342