Skip to main content

Updating a replica after migrating it to a new datastore

Thread needs solution

Hi,

Is it possible to continue using the same replication job after moving replicas to a new datastore? I moved a series of _vmpreplica VMs to a new RAID array on my backup server. The replica job failed after that move, and had to remove them from inventory, rename the folders, and create a new replica job. That will take a good bit of time to do. Seems like there should be a simpler way to use the existing replicated VMs.

Thanks!

--Ben

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 22
Comments: 3800

Hi Ben,

There is one specific here: in the replica VM folder Acronis vmProtect also creates a special test_meta.info file which contains metadata information about the replica VM in order to properly track it. When you migrate the replica VM to another datastore through vSphere client this test_meta.info file is not migrated automatically which causes the problem. Therefore the proper sequence of actions should be as follows:

1) Migrate the replica VM to different datastore
2) Edit the existing replication task and point it to the new datastore on 3rd step of the replication wizard
3) Move the test_meta.info file from the old replica VM folder to the new one (on new datastore) via vSphere Datastore Browser

After that the existing replication task will be able to run and update replica incrementally.

P.S. we are planning to change this behavior in the next version of Acronis vmProtect where test_meta.info will be added as part of the replica VM, so that this info is also migrated when you change datastore for the replica VM through vSphere client (likely it will be a separate virtual disk attached to replica instead of test_meta.info file).

Thank you.
--
Best regards,
Vasily
Acronis vmProtect Program Manager

"2) Edit the existing replication task and point it to the new datastore on 3rd step of the replication wizard"

That has been the step that I missed. Other than that, the steps mentioned by Vasily works!