VMware vSphere • Re: BackupCopyMirrorAll behaviour

Hi mrmagicman,

The registry value you're discussing doesn't impact the rehydration of fast clone'd/deduplicated files, it simply instructs the Backup Copy Job on how to handle the backups it intends to make copies of.

You are correct that moving dehydrated data to a new volume, the data will be rehydrated. If the target volume supports fast clone or deduplication, Veeam operations will be "aware" of these features and fast clone/dedup will be applied as usual when writing, but the data will be rehydrated for transit.

So it's not about the registry value, it's about moving dehydrated data to a new location, which will happen regardless of this registry value.

Can you share a bit more on the target repository? Does it support fast clone also?

Statistics: Posted by david.domask — Feb 13, 2025 9:07 am

---