Unsolved
2 Posts
0
968
August 2nd, 2022 10:00
RP4VM for Migration
Hi Team,
We are using RP4VM to Migrate VM from Source to Target V-center , after Migration we observed VM name has been changed to VM.copy , to change name again as it is in Source V-center we have to perform name change and Storage VMotion. Which become manual effort after migration.
Please let me know if RP4Vm can be use for Migration if yes why it is changing VM name
No Events found!
DELL-Josh Cr
Moderator
•
9.2K Posts
0
August 3rd, 2022 07:00
Hi,
Thanks for your question about RP4VM. It being named copy is the expected behavior. Page 51 https://dell.to/3JrVCVO
Let us know if you have any additional questions.
Mahendra Sahu
2 Posts
0
August 3rd, 2022 08:00
Hi Josh,
Thanks for your response , Since we are working on project where customer want to migrate Server like to like ( no change in Name or VMDK file ) . if we use RP4VM for migration , it will change the name after cutover , and to meet customer expectation we have to rename VM to remove .copy and then do Storage Vmotion to remove .copy from vmdk files.
This additional manual effort additional delay and chances or errors . I have not seen this behavior in any other migration tool.
Idan
675 Posts
0
September 12th, 2022 04:00
The only workaround is of today is to pre-configure a VM on the replica side (with fresh disks but with same size as prod) @Mahendra Sahu and use it as an existing replica VM.