Today we will discuss how to migrate the virtual machines running on a vSphere cluster into a VxRail cluster. Actually there are many methodologies for data migration, now I will list out some migration methodologies, its benefits and limitations.
Target VM – Non-Clustering virtual machines without Raw Device Mapping (RDM), the virtual machine only includes of the Virtual Machine Disk (VDMK).
- Migration method – VMware Storage vMotion.
- Require 1 x downtime windows for VMtools upgrade if necessary.
- The vSphere cluster and VxRail cluster are managed by an external vCenter Server.
Remark: The VxRail cluster must be managed by an external vCenter Server.
- It can keep same configuration of source VMs after move to VxRail cluster, eg universal unique identifier (UUID).
Remark: Each virtual machine has a UUID.
Now lets we look at the SDDC Manager GUI and how to monitor the VxRack SDDC Infrastructure. We’ll start on the Dashboard, where we can see at a high level physical resources that are available, the workload domains that have been deployed, and the resources that are currently in use.
Please vote for me if you like my blog “Victor Virtualization“. Thank you.
Remark: Voting will run until 15-Dec-2018.
This is my fourth year to attend the VMware vFORUM HK. Every year I enjoy each presentation and keynote sessions, I can get some information about VMware products and can meet some good friends who is working in IT company at HK.
Nutanix AHV Integration
- AOS 5.1.1+, 5.5.x+
- Veeam Backup & Replication v9.5 Update 3a
The is the demo configuration for AHV integration. Firstly we configure Veeam Backup Proxy Appliance, setup the network settings, admin user and password.
Veeam Backup & Replication 9.5 integrates with Nutanix Acropolis hypervisor (AHV), allowing you to back up Nutanix AHV VMs to Veeam backup repositories.
For integration with Nutanix AHV, Veeam Backup & Replication offers a special component of the Veeam backup infrastructure – Veeam Availability for Nutanix AHV (proxy appliance for AHV VMs backup). The proxy appliance is a virtual module that performs the role of a coordinator between the Nutanix platform and Veeam Backup & Replication. The proxy appliance communicates with Nutanix AHV to back up VMs and restore VMs back to Nutanix AHV clusters.
To back up Nutanix AHV VMs, Veeam Backup & Replication uses agentless approach. The solution works at the hypervisor level. It creates image-based backups of VMs, capturing the whole VM data at a specific point in time, including OS, system state data, application data and so on. Backups of Nutanix AHV VMs are stored on Veeam backup repositories in the native Veeam format. You can use the resulting backup files for the following restore scenarios:
- Entire VM restore
- VM disks restore
- File-level restore
- Application item restore
- Restore to Microsoft Azure
- VM disk export
- Instant recovery to Hyper-V VM
Architecture of AHV Integration
Nutanix offers a “Metro Availability” option that is a policy applied on a datastore, which effectively spans the datastore across two sites. This is accomplished by pairing a container on the local cluster with one on a remote site and then synchronously replicating data between the local (active) and remote (standby) containers. When metro availability is enabled, everything in the active container is replicated synchronously to the remote container.
Figure: The example of Metro Availability
Nutanix Cluster A (3 nodes).
Protection Domain 1 – Active Controller.
Protection Domain 2 – Standby Controller.
The protected VMs enabled with “Should DRS Affinity Rule” on Controller 1.
Nutanix Cluster B (3 nodes).
Protection Domain 1 – Standby Controller.
Protection Domain 2 – Active Controller.
The protected VMs enabled with “Should DRS Affinity Rule” on Controller 2.
Witness virtual server.