NAKIVO Backup & Replication v7.5 – Installation

This part of the NAKIVO Backup & Replication review I highlight the installation and basic configuration.

For the installation of NAKIVO Backup & Replication you have several options. NAKIVO Backup & Replication can be installed as:

  • Windows or Linux installation package
  • Virtual Appliance for VMware (OVF)
  • In the Amazon AWS cloud
  • Directly installed on NAS devices such as QNAP, Synology and NETGEAR

In my test environment I installed NAKIVO Backup & Replication as Virtual Appliance (VA) on my VMware vSphere 6.7 environment. This is the latest available version of VMware vSphere when writing this blog. The installation of the virtual appliance can be deployed using the vSphere Client (HTML5) or the vSphere Web Interface.

After specifying the name, ESXi host/cluster, storage and selecting the right network, the VA is ready to be deployed. The appliance uses the following resources as VM:

OSUbuntu Linux (64-bit) Virtual Appliance
CPU2 vCPU
Memory4 GB
Hard Disk 130 GB
Hard Disk 2520 GB (repository)
Network Adapter1

After the deployment the appliance is ready to start. In the console of the Virtual Appliance several settings can be adjusted such as: networking, security (SSH and root password), time and services using a menu interface.

The next step is the basic configuration.

Network Attached Storage (NAS) Support

Another test i did is to install NAKIVO Backup & Replication directly on my QNAP NAS. The installation is straight forward. Download the NAKIVO QNAP package and install this using QNAP AppCenter. After the installation you’re ready to perform the basic configuration.

Basic config

After the installation is complete, you can log into NAKIVO Backup & Replication by opening the following URL:

https://<IP_address_of_QNAP_NAS>:4443

The fist time create an user and you’re able to log in. In a three step wizard the following is configured:

  • Inventory: On what virtual/cloud environment are my VMs running (VMware, Hyper-V or AWS)?
  • Transporter: That’s the component that performs the actual backup, replication and recovery as well the data compression, deduplication and encryption of the data.
  • Repository: Where will the data stored.

Inventory

Because I have a VMware vSphere environment, I connect to an ESXi or vCenter Server in the inventory tab.

Transporter

The Virtual Appliance acts as transporter. The maximum load is default 6 concurrent tasks. It’s always possible to add extra transporters when needed.

Repository

For the repository I use the onboard repository (uses hard disk 2) that is attached to the Virtual Appliance. The onboard repository compression and deduplication is configured by default.

Other repositories options are: CIFS, NFS and Amazon EBS.

Updating

When new updates are available they are displayed in the web interface.

For the Virtual Appliance (VA) download the updated installer and upload it the VA (/opt/nakivo/updates) folder. Open the console of the VA and select “Software Update” in the menu. It would be great when the upgrade process of the VA can be automated without any manually actions in feature releases.

This was the last step of the 3 step wizard. After approximately 15 minutes i’m ready with the installation and basic configuration of the Virtual Appliance.  I can conclude the following  after the installation and basic configuration of NAKIVO Backup & Replication:

  • The installation of the Virtual Appliance and NAS option are simple and can be deployed very fast (minutes) without the need of a extra Windows licensing costs.
  • When installing NAKIVO Backup & Replication on a NAS device. there is no need for VM resources or physical hosts which saves money
  • Management via done by Web Browser, no software installation is needed

NAKIVO Backup & Replication v7.5 released

NAKIVO announced today that NAKIVO Backup & Replication v7.5 is out of beta and available. This new version includes the following new features:

  • Support for VMware vSphere 6.7: It’s now officially compatible with the latest version of VMware vSphere.
  • Cross-Platform Recovery: With the Cross-Platform Recovery feature, users can export VM data from VMware and Hyper-V backups into VMDK, VHD, or VHDX format. The exported files can then be used for recovery across different hypervisors, cross-platform VM data migration, long-term archival, or sandbox testing.
  • Advanced Bandwidth Throttling: Allow you to set speed limits during data protection jobs to avoid network overload for example during business hours.
  • Dell EMC Data Domain Boost Support: Dell EMC Data Domain: Integrates with the BoostFS plugin, combining benefits of the VM backup software with the source-side deduplication offered by Dell EMC Data Domain Boost. As a result of this integration, VM backup size can be reduced by up to 17X while VM backup speed can be improved by as much as 50%.
  • NETGEAR ReadyNAS VM Backup Appliance:  can be installed directly on NETGEAR ReadyNAS devices, creating a cost-effective VM backup appliance. The ReadyNAS-based appliance is a 5-in-1 solution featuring backup hardware, software, storage, built-in global data deduplication, and backup-to-cloud functionality. This is already possible with QNAP and Synology NAS devices.

NAKIVO develops data protection solutions for VMware, Hyper-V, and cloud environments such as Amazon and Azure. I was asked to do an independent review of NAKIVO Backup & Replication. In a series of blog posts I will look closer to existing and new features of NAKIVO Backup & Replication v7.5. I’ll will be highlight the following topics:

  • Installation, link
  • Configuration, link
  • Backup, replication and cross platform recovery (coming soon)
  • Editions and licensing (coming soon)
  • Conclusion (coming soon)

More information can be found here:

  • NAKIVO VMware Backup, link
  • NAKIVO Hyper-V Backup, link
  • NAKIVO AWS EC2 backup. link
  • NAKIVO Backup & Replication v7.5 full-featured trial download, link
  • NAKIVO Backup & Replication v7.5 release notes, link

 

Quick Tip – PowerCLI Invalid server certificate

When trying to connect with PowerCLI to a vCenter Server Appliance the following error occurred:

Connect-vIServer : 18-7-2018 13:20:10 Connect-VIServer Error: Invalid server certificate. Use Set-PowerCLIConfiguration to set the value for the InvalidCertificateAction option to Prompt if you’d like to connect once or to add a permanent exception for this server.

As stated in the error, the Set-PowerCLIConfiguration command can be used to ignore the certificate check using the following syntax:

Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -Confirm:$false

After this command you’re able to connect to the vCenter without the certificate error.