|Article Number: 488925
||Article Version: 4
||Article Type: Break Fix
RecoverPoint for Virtual Machines 4.3,RecoverPoint for Virtual Machines 4.3 P1,RecoverPoint for Virtual Machines 4.3 SP1,RecoverPoint for Virtual Machines 4.3 SP1 P1,RecoverPoint for Virtual Machines 4.3 SP1 P2
There was a storage vMotion done on a copy VM to a different DataStore.
In order to do so, both shadow VM and replica VM must be migrated.
The first migration is successfully performed but the second one is blocked by VMware.
Symptoms found in the logs:
The second migration is blocked due to an error:
“Relocate virtual machine <vm name> Cannot complete the operation because the file or folder ds:///vmfs/volumes/<first vmUid>/<first vm name>/vmware.log already exists”
Storage vMotion is performed by VMware, the second migration fails due to a conflict of an already existing file.
4.3, 4.3.1, 18.104.22.168, 22.214.171.124, 5.0
In RP4VMs, migrating protected VMs (with shadow based RP4VM solutions) to a different DataStore.
In order to Storage vMotion the shadow and replica VMs, the following steps would need to be performed:
1. Storage vMotion the shadow VM – only the configuration file (VMX) should be migrated, the replica VMDK(s) should be kept on the current DataStore.
By default, Configuration file and all VMDKs are migrated as part of the storage vMotion process so it is vital to click on “Advanced” on the “Select DataStore” step of the “Migrate Virtual Machine” wizard and select a different DataStore specifically for the Configuration file while keeping the VMDKs on the current DataStore.
2. Perform Test a Copy (enable image access) to bring up the replica VM
3. Storage vMotion the replica VM – (Configuration file and all VMDKs) to the new DataStore
If in step 1 a full migration was performed (i.e. to both VMX configuration file and the VMDKs), the second migrate of the replica VM will be denied. In order to solve this, perform a full migration of the shadow VM back to the initial DataStore and follow the storage vMotion steps exactly as described in the procedure above.
Finally, the floppy imageiso file used by the shadow VM would need to be changed as well:
1. Check if the target DataStore has a “RecoverPoint” folder with a RecoverPointVM.flpRecoverPointVM.iso file.
If it does not, copy the RecoverPoint folder from the current DataStore
2. Edit the settings of the shadow VM and point the floppy image to the RecoverPointVM.flp file on the target DataStore.
3. Reset the shadow VM
Remark: RecoverPointVM.iso is relevant to version 4.3.1 only. RecoverPointVM.flp is relevant to 126.96.36.199 and higher versions.
Storage vMotion procedure is described above.