Nakivo Backup and Replication v10 released with support for vSphere 7

Nakivo Backup and Replication released last week version 10. I personally use Nakivo Backup and Replication in my lab environment because it can be installed on my NAS device. This saves me hardware resources of the backup VM (appliance or Windows/Linux) and the deployment is super fast.

In version 10 of Nakivo Backup and Replication the following new improvements are added:

  • VMware vSphere 7 support. vSphere 7 support for Nakivo Backup & Replication. This is the latest version of VMware vSphere when writing this blog post.
  • User Interface Enhancements. The user interface has a new facelift to improve the experience with the product.

  • Physical Machine Recovery to VMware (P2V). To protect mixed physical and virtual IT environments, Nakivo Backup & Replication offers the Physical to Virtual Machine Recovery feature.
  • Backup to Wasabi Hot Cloud Storage. You can create backup repositories in Wasabi buckets for backing up and storing virtual and physical machines.

  • Linux Workstation Backup. Perform app-aware, incremental backups of Linux workstations running Ubuntu 18.04 Desktop and 20.04 Desktop. Quickly recover entire workstations or restore individual files and objects directly from backups.

Other improvements are:

  • Application permissions for Microsoft 365 accounts have been updated. Make sure you make the necessary changes to prevent backup and recovery jobs from failure. Refer to Obtaining Microsoft 365 credentials (item 10) for details.
  • CentOS v7.0-7.6 support
  • Improvements for Backup to Amazon S3

The release notes can be found here: link and a free trial can be found here: link.


Quick Tip: Disable memory warnings on VMs with NVIDIA GPU profiles

When using PCI passthrough devices such as for example NVIDIA GPUs with VMware vSphere and configure the VMs with a GPU profile, the full memory is reserved (100% Memory Active). When the VM is active, a red “Virtual Machine memory usage” alarm is displayed in the vCenter for every VM.

I see this behavior in a lot of  VDI environments with PCI passthrough GPU cards. Customers I work for ask me to disable this annoying alarm. This can be easily done in the vSphere Client by disabling the “Virtual machine memory usage” alarm:


When using PowerCLI this can be done with the following command:

Get-AlarmDefinition -Name 'Virtual machine memory usage' | Set-AlarmDefinition -Enabled:$false

Problems with installing modules from the PowerShell Gallery

Lately, on several Windows Server 2016 servers, I wanted to install a PowerShell module such as VMware PowerCLI.  When trying to install the module  I’ve got the following error:

NuGet provider is required to continue
PowerShellGet requires NuGet provider version ‘’ or newer to interact with NuGet-based repositories. The NuGet provider must be available in ‘C:\Program Files\PackageManagement\ProviderAssemblies’ or
‘C:\Users\Administrator\AppData\Local\PackageManagement\ProviderAssemblies’. You can also install the NuGet provider by running ‘Install-PackageProvider -Name NuGet -MinimumVersion -Force’. Do you want PowerShellGet to install
and import the NuGet provider now?
[Y] Yes [N] No [S] Suspend [?] Help (default is “Y”): Y
WARNING: Unable to download from URI ‘′ to ”.
WARNING: Unable to download the list of available providers. Check your internet connection.

PackageManagement\Install-PackageProvider : No match was found for the specified search criteria for the provider
NuGet’. The package provider requires ‘PackageManagement’ and ‘Provider’ tags. Please check if the specified package has the tags.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\\PSModule.psm1:7405 char:21
+ … $null = PackageManagement\Install-PackageProvider -Name $script:N …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (Microsoft.Power…PackageProvider:InstallPackageProvider) [Install-Pac
kageProvider], Exception
+ FullyQualifiedErrorId : NoMatchFoundForProvider,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackagePro

The required modules come from the PowerShell Gallery. Windows Server 2016 has PowerShell version 5.1 installed and supports TLS 1.0 and TLS 1.1. by default. The PowerShell Gallery has deprecated and discontinuing support for TLS 1.0 and 1.1  as of April 2020! TLS 1.2 is set as default for the PowerShell Gallery.

A temporary fix (that won’t persist) is to add the following line before installing the PowerCLI module:

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

Another way is to add this line to your PowerShell profile. More information about the PowerShell TLS change can be found here, link.