1.0
Table Of Contents
- About this Guide
- Introducing Hybrid Cloud Manager™
- Understanding the Hybrid Cloud Manager Installation Process
- Choosing a Deployment Architecture
- Preparing Your Installation Environment
- Installing and Configuring Hybrid Cloud Manager
- Install the Hybrid Cloud Manager Appliance
- Register the Hybrid Cloud Manager with the vCenter
- Configuring the Hybrid Cloud Manager for vCenters with an External Lookup Service
- Register the Hybrid Cloud Manager with a vCloud Air Endpoint
- Installing and Configuring Hybrid Services
- Configuration Overview
- Start Appliance Installation and Configuration
- Configure the Hybrid Cloud Gateway
- Configure the Network Extension Service
- Stretching an L2 Network to vCloud Air
- Migrating a Virtual Machine to vCloud Air
- Administration
- Troubleshooting
vCloud Air® Hybrid Cloud Manager™ Installation and Administration Guide
Page 35
b. CLI: Log in to the ESXi host running the virtual machine using SSH.
Run this command to obtain the virtual machine ID:
# vim-cmd vmsvc/getallvms | grep -i vmname
Vmid Name File Guest OS Version
6 WordPress_App [storage]WordPress_App/WordPress_App.vmx otherLinuxGuest vmx-10
Run these commands to monitor replication state using the Vmid obtained in the previous step:
# vim-cmd hbrsvc/vmreplica.getState vmid
# vim-cmd hbrsvc/vmreplica.queryReplicationState vmid
c. ICMP Ping: Monitor the continuous ping you started earlier.
The test ping should resume shortly after the Migrate VM task is completed.
9. After the migration, view the vCenter and note the folders labeled “VMs migrated from the cloud,” and “VMs
migrated to the cloud.”
• As discussed in “Understanding Replication-Based Migration,” the powered on VM has its original name. Any
replicas have a binary timestamp appended.
• Replica VMs can be used like any other VM.
Note the live and replica VMs in the following screen shot. The VM vcc-cm5 has been migrated back and forth
several times.