Below is the process for doing V2V conversions (i.e. taking VM’s on a separate server and moving them into our cloud). We do this by mapping the FreeNAS backup volume to the client server and moving it. Once in our new cloud, we move the VM from the backup volume to the production volume. This is a second step, it’s safer than mapping our production SAN volumes to client servers.
- Client server must have a spare NIC.
- Create a new vSwitch on client server
- Add their spare NIC to the vSwitch. Give it the following IP info:
- 172.29.253.249 255.255.255.0
- It does not need a default GW
- Patch the NIC into SAN-SWITCH-A port 23 (copper)
- On client’s server go to Configuration -> Storage
- Click “Add Storage…”
- a) Choose Network File System
- b) Server: 172.29.253.10
- c) Folder: /mnt/md1000-a-b/md1000-a-b-A
- d) Datastore Name: freenas-backup-md1000-a-b-A
- The client server will now see this new disk.
- Shut down the client VM’s
- Right click on each and choose “Migrate….”, select “Change datastore” and select the FreeNAS backup volume
- Once done, right click on the VM and select "Remove from Inventory" to unregister it
- Log into our production cloud and browse the freenas-backup-md1000-a-b-A volume
- Go into the folder for the VM, right click the .vmx file and “Add to Inventory”
- Once in inventory, right click on the VM and choose “Migrate…”, select “Change datastore” and select either the nexenta-md3060e-A or nexenta-md3060e-B volume.
- Snapshot the VM
- Right click on the VM with it shut down and choose “Upgrade virtual machine hardware”
- Edit the settings on the VM and assign the NIC to the proper VLAN
- Start up the VM
- Make sure all is good
- Delete the VMware snapshot
- Upgrade VMware tools
- Once done, go back to the client server under Configuration -> Storage. Right click on the freenas-backup-md1000-a-b-A volume and delete it from the client server.
- Remove the NIC settings and delete the vSwitch.
- Remove the patch cable from the spare NIC to our SAN-SWITCH-A