Migration from one VC to another using VEEAM

VEEAM, LET'S DO IT!!

The purpose of this entire experiment was to work through the logistics of moving a VM from a 5.0 vSphere to a 5.1 vSphere without shared storage.  Or from one datacenter to another. 

I wanted to use VEEAM fastscp for the transfer as it installs quite quickly and the interface is easy to understand.   Both vCenters are joined to the same domain.

Below is the physical ESXi box.

Below is one of the nested ESXi VMs on my workstation.

As you can see, the interface would be familiar to vCenter users or even those familiar with windows explorer.

Once complete, click new schedule

Click add

Select source folder.

Select destination folder

Continue with the job creation

You'd think it would be as simple as clicking on Finish below, but that was not the case

When I tried both the scheduler and simply copying from one folder to another I received this error:

Retrieving the COM class factory for component with CLSID [5F1555F0-0DBB-47F6-B10B-0AB0E1C1D8CE} failed due to the following error: 800700c1

I then found this fix.

Due the way the COM module are coded, thankfully there is any easy fix:

1) Download the .NET 3.5 SP1 SDK Here

2) Do a custom install and select only the Developer Tools

3) Run the following commands in an elevated prompt:

CD C:\Program Files\Microsoft SDKs\Windows\v7.0\Bin\x64

CorFlags.exe "c:\Program Files (x86)\Veeam\Veeam Backup and FastSCP\VeeamShell.exe" /32BIT+

http://www.techspew.net/2011/06/27/veeam-fastscp-and-x64-windows/

After running that command, the transfer started.

When the copy completed, I browsed the LUN, found the VM and added it to inventory.

Upgraded VMTools, assigned an IP through DHCP, logged on and found a document that I created quite some time ago.  (This was originally sitting on the iSCSI appliance)

Remember, this just copies the VM, so it's still sitting back in its original storage area and the original can be deleted from the source once you have verified that the VM is stable.


Update - I did come across an issue where the datastore was not found or accessible.  I was able to connect to the hosts directly after removing the lockdown mode and opening up port 443.  (Both security risks in some environments.)