Skip to main content

Nutanix Metro Availability - Setup Guide

Nutanix Metro Availability (MA):

This new feature introduced on NOS 4.1 (Nutanix Operating System) which is really useful for the customers who is looking inexpensive DR solution especially VDI use case.  This feature allows replicate data synchronously between two sites.

Lets see requirements for implementing this feature:

NOS Version:

NOS 4.1 or later

1.     <=5ms RTT latency
2.     <400 between="" both="" distance="" kms="" o:p="" sites="">
3.     Bandwidth depends on “data change rate”
4.     Redundant  physical network connection


1.     2 Nutanix clusters at each site
2.     mix/match models (eg: NX3000 at primary site and NX6000 at DR Site)


1.     ESXi 5.x supported
2.     KVM/Hyper-V not now, maybe later

Nutanix License:

1.     Ultimate

MA supports compression-over-the-wire which reduces bandwidth utilization significantly during replication.

Though it is only few clicks to configure the Metro Availability feature, but it requires few other configurations. Technically, the container is getting replicated to the DR site. So, the container name must be same for both sites (reason behind this the same datastore name maintained in VM configuration file to avoid re-registering the VMs in the DR site).

Step 1:

Create the Container on the both sites using the same name.  Select the “Storage” from Prism UI, click the Container option.  The Data de-duplication and compression supported on the containers for MA.

Step 2:

Create the Remote Site, Select the “Data Protection” from the Prism UI, and then click “Remote Site”

Enter the name for Remote site and enter IP Address of CVMs of the target site.

Select the Use SSH Tunnel if you are planning to use the SSH tunnel between both sites.  Select the “Disaster Recovery”  without fail. VStore name mapping not required.

Repeat the same setup on the DR site, but enter IP address of Primary site CVMs. After the configuration, test the connection between both sites using Test Connection option

Step 3:

Time to configure the Metro Availability (MA), select the Data Protection from Prism UI, click the “Protection Domain” and select “Metro Availability”

Enter name for MA, press Next.

Select the container to replication,  you cannot select multiple containers.

Then select the remote site from compatible Remote site (Upper window)

In the VM Availability screen, select the method to disable the MA either manually or automatically after specified time when a network or any other problem interrupts the connection between both sites.

Press Next, in the “Review” screen verify the all the configuration and click the “Create” button.

Step 4:

Activate the Metro Availability , click the “Metro Availability” in the “Protection Domain”, select the target container, Click the “Activate” button. Make sure that target container is empty, else MA will delete the data from the container.


Popular posts from this blog

vCenter Reinstallation after 60-Days trial expires without losing Database Contents

Many of us still evaluating the vSphere and vCenter in our test environments. Sometimes, it takes more than 60 days to evaluate where trial edition expires.
We can't extend the trial edition in ESX host, either we have to reinstall it or license it. vCenter also have to follow the same way as ESX does. But, here we can keep old database contents as it is when you reinstall the vCenter software.

This document using vCenter 4.0 and SQLEXPRESS 2005 (built in) database. At the time of installation of vCenter 4.0, it installs SQLEXPRESS 2005 by default unless any other Database specified. Mostly, we are using built-in database is SQLEXPRESS 2005 for testing environment.
When you install vCenter 4.0, it installs SQLEXPRESS 2005 and creates a database called "SQLEXP_VIM". You can view this thru SQL Server Configuration Manager console.
Start à All Programs à Microsoft SQL Server 2005 à Configuration Tools à SQL Server Configuration Manager

Creating DSN

Create a System DSN for this d…

Set VLAN ID to IPMI Address in Nutanix

The IPMI is remote management interface like as HP iLO, DELL DRAC. During the Nutanix cluster deployment, it is not possible to mention the VLAN ID of the IPMI's IP Address. This need to be entered thru command line via ESXi host or Windows Hyper-V. This article talks about ESXi host only.

Login to ESXi thru SSH client. Run the following command to enter the VLAN ID (we assume that you already configured IP Address)

~ # /ipmitool lan set 1 vlan id 333

~ # /ipmitool lan print1
Set in Progress         : Set Complete Auth Type Support       : NONE MD2 MD5 PASSWORD  Auth Type Enable        : Callback : MD2 MD5 PASSWORD                          : User     : MD2 MD5 PASSWORD                          : Operator : MD2 MD5 PASSWORD                          : Admin    : MD2 MD5 PASSWORD                          : OEM      : MD2 MD5 PASSWORD  IP Address Source       : Static Address IP Address              : xx.xx.xx.xx Subnet Mask             : MAC Address             : xx:xx:xx…

Changing Thin to Thick disk and vice-versa

You can change the existing Virtual Hard disks (VMware based) from Thick to thin and vice-versa. This can be achieved by either using VMotion/SVMotion or command line tool called "vmkfstools". Using VMotion/SVMotion is required a valid license. Select “Migrate” and choose “Change Datastore” and select the Disk format.

If you don’t have a VMotion/SVMotion license, use the following command to achieve the same.

From Thick to Thin:

vmkfstools –i "Thickdisk.vmdk" -d thin "Thindisk.vmdk"

It will start to clone to virtual hard disk in Thin Provision method. After completed, you can attach this disk with VM and power it on. If all looks good, you can delete the original thick disk from the data store.

Use the following command to see real-time usage of thin disk:

du –h "Thindisk.vmdk"

You can notice the big difference of disk usage between of Thin and Thick format disks.

From Thin to Thick:

vmkfstools –i "Thindisk.vmdk" -d zeroedthick "Thindisk…