- Posts: 3
- Liked: never
- Joined: May 27, 2014 2:28 pm
- Full Name: Jason Murray
-Source Host: VMWare 5.5 Update 2
-Target Host: VMWare 6.5 Update 2
-Using B&R 22.214.171.1248
On two virtual machines running Exchange 2013 and SQL Server 2012R2, the quickmigration finished successfully. Upon successful completion, I had set the source to be deleted and the migrated VM to be powered on. On first inspection, the virtual machines looked fine, but once you tried to install VMWARE tools, the services would not start correctly and a wide variety of small strange issues popped up. In the case of the Exchange server, the migrated VM was unusable. I attempted to uninstall and reinstall the VMWare tools without success. Eventually I was forced to perform a full restore.
Note: I was able to quickmigrate 6 other VMs just fine. I do not believe that the quickmigrate function is compatible with SQL or Exchange at this point. If I were to try again, I would make sure to uncheck the "delete source VM", which is checked by default.
- Veeam Software
- Posts: 21527
- Liked: 1281 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
That's quite an unexpected behavior. Not sure if it relates to the vSphere version or not, but next time I would start investigation with reviewing the Windows Event log (VSS/Application related) to see why services cannot start etc. Also, feel free to contact our technical support team to try to resolve the issues over the remote WebEx session, if you see these things happen again.
- Veeam Software
- Posts: 22981
- Liked: 2882 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
Putting VMDK movement aside, all quick migration effectively does is suspends (or powers off) VM on the source host, and resumes (or powers on) VM on the target host. These are basic VM management operations that should not be causing any issues to any apps. It's also impossible for one "not to be compatible" with the specific applications, when it does not interact with what's running inside of the VM. Finally, quick migration functionality is so old and so widely used that it is hard to believe it can still have such a terrible bugs of "nothing works" type.jmurray wrote:I do not believe that the quickmigrate function is compatible with SQL or Exchange at this point.
As such, I am much more inclined to suspect issues with the target host or storage... or may be yet another bug in vSphere 6.5? Worth investigating with our support.
On a separate note, "VMWare 6.5 Update 2" does not exist yet - I assume this is just a typo.
Users browsing this forum: No registered users and 23 guests