daphnis wrote:When a VM is replicated to a destination site, Veeam preserves the instanceUuid (AKA vc.uuid in the VMX file) as it should. If one manually changes the instanceUuid at the destination and the Veeam replication job re-runs and moves data, that ID is overwritten with the one in the source (because this is what is in the source VMX). Is there a registry key somewhere that will prevent Veeam from behaving this way? I need those instanceUuid numbers to be different and yet still be able to replicate the contents of the source VM's disk. Can this be done?
Users browsing this forum: Bing [Bot] and 1 guest