Team Leader - Nutanix Technology Champion - Nutanix NTC Storyteller

Julien DUMUR
Infrastructure in a Nutshell
nutanix hycu

HYCU being a backup software followed and supported by the publisher, updates will be regularly made available to you in order to correct bugs, security flaws, provide optimizations or add new features.

Upgrade Path

If you missed some updates of your HYCU system, you should know that you will have to respect an update order to reach the desired version.

Indeed, if you are like me in version 4.9.0-5310 and version 5.1.0-2871 is available, you will not be able to perform a direct update to 5.1.0-2871. You will first have to install all the intermediate updates, i.e.: 5.0.0-1643 then 5.1.0-2871.

To know the update orders, you must consult the “Upgrade Notes” section of the Release Notes of the versions you must install:

Preparing the update files

If you followed the beginning of the guide, you will have noticed that I had uploaded in advance 2 additional versions of HYCU:

Otherwise, for those who missed it:

  • Check the box “I agree to the HYCU…” and click “Continue”:

  • Click on “Download .qcow2”:

Once you have downloaded the qcow2 image from HYCU, you now need to transfer it to your Nutanix cluster.

To do this, connect to the Prism Element of your Nutanix CE cluster and go to “Settings > Image Configuration”:

Click on “Upload image”, fill in the form and select the previously uploaded image:

Click “Save” to start the transfer and wait until your image is processed by the cluster and is indicated as “ACTIVE”.

Installing updates

Once you have finished preparing your update files, log in to the HYCU interface, and click on the cogwheel at the top right:

We’ll start by pausing all controller activity so that the updates can run smoothly. Click on “Power options”:

Select “Suspend All” and click “Save”. Then go back to the “Setting” menu in the cogwheel and then click on “Software Upgrade” to display the list of available updates:

Select the update you want to install and click “Software Upgrade”:

A message alerts you that the backup jobs currently running will be canceled, click “Yes”:

The system will log you out during the update. Wait about ten minutes before logging back in:

Once the update is complete, log back in and perform the following updates:

When your HYCU controller has reached the target version, reconnect to the interface then go to the settings at the top right, then to “Power Options”:

Select “Resume” to return your HYCU controller to normal operating mode and click “Save”.

On your Nutanix cluster, you will then find the old versions of your HYCU controller:

You can delete them after some time if you don’t have any problems with the version currently in production (remember to update the name of the virtual machine if you put the version in it like me!).

Read More
nutanix hycu

Now that the Nutanix cluster is added to the HYCU software, we need to add the backup target to which the files will be sent.

Adding a SMB backup target

To add a backup target on HYCU, go to the left side menu and click on “Target”:

Then click on “Add” at the top right to launch the target addition wizard:

Then, select the type of target you want to add on HYCU, then click “Continue”. In my case, I kept it simple with an SMB share on the Synology but you are spoiled for choice (NFS, SMB, Nutanix Objects, iSCSI, S3 storage…):

Then enter a name, a description if you wish, and the number of simultaneous backups then click on “Next”. In my case, I limited myself to 2:

Then provide the account information to access the SMB share that will be used as a target. In my case, I need to provide the username, password, server IP address, and shared folder name:

Once the information is correctly entered, click on “Save”. Your backup target now appears in the list of targets, ready to receive backups:

Backup target configuration is complete, my HYCU controller is ready to backup my data.

Read More
nutanix hycu

After deploying the HYCU controller and initializing it, you need to add your Nutanix cluster as a source of virtual machines to backup.

To add a Nutanix cluster on HYCU, you need to provide an account with “Cluster Admin” rights on Nutanix. If you want to do things properly, you should create a service account that is dedicated to this use rather than using the “admin” account of the Nutanix cluster.

I will show you how to create the service account on Prism Element.

Creating the service account on Prism Element

The first step is to connect to the Prism Element of your Nutanix cluster and go to “Setting > Local User Management” and click on “New User”:

Fill in the fields with the desired information and click “Save”:

It is imperative that the “Cluster Admin” and “Backup Admin” boxes are checked! The user is now created, you must now return to HYCU to continue adding the Nutanix cluster:

Creating the service account on Prism Central

The second step is optional and is only necessary if your cluster is registered on a Prism Central. Log in to the Prism Central of your Nutanix cluster, then go to “Admin Center > IAM > Identities” and click on “+ Add Local User”. Fill in the fields with the desired information and click on “Save”:

The user is now created on Prism Central, you now need to assign the correct access rights:

Go to “Admin Center > IAM > Authorization Policies”. Click on “Create Authorization Policy”:

On the page that appears, start by renaming the policy and select “Cluster Admin” in the field provided for this purpose (type “cluster” to do a search) then click on “Next” at the bottom right:

Leave the default selection and click “Next” at the bottom right of the page:

Add your previously created user to the policy and click “Save” at the bottom right of the page:

The user is now created on Prism Central and Prism Element, you must now return to HYCU to continue adding the Nutanix cluster:

Adding the Nutanix cluster on HYCU

In the “Settings” menu, click on “Sources” to open the menu for adding a backup source:

Then click on “New” to start the cluster adding process:

In the window that appears, enter the URL of your Prism Element, the username and password of the HYCU account previously created and click “Next”:

Then enter the URL of your Prism Central, the username and password of the account previously created and click on “Next”:

If you have completed all of the previous steps correctly, you should see a message like “Validation successful”:

Your Nutanix cluster is now added to your HYCU backup solution and appears in the list of sources:

Read More
nutanix hycu

In the previous blog post, I created and started the HYCU virtual machine. Now let’s move on to the initial configuration of the Backup Controller.

Initializing the HYCU backup system

To start the initialization of the HYCU backup controller, you need to connect to the virtual machine via the Nutanix console. Connect to your Prism Element interface, go to “VM”, right-click on the virtual machine you just deployed and click on “Launch Console”:

A new window will open and you should see the initialization startup window. Select “HYCU Backup Controller” from the list and validate:

On the next screen, you must now enter all the network configurations, namely:

  • Host name of the virtual machine
  • Its IPv4 address
  • The associated subnet mask
  • The default gateway
  • The DNS server
  • Possibly, the domain

Once all the information is entered, validate to launch the initialization of the backup controller:

A little less than 10 minutes later, the initialization will be complete and you will be able to access the solution’s web administration console at the address https://HYCU-IP-ADDRESS:8443:

The default login and password are: “admin” for the login and “admin” for the password, to be changed quickly for obvious security reasons:

You are now connected to the HYCU web interface, we can now move on to the basic configuration:

Basic configuration of my HYCU controller

After finishing deploying the solution, there are some basic configurations to be done to make our system fully operational. I detail some steps here, others not because the article is adapted to a use in lab mode!

Changing the password

We will start by changing the default password of the admin account which is currently “admin”. To do this, go to the top right of the interface, click on the connected username “admin” and in the menu that appears, click on “Change Password”:

Enter the old password, the new password twice and validate:

Checking the license level

Before continuing, let’s check the license level of our installation. To do this, click on the gear at the top right of the window to display the drop-down menu, then click on “Licensing”:

If everything is OK, you should now have a valid “Free license” type license:

Bandwidth Throttling Configuration

Working from home most of the time, I planned to schedule my backup slots between 8pm and 7am. But since I’m also a gamer, there’s no way I’m going to crush my network bandwidth during my sessions… So I set up a bandwidth limitation. In the settings (cogwheel), in “Networks > Throttling”:

Then, in “Throttling Windows”, I was able to enter a limitation range named “Gaming Hours” which extends from 8 p.m. to 1 a.m.:

And then I added a throughput speed limitation to 1MiBps:

Additional configurations

Among the additional configurations that can be done but that I will not detail here because it is not in place in my lab, there is in particular the AD authentication part:

And the email notifications part:

Read More
nutanix hycu

Today, I will present you the method of deploying the HYCU backup solution on my Nutanix AHV cluster.

In the previous article, I presented you the prerequisites necessary for installing the solution, including sending the HYCU installation files to the Nutanix AHV cluster. At this stage, you should therefore have the desired version of HYCU available on your cluster:

In my case, I have deliberately placed 3 different versions of the software in order to be able to show:

  • the deployment of the solution
  • the upgrade with upgrade path

Sizing

Before proceeding with the installation, it must first be sized according to our needs. For this, HYCU gives indications on VM sizes depending on the quantity of virtual machines to be backed up:

In my case, having less than 50 virtual machines to backup, I will go for the smallest size:

  • 8 vCPU
  • 8Gb RAM
  • 32Gb storage

Now that my VM is sized, let’s move on to its deployment.

Deploying the HYCU controller

To deploy the HYCU VM, you need to connect to the Prism Element, go to the “VM” menu and click on “Create VM”. In the window that appears, I give it a name and move on:

I enter the values ​​retained during dimensioning in the “Compute Details” section:

And then I add the first disk of type “DISK” as “Clone from Image Service” and select the image I previously loaded on my cluster “hycu-4.9.0-5310”:

I then add a second disk of type “DISK” this time, in “Allocate on Storage Container” since it is a blank disk of 32Gb that I place on the default storage container:

Finally, I assign a network card to my virtual machine on the subnet of my choice:

My virtual machine is now deployed, I can start it:

My next blog post will detail the initial configuration of the HYCU virtual machine which will allow to finalize the system initialization and access the solution administration interface.

Read More
nutanix hycu

In my previous article, I introduced you to the HYCU backup solution. I will now describe my deployment environment and explain how to retrieve the solution’s installation sources.

Deployment environment

My deployment environment is as follows:

  • Nutanix CE2.1 cluster to deploy and as a source for backups
  • Synology NAS as a destination for backups

This is enough to test the solution and simulate a real production environment.

I have already set up a share on the Synology NAS to receive the backups and I have made sure that the Nutanix cluster, the HYCU VM and the Synology NAS could communicate without any problem.

I will see later if I can simulate an additional S3 type location to simulate an externalization of data in “Archiving” mode.

Let’s now move on to recovering the files needed for the installation.

Solution Compatibility

In terms of compatibility, here are the main elements to keep in mind on the scope that interests us:

  • Nutanix AOS 6.5, 6.8 and 6.10
  • Nutanix Files 4.4 and 5.0
  • Nutanix Objects, Amazon S3, Wasabi
  • VM Windows Server 2016, 2019, 2022
  • Linux

I invite you to consult the compatibility matrix available on the HYCU Support site to learn about all the HYCU compatible platforms: https://download.hycu.com/ec/v5.1.0/help/en/HYCU_CompatibilityMatrix.pdf

Retrieving installation images

To retrieve the images, you must go to the publisher’s website and request a trial license: https://www.hycu.com/solutions/data-protection/nutanix#getForm

There are a few fields to fill in, a person from HYCU will then contact you by phone (so provide a number on which you can be reached!) to ask you what your motivations are.

Once all the prerequisites are filled in, HYCU will provide you with a download link that will allow you to retrieve the software installation image in qcow2 format, ready to be imported into your Nutanix cluster.

Transferring images to the Nutanix cluster

Once you have downloaded the qcow2 image from HYCU, you now need to transfer it to your Nutanix cluster.

To do this, connect to the Prism Element of your Nutanix CE cluster and go to “Settings > Image Configuration”:

Click on “Upload image”, fill in the form and select the previously uploaded image:

As this will be a prerequisite for future operations on your HYCU, I invite you to get into good habits right away and name your image according to the HYCU-VERSION-BUILD model.

Click on “Save” to start the transfer and wait until your image is processed by the cluster and is indicated as “ACTIVE”.

HYCU official documentation

For the official documentation from the publisher, it is freely available on the HYCU website in PDF format: https://support.hycu.com/hc/en-us/categories/15363454825500-Documentation

No translation other than English, so you’ll have to learn the language of Shakespeare!

There you have it, you now have everything you need to deploy the HYCU controller on your cluster, see you in a future article to find out how to deploy the controller.

Read More
nutanix hycu

In a world where data management is a major issue, companies are looking for efficient, simple and powerful backup and disaster recovery solutions. HYCU stands out as a backup solution specifically designed for hyperconverged environments, particularly Nutanix.

This article is the first of a complete guide on the HYCU backup solution, a guide that you can find with the other guides here: https://juliendumur.fr/en/guides/

Native integration with Nutanix

HYCU is the first backup solution developed exclusively for Nutanix. Unlike traditional solutions tailored to hyperconverged infrastructures, HYCU is designed to fully leverage the Nutanix ecosystem. It integrates directly with Nutanix AHV and Nutanix Files, ensuring optimal data protection without impacting system performance.

With its API-first integration, HYCU is able to align seamlessly with the Nutanix architecture. This allows IT administrators to manage backups and restores from the Nutanix Prism interface, providing centralized and intuitive management. This approach reduces the learning curve and limits operational efforts.

Key Features of HYCU for Nutanix

Unlike traditional solutions that require installing agents on each virtual machine, HYCU is based on an agentless approach, reducing resource consumption and simplifying maintenance. It is able to automatically detect workloads and adapt backup policies based on the defined configurations. This automation minimizes human intervention and reduces the risk of error.

One of HYCU’s strengths is its ability to perform granular (individual files, specific databases) or complete (entire virtual machines) restores in just a few clicks, ensuring rapid recovery in the event of a failure.

HYCU also integrates advanced data compression and deduplication technologies, reducing storage consumption and improving overall backup performance. Native integration of WORM locking also improves the immutability and security of backed up data.

However, HYCU is not limited to on-premises Nutanix infrastructures. It supports hybrid and multi-cloud environments, allowing companies to protect their data on AWS, Google Cloud, and Microsoft Azure. It is also capable of backing up VMWare ESXi environments or SaaS applications.

Unlike complex solutions requiring advanced configurations, HYCU offers a “plug-and-play” approach where setup and operation are accessible even to IT teams not specialized in backup. The intuitive user interface allows administrators to manage the entire backup and restore lifecycle in just a few clicks.

Use cases and benefits

Companies using HYCU for Nutanix benefit from optimized data protection without compromising the performance of their infrastructure. Key benefits include:

  • Reduced operational costs through simplified management and reduced storage requirements.
  • Significant time savings through automated and rapid restores.
  • Improved business continuity with rapid disaster recovery.
  • Regulatory-compliant protection through encryption and data retention features.

HYCU combined with Nutanix environments is a modern and innovative backup solution that is perfectly aligned with the principles of hyperconvergence. In the next article, I will present the different prerequisites necessary for deploying the solution.

Read More
nutanix move

It may happen that you are hosting servers whose operating systems are not supported by Nutanix Move. In these rare cases, you will then have to proceed manually to migrate your virtual machines and you may be faced with post-migration boot issues.

For the demonstration, I chose a really old operating system: Ubuntu 12.04.

This version is not part of the list of systems supported by Nutanix Move for migration and the migration must therefore be done manually:

I have set up a manual migration plan for this virtual machine and I am proceeding with its migration which is going smoothly:

Unfortunately, when starting the virtual machine on the Nutanix AHV side, I encounter a boot problem:

To fix this issue, I shut down the virtual machine, log into my Prism Central, and navigate to the “Compute and Storage > Images” menu:

I click on “Add Image”, select “VM Disk” as the image source and select my Ubuntu12 VM:

I name the disk with an explicit name and click on “Next”:

I leave the image placement option in its default configuration and save:

My disk image will appear in the list of images available on my Nutanix cluster:

I then go back to the “Compute and Storage > VMs” menu and open the control panel of my virtual machine:

The part that interests us concerns the machine’s 2 disks with a virtual disk and a CD-ROM type reader:

The first step is to delete all disks by clicking on the trash icon:

Then, once the 2 disks are deleted, click on “Attach Disk”:

Configure the disk as follows:

  • 1 – Type : Disk
  • 2 – Operation : Clone From Image
  • 3 – Image : select the disk you added initially
  • 4 – Capacity : you can make it any size you want
  • 5 – Bus Type : select PCI

Validate the new configuration of your virtual machine and boot it. The boot problem is now fixed, and the operating system boots perfectly fine:

Welcome to Ubuntu 12.04 LTS (GNU/Linux 3.2.0-23-generic x86_64)
Documentation: https://help.ubuntu.com/ System information as of Thu Sep 26 15:58:58 CEST 2024 System load: 0.0 Processes: 67
Usage of /: 3.5% of 37.68GB Users logged in: 1
Memory usage: 2% IP address for eth0: 192.168.2.137
Swap usage: 0% Graph this data and manage this system at https://landscape.canonical.com/
0 packages can be updated.
0 updates are security updates.
Your Ubuntu release is not supported anymore.
For upgrade information, please visit:
http://www.ubuntu.com/releaseendoflife
New release '14.04.6 LTS' available.
Run 'do-release-upgrade' to upgrade to it.
Last login: Thu Sep 26 15:58:05 2024
nutanix@ubuntu24hv:~$

The main problem encountered when migrating these obsolete systems is a boot issue. By following this method, you should be able to migrate all your virtual machines without any problems.

Read More
nutanix move

It may happen that you host servers whose operating systems are not supported by Nutanix Move. In these rare cases, you will then have to proceed manually to migrate your virtual machines and you may encounter post-migration network issues.

In my example, I deployed on my ESXi an Ubuntu Server machine in version 24.04LTS, an operating system released only a few months ago. It is not yet officially supported by Nutanix Move according to the documentation:

When creating my migration plan, I did not encounter any errors, I was able to validate the options without any problems, in automatic mode and I start it immediately.

Unfortunately, the automatic preparation of the virtual machine fails:

The message is clear, Nutanix Move cannot install the necessary drivers:

Drivers Installation Failed. Driver(s) virtio_scsi could not be installed for kernel 6.8.0-45-generic

So I delete my migration plan, create a new one manually and shut down the virtual machine without running the scripts:

I then start my migration plan to migrate the virtual machine to my AHV cluster and everything goes well:

Once the data transfer is complete, I launch the switch immediately. The server is migrated:

On the Nutanix AHV side, I can clearly see my freshly migrated virtual machine:

I start the virtual machine to check that the migration went well. The VM starts correctly but it does not take an IP address…

This problem is common with recent operating systems. As a general rule, they integrate the modules and components necessary for full support by Nutanix. However, it is common for the configuration of the network cards not to be correctly resumed after migration.

To correct the malfunction, you must open a console on your VM and perform the configuration manually.

We start by retrieving the name of the interface:

nutanix@ubuntu24e1:~$ sudo lshw -class network
[sudo] password for nutanix:
*-network
description: Ethernet controller
product: Virtio network device
vendor: Red Hat, Inc.
physical id: 3
bus info: pci@0000:00:03.0
version: 00
width: 64 bits
clock: 33MHz
capabilities: msix bus_master cap_list rom
configuration: driver=virtio-pci latency=0
resources: irq:11 ioport:c040(size=32) memory:febd1000-febd1fff memory:fe000000-fe003fff memory:feb80000-febbffff
*-virtio0
description: Ethernet interface
physical id: 0
bus info: virtio@0
logical name: ens3
serial: 50:6b:8d:c0:82:7b
capabilities: ethernet physical

Here it is ens3. Now we will modify the network card configuration file:

nutanix@ubuntu24e1:~$ sudo vi /etc/netplan/50-cloud-init.yaml
This file is generated from information provided by the datasource. Changes to it will not persist across an instance reboot. To disable cloud-init's network configuration capabilities, write a file /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
network: {config: disabled}
network:
ethernets:
ens160:
dhcp4: true
version: 2

Correct the “ens” line with the correct name of your network card and save the file. Apply the configuration:

sudo netplan apply

That’s it, the machine retrieves an IP address.

You get the idea, my example is based on Ubuntu but reproducible on other recent Linux distributions, as long as you adapt the commands to the operating system.

Read More
nutanix move

Now that everything is ready, it is time to migrate the virtual machines from the old Hyper-V and ESXi clusters to the new Nutanix AHV cluster using the migration plans previously created.

The different states

A migration plan can be in different distinct states depending on the stage of the migration:

  • Not Started: You have created the migration plans but have not yet started them
  • In Progress: The migration plan is launched, the data is starting to be replicated.
  • Ready to Cutover: The data migration is complete, Nutanix Move continues to synchronize the changes, the virtual machines are waiting to be switched to the target cluster.
  • Paused: You have paused the process for some reason. The data migration is suspended.
  • Failed: Error during the process of preparing the machines in general. The anomaly must be corrected in order to resume the operations.
  • Completed: The virtual machines that have been successfully migrated.

Starting migrations

If you have planned to start one of your migration plans like me, you should already have virtual machines in “Ready to Cutover” status.

This means that they are ready to complete their migration.

For other pending migration plans, you need to start them manually. To do this, check the box in front of the migration plans you want to start, click on the “Action” menu at the top of the list and click on “Start”:

The migration plan starts to execute:

If you followed all the steps correctly, the migration plan should go smoothly. You can track the progress of the plan on the corresponding line, and of the virtual machines in the boxes at the very top:

By clicking on the “2 VMs” in the banner, you will have a step by step guide for each virtual machine:

You can get more details on the operations carried out in the “Events” menu at the top right of the interface:

Synchronizing the data with the new cluster is the longest step of the process and will depend on the volume of your virtual machines.

The cutover

The cutover is the operation that will allow you to finalize the migration from the old cluster to the new one.

You can only perform a Cutover on virtual machines that are in the “Ready to Cutover” state:

To check the status of the virtual machines and proceed with the cutover, click on the “2 VMs” in the “Ready to cutover” frame:

You will then have the list of VMs ready to switch to the new cluster. You can do them all at once, or one by one, it doesn’t matter. It’s up to you. I will migrate Ubuntu_4 by checking the box at the beginning of the line and then clicking on “cutover”:

Validation is required to start the process:

The failover process only takes a few minutes during which Nutanix Move will:

  • Power off the VM
  • Create a final snapshot
  • Synchronize it with the target cluster
  • Create the target VM
  • Clean up the source VM (disconnect network cards)
  • Delete all snapshots created by Move
  • Consolidate the virtual machine disks
  • Clean up the target VM

The migration status for this virtual machine then changes to “Completed” and I find it on my Nutanix AHV, started and functional:

The virtual machine is successfully migrated, I just have to do all the others.

Read More