- When we were running differential migration after successful full sync , it got failed moreover removed the target machine as well. We had a long discussion with Support team and they dig though all the longs and all but finally had to create the VM with the remaining VHD on Azure as without VM RM portal not even recognizing the Target. After successful creation of machine we ran the DM and again it got failed and finally it came to our notice its the VM Disk or OS disk of the VM which is not supported by RM. RM only supports 2 kind of disk Standard HDD and Premium SSD hence it was getting failed because during testing disk of the VM got changed to Standard SSD.
- After full sync customer's team was working on the Target VM and differential yet to be run. Which was planned only after the successful testing on the target VM & during the testing a lot of changes performed on the VM for the better performance and other reasons like increasing or decreasing the VM size , moving VM to different subnet and one time VM needed to recreated because of some issue. So after successful testing on the target we ran the differential and it got failed. Here lesson learnt was differential will fail if nic of VM or IP of target VM gets changed however vm size and disk doesn't matter until its supported by RM.
- Third thing that we observed at the time when we ran the first complete sync in Feb 2019 , we didn't find any option to put the target machine in AV-set during the initial setup or first full migration where we provide all the target information to be created by the replication of source and we could place the target VM in AV-set latter however it didnt create any issue for the differential migration.
No comments:
Post a Comment