The Prism Self Service feature represents a special view within Prism Central. While Prism Central enables infrastructure management across clusters, Prism Self Service allows end-users to consume that infrastructure in a self-service manner. Prism Self Service uses the resources provided by a single AHV cluster. (ESXi and Hyper-V are not supported platforms for Prism Self…
This set of questions comes up a lot in conversations with my customers, “What should my Enterprise Cloud look like? Should I stick with Private Cloud, should I go Hybrid Cloud or put everything into the Public Cloud? Which Public Cloud provider is the best?” It is a confusing time for enterprises developing their cloud […]
At Rubrik, every product release aims to add capabilities that will address our customers’ current pain points with enterprise data management. We started out by protecting VMware vSphere environments, and now support more than 20 platforms. While we are aggressively proliferating to multiple platforms, we are equally focused on refining our current solutions based on […]
This could be the easiest application migration you have ever completed Nutanix released Acropolis Operating System (AOS) version 5.5 a few days ago which I blogged about here. One major shift is that Nutanix Self Service Portal (SSP) has been moved from Prism Element, admin interface per Nutanix cluster, to Prism Central (PC), multi cluster…
To continue my previous post here I will show how to restore Nutanix AHV VM,
The below is outline of process of the restore process:
- Mount Nutanix container to backup host.
- Create a .restore folder on container.
- Restore AHV VM disk to .restore folder.
- Run nbaapi_ahv_vm_restore
- Verify restored VM on Prism Console.
Lets try restore now:
- Login to backup client using your choice of SSH client and create a mount point to mount Nutanix Container.
Here i had create a mount point as nfs1 at root.
- Mount the Nutanix container at /nfs1 directory.
mount -t nfs 172.16.157.10:/default-container-33163 /nfs1
change to /nfs1 and list files to verify
- Create .restore folder and verify
List to verify its been created.
ls -ld .?*
- Now go to Backup, Archive and Restore in Netbackup Console and browse for the backed up VM. Source client will be the VM name and destination client will be the backup host.
- Select disk image file, metadata file on contents lists and click Restore to select destination folder as .restore directory on the mount point where you have mounted Nutanix Container on backup host. NOTE: the disk image file should be restored on root of to .restored directory.
- Monitor and wait for the restore to complete from Activity Monitor. the restore process will restore two files metadata.json and disk image file.
- In order to restore the VM onto the Nutanix cluster we need to run nbaapi_ahv_vm_restore whihc is located at /usr/openv/netbackup/goodies.
- There are three scenarios to restore based on that we need to update the metadata file.
- When original VM is NOT existing or we are restoring the VM to another Nutanix cluster, use the original metadata file.
- Restore the VM where the original VM exists and it should be impacted, update the metadata file.
- Restore to same cluster or another cluster with different container, update the metadata file. The details are specified in Veritas Netbackup AHV Administrator’s Guide here
- Run the command as below to restore the VM according to scenarios above with metadata file.
/usr/opnev/netbackup/goodies/nbaapi_ahv_vm_restore --metadata_file_path /nfs1/.restore/metadata.json --username --password --cluster_name
This command is going to use Nutanix API to create VM using the restore disk image and specification using metadata.json file
- If you are restoring as different VM you have option to use native Prism capabilities without using the above command. Create a new VM and add disk using ADSF file with required specifications without impacting original VM.
- Power On your restored VM to verify.
Conclusion : Although the overall process is not simple but it great effort to have protecting your Veritas Netbackup investment and adapting Nutanix AHV. Hope Veritas team is going to add more simplicity to the overall process and keep updating for full integration with Nutanix. After having discussion with Veritas Netbackup product team I am very much optimistic with their openness to feedback and wish them to stay ahead in the Backup and Recovery.
In my previous post here I had gone through how to verify the prerequisites for integration of Veritas Netbackup to protect Nutanix AHV. In this blog i will go through the policy configuration and backup of Nutanix AHV VMs.
- Create a new policy and specify name of the policy
- On the attributes tab select “BigData” as Policy Type and use your Policy Storage.
- On Schedule tab create a new schedule for backups using required frequency setting or calendar schedule and backup windows.
- On next Clients tab specify the AHV Virtual Machine names you need to protect. NOTE: The VM names are case-sensitive, I would recommend to copy and paste the client names from Prism interface. NOTE: The client operating system is NOT automatically detected.
- The most important configuration is on “Backup Selection” tab. Add the below as
- Backup_Host=<hostname of your backup host>
- Application_Server=<ip address or fqdn of Nutanix cluster>
- Save the policy by click OK
At this point you are ready to test your Nutanix AHV policy. Right click the policy you created and click “Manual Backup” and click OK
Go to Activity Monitor and the policy process, you can also see in Prism snapshot creation task before backup has started and snapshot deletion when backup finished.
Looking at the backup speed I was really impressed, while I was uploading the above image the backup was already finished. In order to verify the speed I did run a full backup of a VM having 50Gb of data and was completed in ~8 minutes and consecutive backups in ~3 minutes. NOTE: Although statistics may vary based on real environment.
In continuation next post here I will cover how to restore the VM to Nutanix Cluster.
As Nutanix AHV is getting more attention in enterprise data center it had started to get more recognition from supporting ecosystem. One of the most important support for any hypervisor is backup integration, although the native Data Protection are in most case fully sufficient a third-party backup solution is equally important to have improve adaptability in enterprises.
Within the core enterprise backup provider Veritas Netbackup was recently to onboard the hyperconverged journey into data center.
With the release of Veritas Netbackup 8.1, Parallel Streaming Framework (PSF) was introduced. PSF is an integration of distributed kind of workload like Hadoop, HBase etc, kind of bigdata or distributed application and obviously Nutanix platform which service multi-PBs of data. More about PSF is available here at Veritas Blog.
As this is first release of integration Veritas Netbackup is currently supporting full VM backups only and expected to support Nutanix change block tracking in upcoming release.
I appreciate Veritas Netbackup Product Management and Engineering Team who openly accepted my feedback and jumped immediately to address the concerns.
In the first blog i will go through the requirements about configuration of VM backups using Veritas Netbackup.
Requirements or can call as pre-requisites:
- Firstly Veritas Netbackup version 8.1 should be already installed and configured.
- Media server should be configured with backup target, tape volume pool or storage pool.
- Linux-based backup host with Nutanix AHV plugin installed, it can be Master, Media or a client (appliance is also supported). Currently backup host is supported on RHEL and SUSE Linux, although i had tested successfully on CentOS 7.4. The plug-in installation is straight forward and required no input or configuration, just extract the package downloaded from MyVeritas and install using command
- Make sure NFS client is already installed on backup host, try mount/unmount Nutanix container to verify.
- A Nutanix AHV cluster with version 5.1.x and above. I had tested with AOS 5.5 and AHV 20170830.58
- If you use the default selft-signed certificates from Nutanix, NetBackup may fail SSL validation. To disable SSL validations, edit the
nb_nutanix-ahv.conffile located on backup host in /usr/openv/netbackup and set the enable_ssl_validations to false.
- Nutanix cluster name is successfully able to resolve from master, media and backup host, unless you want to use IP address of Nutanix Cluster.
- Add backup host to Nutanix global whilelist.
- Add backup to VMware Access Host from Netbackup Console -> Host Properties – > Master Server -> Properties (Right Click or Double Click) -> VMware Access Host. Add the fqdn or shortname of backup host (i preer to add both). NOTE: Do not confuse with the name “VMware Access Host”.
- Add Nutanix cluster credentials to Netbackup, using Netbackup Console -> Media Device Management -> Credentials -> Virtual Machine Servers
Enter the name or IP address with username and password of Nutanix cluster. i would recommend to have a dedicated prism account for the purpose as using admin account will always trigger an alert in Prism when is used to call remote api.
Once the above prerequisites are verified we are good to create Nutanix AHV policy in next blog here.