Hornetsecurity VM Backup v9 with Immutable Cloud Storage


Hornetsecurity released the new VM Backup v9 (formerly Altaro VM Backup) providing the ransomware protection for your backups leveraging immutable Cloud Storage.

VM Backup v9 allows the administrators to add an extra layer of security protecting backup data stored offsite on the supported cloud storage against deletion, overwriting and modification.

Wasabi and Amazon S3 are currently the supported cloud storage solutions you can use to protect your backups making them immutable.

Immutability is the condition where backups cannot be altered in any way and it is generally configured at the software level and backups are protected for an amount of time defined through a retention policy.


VM Backup support both VMware and Hyper-V environments and it is a valid solution to protect your data backup against ransomware attacks or unauthorized accesses.


What's new in VM Backup v9

The new version provides the following new features:


Protection against ransomware

Leveraging Immutable Cloud Storage, backups are now protected against ransomware attacks, deletion, and modification enforcing the security level. The new version currently supports Amazon S3 and Wasabi. Support for immutable Azure storage will be available in the next update.

vm backup 1



  • VM Backup v9 can now manage large infrastructures due to a redesigned backup repository that provides a robust long-term storage and a more efficient use of disk space.
  • In the offsite repository data retention can now run in parallel with other operations.
vm backup 2


VM Backup 9 key features

To protect your business, VM Backup provides all the features required to modern solutions to ensure data integrity and availability.

  • Protection against ransomware - the new feature provided in version 9 to protect your backups against deletion or modification.
  • Augmented Inline Deduplication - allow to reduce storage requirements for backups.
  • WAN-Optimized Replication - allows the administrators to switch the production to replicated VMs offsite with a minimal time by reducing services disruption.
  • Continuous Data Protection (CDP) - the Recovery Point Objective (RPO) can be adjusted up to 5 minutes limiting the data loss in case of a disaster.
  • Multiple offsite backup locations - ideal tool for Disaster Recovery purposes allowing the administrators to store backups offsite and in a cloud environment. Microsoft Azure, Amazon S3, Wasabi are the natively supported cloud storage options. Offsite copies are also protected with the 256-bit AES encryption.
  • Full control – you can manage your Hyper-V and VMware hosts from a single console through an easy and intuitive GUI.
  • GFS Backups - Grandfather-Father-Son archiving model can be used to organize separate backup cycles.
  • Restore - different options are available to restore your backup data, such as Restore VM as Clone, Restore Virtual Disk, File Granular Restore, and Exchange Item Level Restore.
  • VSS Settings - allows to backup supported applications in application-aware mode.
  • Drivers Exclusion - to skip selected disks from backup.
  • Encryption - used to increase security for backups.
  • Sandbox & Verification - backups can be tested and verified to ensure their recoverability.

Supported Hosts

VM Backup v9 provides protection for the following environments:

  • Microsoft Hyper-V - Azure Stack HCI, Windows Server 2008 R2, 2012, 2012 R2, 2016, 2019, 2022, Microsoft Hyper-V Server (Core). VMs can be backed up and restored on/to ReFS and NTFS partitions.
  • VMware vSphere - VMware vSphere 5.5, 6.0, 6.5, 6.7, 7.0 & 8.0. Free VMware ESXi and ESXi 5.0, 5.1 are not supported.


Supported OSs

VM Backup can be installed on the following OSs:

  • Azure Stack HCI, Windows Server 2008 R2, 2012, 2012 R2, 2016, 2019, 2022, Microsoft Hyper-V Server (Core).

Hosts must be in the same LAN and at the same physical site. If you plan to have multiple physical sites, you must deploy a VM Backup instance to each site.

Check out the System Requirements page for additional info.


VM Backup editions

VM Backup v9 comes in three editions:

  • Standard – you can backup up to 5 VMs per host with limited features.
  • Unlimited – an unlimited number of VMs per host can be backed up and Exchange item restore, Deduplication and Boot from Backup capabilities are supported. The Unlimited edition supports also Microsoft Hyper-V Clusters and vCenter.
  • Unlimited Plus – all the Unlimited features are available with the addition of the Cloud Management Console and the Cloud Backup to Azure features as well as Continuous Data Protection (CDP) and WAN-Optimized Replication.

VM Backup is also available as Free edition and allows the backup of 2 VMs per host.



Two types of licensing are currently available:

  • rice based on VMs to protect and not tied to any host. Provides the Unlimited Plus edition.
  • of the number of sockets installed. Standard, Unlimited and Unlimited Plus are the editions available with this type of license.



The upgrade to VM Backup v9 can be done in two ways depending on the version installed in your system.


Version 8

If you have version 8 installed, a direct upgrade from v8 to v9 is supported and all settings will be retained.

Before proceeding with the upgrade, make sure to meet the requirements:

  • You must run at least VM Backup v8.21.x and .NET 4.8 is required.
  • If your license uses the Support & Maintenance Agreement, you must upgrade your license key since v9 requires a new format.
  • A new set of firewall ports must be opened if you use Offsite Backup Server and Replication.
  • A fresh set of onsite/offsite backups (replication included) will be required.
  • Backup taken by v8 will not be deleted automatically.


Version 5, 6 or 7

If your system is running VM Backup version 5, 6 or 7, a direct upgrade is not supported and you need to perform a fresh installation.


Upgrade VM Backup to v9

Before proceeding with the upgrade, you can take a snapshot of your current VM Backup Server to quickly restore the server in case something goes wrong during the install procedure.

vm backup 3

Download the VM Backup upgrade file from Hornetsecurity website and run the installer.

Make sure .NET Framework 4.8 is already installed in the server otherwise you will receive the following message:

vm backup 4


Install .NET Framework 4.8

In case the application is not installed, download the .NET Framework 4.8 and run the installer. Click Install.

vm backup 5

The installation takes only few seconds.

vm backup 6

When the .NET Framework 4.8 installation has been completed, click Finish to close the window.

vm backup 7

Click Restart Now to complete the installation. The Server reboots.

vm backup 8


Install VM Backup

The installation is pretty quick and requires only few seconds. Run the VM Backup installation wizard.

Accept the EULA and click Install.

vm backup 9

The software is being installed in the system.

vm backup 10

When the installation has been completed, click Launch to run the application.

vm backup 11

Enter the credentials and click Connect.

vm backup 12


Register the Server to CMC

When main Dashboard is displayed, click Connect to Control Panel to register the VM Backup Server to the CMC.

vm backup 13

Click Next.

vm backup 14

Now using your preferred browser, access the URL https://eu.manage.altaro.com then enter your credentials to login the CMC. Click Sign In.

vm backup 15

Select VM Backup application.

vm backup 16

When the CMC opens, the system detects there is an installation in progress. Copy the generated access key.

vm backup 17

Paste the access key to the on-prem VM Backup Server and click Next.

vm backup 18

When the connection has been established, click Register to complete the server registration to CMC.

vm backup 19

The VM Backup installation has been linked to the CMC. Click Close.

vm backup 20

From the CMC console you can now start managing the installation.

vm backup 21

The CMC's Dashboard.

vm backup 22


Configure the VM Backup Server

When the on-prem Server is connected to the CMC, you can proceed with the configuration.

vm backup 23

The VM Backup configuration requires three steps to protect your environment:

  • Add Hypervisor.
  • Configure Backup Locations and Offsite Locations.
  • Configure Backups.


Step1. Add Hypervisor

From the Quick Setup, click Hyper-V / VMware Host. In the example VMware vSphere will be the environment to protect.

vm backup 24

Select VMware vCenter Server and click Next.

vm backup 25

Enter the vCenter Server parameters and click Test Connection.

vm backup 26

When the connection is established successfully, click Next.

vm backup 27

Setup is now completed. Click Finish.

vm backup 28

The configured hosts.

vm backup 29


Step 2. Configure the Backup Location

It includes the configuration of the repository to store backups. Select the Backup Location type (in the example a CIFS share is selected) and click Next.

vm backup 30

Enter the path to the share and the correct Share Credentials to connect then click Test Connection.

vm backup 31

When the connection is established, click Finish to save the configuration.

vm backup 32

The created backup repository.

vm backup 33


Create an Offsite Location

To comply the 3-2-1 backup rule, click the Add Offsite Location button to create an external repository.

vm backup 34

Select the desired Offsite Location (Wasabi in the example) and click Next. Note the two available options to store immutable backups.

vm backup 35

Enter the Wasabi Account Credentials and specify the Bucket Name to use.

vm backup 36

To make backups immutable, set the Enable Immutable backups for Wasabi switch to On and specify the retention in days. If you want to have immutable backups, make sure the chosen bucket has been configured with Object Locking option. Click Test Connection to test if the bucket is reachable then click Finish.

vm backup 37

The create Offsite Location.

vm backup 38


Assign VM to Backup Location

To configure the Backup Job, you need first to assign VMs to protect to the desired Backup Location.

Select the required VMs and drag and drop to the appropriate Backup Location and click Save Changes.

vm backup 39


Step 3. Create a Backup Job

Last step is the creation of the Backup. Select the VMs to backup (make sure the Backup Location has been already defined) and click Take backup to execute the backup immediately.

vm backup 40

Selected VMs are being processed.

vm backup 41

Based on the VMs size, after few minutes the backup complets successfully.

vm backup 42

Backups can also be scheduled by click the dedicated icon or in the Backup Settings section.

vm backup 43

Select the VMs to protect and drag and drop to the desired Backup Schedule. Click Save Changes.

vm backup 44

Click the pencil icon to customize the Backup Schedule configuration.

vm backup 45


Backup Offsite

From Backup Location section, select VMs to backup offsite and drag and drop selected VMs to the previously create Offsite Location.

vm backup 46

Click Proceed.

vm backup 47

Select VMs are assigned to the specified Offsite Location. Click Save Changes.

vm backup 48

Offsite copies require a Master Password for VMs configured with encryption. Enter the password and click Save.

vm backup 49

You are now prompted to enter the credential for the authentication. Click Proceed when done.

vm backup 50

Now access the Offsite Copies section, select VMs to store offsite and click Take Offline Copies. If you have a large amount of data to copy over WAN and the available bandwidth is slow, you can perform the Seed to Disk operation by storing the full backup to Disk and send the disk to the provider if this service is supported.

vm backup 51

Offsite Copies are being processed.

vm backup 52

Based on the VMs size, after some minute the backup completes successfully.

vm backup 53

Checking the Wasabi bucket, we can see the stored backups.

vm backup 54



VM Backup provides different options to restore backup data:

  • Restore VM as Clone - a VM can be restored from the backup to a new location with a new name.  Because the source VM is not deleted, make sure the NIC card is not connected to avoid IP conflicts.
  • Restore Virtual Disk - a virtual disk can be restored directly from the backup.
  • File Granular Restore - files and folders can be restored directly from the backup without restoring the entire VM.
  • Exchange Item Level Restore - individual items from the Exchange Databases inside the VM can be restored granularly.
  • Boot From Backup - a VM can be booted directly from the backup providing a reduced RTO.


Restore a VM

Go to Restore section and select the desired restore option. In the example the Restore VM as Clone is selected.

vm backup 55

Select the repository where the VM backup to recover is stored and click Next.

vm backup 56

Select the VM to restore and click Next.

vm backup 57

Specify where the VM should be restored. Click Restore to proceed.

vm backup 58

The restore progress can be monitored from the Dashboard.

vm backup 59

Selected VM has been restored successfully.

vm backup 60



From the Dashboard you can have a global overview of your VM Backup infrastructure.

vm backup 61

The overview of your backup environment can also be verified also from the CMC.

vm backup 62


Apply the license

Although the trial is valid for 30 days, you need the license to keep protecting your environment.

Go to License section and select hosts to license. Click Assign License to.

vm backup 63

If you already have the license key available, click the link Click to add license.

vm backup 64

Paste the received license key and click Add License.

vm backup 65

When the correct license has been applied, the License Manager displays the license status.

vm backup 66

Hornetsecurity VM Backup v9 is a complete backup solution that provides several features useful to safely protect your environment.

The new capability to make offsite backups immutable enforces the security for the business data and provides a strong protection against ransomware.

Hornetsecurity VM Backup v9 is available to download as 30-day trial for testing purposes.


Leave a Reply