Failed vMotion (Vmware Hosts) with Virtual Center (Virtual Machine with Fault Tolerance) - Worked as a Physical

Failed vMotion (Vmware Hosts) with Virtual Center (Virtual Machine with Fault Tolerance) - Worked as a Physical

Hi,

Previously OpManager could understand the migration (VMotion) of virtual machines. When a virtual machine was migrated from one host to another host automatically VM info tab (Server Snapshot) appeared the current host name and not the former. Now when a machine is migrated from one host to another, he continues with the old host information. We had some changes in our infrastructure and these may be the cause of these problems.

- Virtual Center (The machine was physically and now it is virtual, we use a feature called fault tolerance that creates a similar machine and leave it active within the same cluster because if the main problems the other can take over without any problems.)

I rediscovered the hosts and they do not understand that the machine "X" is no longer in it.

- Exchange Database (MySQL to SQL Server)

Another problem, even after upgrading to latest version of OpManager, we continue with problems of loss of connection to the database (SQL SERVER).

I had to upload the file SIF in 4share.com, because it has 30Mb and my email does not support files larger than 10Mb.


Could you help me?


Leandro Melo

                  New to ADSelfService Plus?