I am still not sure what caused the corruption, maybe there was an pre-exsting condition with the VMWare disk files that caused the corruption. It kept doing that, because the disk was now corrupt and the server kept freezing during the boot procedure. After a few minutes, it switched back to the other ESX again. Upon further inspection I noticed that the HA cluster, for whatever reason, decided to do a failover to the other ESX node.

That approach failed horribly.ĭuring the VEEAM backup job the legacy server stopped responding. On a weekend I attempted to start a backup while the server was running in the hopes that I could do incremental backups before finally migrating the server to the new data center. I've got a 1GBit connection between the 2 data centers. I am using VEEAM because the vCenter in the old data center is so old, that I have trouble getting the Standalone converter to both read from the old data center and copy to the new one (SSL issues for example).

I planned on using VEEAM Backup to move the server from the old data center to our new one (back up from old data center, restore on new data center).

The old data center is running a vCenter 5.5.0 with 2 ESX hosts, the new data center uses vCenter 7 with 4 ESX hosts. I have almost no knowledge about the infrastructure in our old data center and it seems that there is no working backup there (I wasn't working here when that data center was set up and nothing is documented). I've got a big (2.5TB) legacy server in an old data center that I need to move to our new data center.

Virtual machine consolidation needed