Awesome! Veeam Backup & Replication 6.1 released

Today June 4th, Veeam released their state of art VM backup software Veeam Backup & Replication 6.1. This new version includes some powerful new features for both VMware and Hyper-V. Let’s have a look at what’s new!


Version 6.1 includes a new capability for performing ad-hoc backups. In many ways, it functions like a zip utility for VMs. For this reason, it’s called VeeamZIP. Use VeeamZIP whenever you need to:

  • Backup a VM on-the-fly. For example, before making changes to it. Instead of running the regular backup job (which typically contains multiple VMs and a specified number of restore points) or creating a new backup job, simply VeeamZIP the VM.
  • Archive a VM. For example, before decommissioning it.
  • Copy a VM to your test lab, training center, to give to a client, etc.

Veeam Backup Free Edition

Version 6.1 introduces a new free mode. The free mode, called Veeam Backup Free Edition, provides a subset of the functionality in the full (paid) editions of Veeam Backup & Replication, including VM and file recovery. So if you ever need to perform a restore but don’t have access to a Veeam backup server, you can simply download and install Veeam Backup Free Edition. You don’t need a license key, and you can recover VMs, VM files and guest files.

New Console

One of the first things you’ll notice about version 6.1 is the new console. While wizards and dialogs haven’t changed, it’s now easier to get to them. Enhancements include:

  • Use of Microsoft design standards
  • Dynamic nodes
  • Extensibility
  • Instant search

vPower for Hyper-V

Version 6.1 extends Veeam’s patent-pending vPower technology, as well as Instant VM Recovery, to Hyper-V. vPower runs a VM directly from a compressed and deduplicated backup file on regular backup storage. You can run a VM from any restore point (full or incremental), without changing the backup. vPower enables Instant VM Recovery, which lets you restart a failed VM from a regular backup in as little as 2 minutes.

Additional enhancements

Version 6.1 also includes a number of other enhancements, as well as all fixes for version 6.0. The remainder of this document provides a list of the most significant enhancements.

Intelligent load balancing

  • Backup proxy server selection. Intelligent load balancing now uses a Network access mode backup proxy server only when there is no backup proxy server available that can process the VM in Direct SAN or Hot Add access mode. This prevents autodetect from picking a Network access mode backup proxy server from another site.
  • Subnet detection. Network access mode backup proxy servers are now chosen based on their subnet. The selection logic always tries to use a backup proxy server located on the same subnet as the processed host. If no such backup proxy server is found, the first least-busy Network access mode backup proxy server is selected, and a corresponding event is logged in the job’s session log.
  • Excluded disks. Intelligent load balancing now takes into account the VM’s excluded disk settings when picking the best backup proxy server to process the VM.
  • Transformation tasks. The transform process is now accounted for as an active backup repository task. This prevents multiple transform operations from overloading backup storage.


  • Data mover agent priority. To make it easier to use an existing Windows server as a backup proxy server, the data mover agent is now started with BELOW NORMAL priority. This reduces the effect of the data mover agent on other applications and services running on the backup proxy server. The priority is further configurable through the registry setting.
  • System cache tuning. The backup proxy server setup now adjusts low-level Windows system cache settings to avoid a gradual decrease in processing speeds with large backup jobs, as has been reported by some customers.
  • Concurrent job limit. The maximum of 64 concurrent jobs per backup server has been removed.
  • Memory consumption. Memory consumption by the job manager process has been reduced.
  • Backup proxy server replication. Added the ability for the backup proxy server to replicate itself.
  • Deleted VM retention period. The deleted VM retention period no longer affects incremental backups.
  • Shared backup proxy servers and repositories. Backup proxy servers and repositories can now be shared between multiple backup servers. Note: The intelligent load balancing algorithm runs on each backup server and is unaware of any tasks assigned to a backup proxy server or repository by another backup server.
  • Bottleneck analysis. Uses enhanced formulas for calculating proxy and network processing statistics.
  • Disabling inline deduplication. Disabling inline deduplication now disables both target-side (as before) and source-side deduplication. This can improve incremental backup performance when backing up to a deduplicating storage device.
  • Email notifications. Redesigned the default email notification subject.


  • Support for rotating backup storage. Added support for the ForceCreateMissingVBK registry key to v6 backup repositories. When this registry key is set, the backup job will create a new full backup if previous backup files are missing. This registry key is useful if you want to rotate backup storage.


  • Omit replica suffix. You can now configure the replica suffix to be empty.
  • Edit source VM hardware. You can now edit source VM hardware settings (for example, add a new vNIC) without having to restart the replication cycle.
  • Continue replication after failback. You can now resume replication after failback without having to replicate the full VM.

VM Copy

  • Overwrite existing VM files. A VM copy job now overwrites existing VM files in v6 backup repositories. Previously, each run would create a new VM copy.
  • Importing backups. You can now import backups from password-protected CIFS shares.

VM migration

  • Preserve source files. New option to enable preservation of source VM files after successful migration.
  • Reliability and performance. Improved overall reliability and performance of the VM migration process.

File-level restore

  • File-level restore mount. When performed by the user interactively (using the backup console UI), the Windows file-level restore process now mounts the volumes of the backed-up VM under C:VeeamFLR. This functionality is useful if you prefer to perform file-level recovery with native tools instead of Veeam Backup Browser.1
  • 1-Click File Restore: Added support for restoring very large files.

Windows guest file indexing

  • Support for ReFS volumes. Added support for indexing ReFS volumes (new Windows Server 2012 file system).
  • Status notifications. Removed warning of failed indexing (and application-aware processing) attempts on non-Windows VMs.

User interface

  • View and restore from Windows Explorer. You can now view the contents of any .VBK file or initiate a restore by simply double-clicking the file in Windows Explorer (without having to import the backup file first).
  • 24-hour job history. You can now see the results of all job runs in the last 24 hours in a single view.
  • Delete default backup repository. As long as it’s not the only one, you can now delete the default backup repository.
  • Synthetic full and transform progress. Progress of the synthetic full and transform operations is now displayed in the job grid.

Enterprise Manager

  • Datastore view. Added datastore view to the virtual machine selection dialog.
  • Repository selection. You can now change the backup repository when editing a cloned job.
  • Email notifications. Added information about the target VM to the email notification for 1-Click File Restore operations.

Enhancements specific to VMware

  • Hot add. If a VM has multiple disks, hot add is performed once for the entire VM, instead of once for each processed disk, which speeds up VM processing.
  • vPower NFS performance. Removed unnecessary logging to improve vPower NFS performance.
  • Failback performance. Enhanced the virtual disk digest calculation process to improve failback performance.
  • Delete default backup proxy server. As long as it’s not the only one, you can now disable and delete the default VMware backup proxy server.
  • Warnings. The warning message indicating failover to network processing mode has been changed to an information event. Likewise, the warning message about outdated VMware Tools on the processed VM has been changed to an information event.

Enhancements specific to Hyper-V

  • SCVMM 2012. Added support for System Center 2012 Virtual Machine Manager.
  • Localized Hyper-V servers. Added support for localized Hyper-V servers.
  • VMs on backup server’s host. You can now protect VMs running on a Hyper-V host where the Veeam backup server is installed in the parent partition.
  • On-host backup proxy server tasks. You can now customize the maximum number of concurrent jobs on a Hyper-V on-host backup proxy server.
  • Changed block tracking. Added compatibility with certain 3rd party applications (such as antivirus) that previously affected changed block tracking. Also, to keep CSV volumes clean and for better reliability, files containing changed block tracking information are now stored on local host storage.
  • Application-aware and VSS processing. Improved reliability of application-aware and VSS processing.
  • Replication. To prevent replicas from auto-starting upon host reboot, VM auto start options are no longer replicated. Virtual network optimizations and VLANID settings are now replicated.


  • Setup. On modern versions of Windows, automount is now disabled using the correspondingnew primitives provided by the operating system (OS). This change was required because “old-style” automount disabling is deprecated in these OSs and can cause unwanted issues, such as issues with OS patching.
  • Logging. Added current backup log compression when the size exceeds the threshold, as well as the ability to customize log folder and log retention policy.

Looking pretty awesome isn’t it? 🙂

Please visit Veeam website to find out more!


– Marek.Z

Be the first to comment

Leave a reply...