In case you missed it last week, the Veeam Availability Suite 9.5 (Veeam Backup & Replication and Veeam One combined) is available for download right now.

Both the What’s New documents are available for Veeam Backup & Replication and Veeam One so I am not going to list it all here.

With the new release there is now support for another storage vendor: Nimble! This one is probably the most requested on our forums but besides this it’s a known fact that the people over at Nimble wanted us to work together. I spoke a few times with them at events and they stated they had the need for a proper integration and felt this task was up to Veeam.

If you are looking at upgrading to Windows Server 2016 (or any related application such as Active Directory, SQL Server or SharePoint) make sure you upgrade to 9.5 however keep in mind that the 9.5 release currently does not support vSphere 6.5! This is related due changes under the hood and therefor support is currently planned for update 1 so you might want to hold of on the jump to vSphere 6.5.

Another cool thing about Windows Server 2016 is the new version on ReFS. I am not going to cover these details as Rick Vanover already did this in a blog post but I can tell you it is a big deal and gamechanger for storing Veeam backups.

Personally there are 3 other features in the Veeam Availability Suite I want to highlight.

1. VMware vSphere infrastructure cache

Maintains an in-RAM mirror of vSphere infrastructure hierarchy to dramatically accelerate job start up (Building VM list operation) and user interface responsiveness while browsing a virtual infrastructure.

This approach removes the load from a vCenter Server, making it more available to perform its core infrastructure management duties, and improves backup success ratio in the environments where jobs would often time out or fail due to an overloaded vCenter Server. The cache is maintained up-to-date with real-time updates via a subscription to vCenter Server infrastructure change events.

2. Parallel processing for full VM restore

As the feature title states this restores multiple disks in parallel, similar to the way backup is performed. This technique is automatically used for all disk-based backup repositories (except Data Domain deduplicating storage for which a new improvement has been added by leveraging a custom tailored logic for both backups and restores).

3. Veeam One Scalability

One major improvement is related to Veeam One and are mostly related to under the hood changes but this is a major step forward in terms of enterprise needs. There are 3 improvements towards the data collection engine which achieve this.

Backup data collection mode: In this mode, Veeam ONE collects Veeam Backup & Replication™ data only and skips virtual infrastructure performance data. This allows you to improve scalability of your Veeam ONE server.

Enhanced advanced scalability mode: This mode collects performance metrics that are used in predefined alarms and reports. This allows users to improve scalability of their Veeam ONE server.

Granular performance metrics selection: The enhanced data collection engine now allows users to select individual performance metrics for each monitored object type (e.g. VMs, hosts, datastores), to improve Veeam ONE server scalability.

As a final note make sure to read the release notes for Veeam Backup & Replication and Veeam One before upgrading.

If you have any questions or need a demo you can always contact your local Veeam represent or hit me up on Twitter.


The Veeam Availability Suite v9 (Veeam Backup & Replication and Veeam One combined) is finally here. We have been giving hints about features for the past months and these are now available for you to use and improve your environment and increase availability!

Instead of just listing all the what’s new things I decided to talk about my personal top 5 on new smaller, unannounced features. We have a “What’s new” document afterall.

1. Per-VM backup file chains

Per-VM backup file chains provide a new backup repository option that makes any backup job written to a repository store each VM’s restore point in a dedicated backup file, delivering 10x faster backup performance with multiple write streams by leveraging parallel VM processing.

For me this is the biggest feature because this allows you to leverage your backup storage investment to a maximum. Before v9 a backup job containing multiple VM’s would be stored in 1 backup file (for either full and incrementals). By using the new option Veeam Backup & Replication will store 1 backup file chain per VM (for either full and incrementals).

Combine this with the new Scale-Out Backup Repository and you can use your backup storage to a better maximum compared to before (usage and performance wise). You could even make one job where you add your vCenter or SCVMM cluster, point to to a Scale-Out Backup Repository and let Veeam take care of everything :-). For more information on Scale-Out Backup Repositories I suggest you read this post by Luca Dell’Oca.

This setting is configured by default when using a Scale-Out Backup Repository however when configuring a new backup repository or editing an existing one this is an option which can be found under the advanced button. Also if you change the behaviour on an existing one Veeam Backup & Replication will take care of everything for you.


2. Parallel processing for Backup Copy Job and Tape

With v9, Backup Copy jobs will now process multiple VMs in parallel, like primary backup jobs. This improves the backup copy and retention processing performance due to removing “dead time” between each VM, and will further speed up processing when per-VM backup file chains are enabled on the target backup repository.

As it states this will help you in getting a copy of your backups to disk more rapidly. The best thing about it is that this option is enabled by default so no configuration is needed.

Parallel backups no longer require the creation of multiple media pools. Backup to Tape and File to Tape jobs can now run in parallel even when pointed to the same media pool. Backup to Tape jobs will process multiple backup chains (either from different source backup jobs, or created with a per-VM backup file chain option) and span them across tape drives automatically to significantly reduce your tape backup window.

A big requested feature finally made it into the release. This setting can be configured per media pool while creating or editing it.


3. vPower cache

vPower® engine will now cache recently accessed backup file blocks in RAM, which will help speed up all functionality that relies on Instant VM Recovery™.

This is important for faster recovery (Instant VM Recovery, file level recovery,…) and especially when you are using deduplication storage (such as HPE StoreOnce, EMC DataDomain, ExaGrid,…) as a backup repository. By default every VM has 40 cached blocks (meaning backup block, 1Mb by default).

4. Storage-level corruption guard

Backup files produced by primary backup jobs can now be periodically scanned to identify storage issues, such as a bit rot. Corrupt data blocks are auto-healed by retrieving correct data from the production storage, increasing the reliability of forever-incremental backups and removing the need for periodic full backups.

This is a feature which was already possible on backup copy jobs and has now been made available in the primary job. This is something you should run atleast once a month to guarantee your files to be fine so you can recover from them. As always running SureBackup is also advised.


5. BitLooker

BitLooker™ is Veeam’s unique, patent-pending, advanced data reduction technology designed to further reduce backup file size and replication bandwidth usage by 20% or more. It allows customers to easily find and reduce useless chunks of data congesting their backup storage resources by providing the following three capabilities:

  • Excluding deleted file blocks
  • Excluding swap and hibernation files
  • Excluding user-specified files and folders

BitLooker will even optimize the backup storage usage even better (combined with Per-VM Backup Chains) for any Windows server with NTFS disks. There are 2 options to configure in the interface.

Option 1 is to exclude deleted file blocks which is an advanced option under the Storage tab.

Option 2 is the exclusion of specific user files and folders which can be found under the Applications button on the Guest Processing tab.

What else is there to check out?

Besides the features above there is a lot more in Veeam Backup & Replication v9. Other great things are:

  • Veeam Cloud Connect Replication (easily create a DR plan using a Veeam Cloud Provider)
  • On-Demand Sandbox for Storage Snapshots (run a sandbox with the same performance as your production VM’s)
  • Direct NFS Access (works by default)
  • Veeam Explorer for Oracle (for both Windows and Linux)

For a full list make sure to read the release notes.

As you can see Veeam does it again. We are very happy with the release and again we prove that we are listening to you, building the tools you need.

If you have any questions or need a demo you can always contact your local Veeam represent or hit me up on Twitter.

DELL EqualLogic

DELL released a new SAN Headquarters version, this is an update towards the v2.5 release which is dated back to December 2012. SAN Headquarters 2.6 supports PS Series firmware version 5.0 or higher.

SAN Headquarters enables you to monitor multiple PS Series groups from a single graphical interface. It gathers and formats performance data and other vital group information. Analyzing the data might help you improve performance and more effectively allocate group resources.

DELL EqualLogic SAN Headquarters Version 2.6 supports the following new features:

  • Dell EqualLogic RAID Reliability
    SAN HQ’s RAID Evaluator has been enhanced to analyze the overall effectiveness of your current RAID policy, based on Dell’s baseline recommendations for all members in a group. SAN HQ calculates a RAID policy reliability score, which rates your current storage configuration’s resilience should it encounter a disk failure. You can enter a different RAID policy to evaluate potential reliability improvements. From this data and from recommended best practices, you can make an informed decision whether to change your current RAID policy.
  • Support for Microsoft Windows Server 2012 and Microsoft Windows 8
  • SAN Assist has been renamed to Dell SupportAssist
  • Additional Features / Enhancements
    • New Alert Display Settings on the General Settings page, which allows you to hide all disabled email alerts from the SAN HQ GUI.
    • New alerts for RAID policy reliability reporting.
    • Proactive notification to SAN HQ clients when the SAN HQ remote server is upgraded.
    • Improved initial launch of the SupportAssist Configuration Wizard.
    • SupportAssist Activity Log view now highlights failed/completed activity.
    • SupportAssist configuration now includes timezone information.
    • New Queue Depth column on the All Volumes Summary view.
    • New Volumes Performance report.
    • Configuration report has been enhanced to include network/ethernet ports configuration information.
    • All Groups Hardware/Firmware Summary view and the Hardware and Firmware report have been enhanced to include the new RAID Policy Reliability score and rating.

VMware has released Update 1 for ESXi and vCenter 5.1 which has some major improvements, bug and security fixes. I am very happy to see that we can now start using Windows Server 2012.

What’s new?

  • vCenter Server is now supported on Windows Server 2012
  • vCenter Server now supports the following databases.
    • Microsoft SQL Server 2012
    • Microsoft SQL Server 2008 R2 SP2
  • vCenter Server now supports customization of the following guest operating systems:
    • Windows 8
    • Windows Server 2012
    • Ubuntu 12.04
    • RHEL 5.9
  • vCenter Essentials no longer enforces vRAM usage limit of 192 GB

Some important notes

  1. The following guest operating system releases that are no longer supported by their respective operating system vendors are deprecated. Future vSphere releases will not support these guest operating systems, although vSphere 5.1 Update 1 does support them.
    • Windows NT
    • All 16-bit Windows and DOS releases (Windows 98, Windows 95, Windows 3.1)
    • Debian 4.0 and 5.0
    • Red Hat Enterprise Linux 2.1
    • SUSE Linux Enterprise 8
    • SUSE Linux Enterprise 9 prior to SP4
    • SUSE Linux Enterprise 10 prior to SP3
    • SUSE Linux Enterprise 11 Prior to SP1
    • Ubuntu releases 8.04, 8.10, 9.04, 9.10 and 10.10
    • All releases of Novell Netware
    • All releases of IBM OS/2
  2. Virtual machines that are compatible with ESX 3.x and later (hardware version 4) are supported with ESXi 5.1 Update 1 . Virtual machines that are compatible with ESX 2.x and later (hardware version 3) are no longer supported. To use such virtual machines on ESXi 5.1 Update 1 , upgrade the virtual machine compatibility.
  3. VMware Toolbox: vSphere 5.1 is the last release to include support for the VMware Tools graphical user interface, VMware Toolbox. VMware will continue to update and support the Toolbox command-line interface (CLI) to perform all VMware Tools functions.
  4. Windows Server 2012 Failover Clustering is not supported
    If you attempt to create a cluster for Failover Clustering in Windows Server 2012, and select to run validation tests, the wizard completes the validation tests with warnings, and after that returns to running the validation tests again. The wizard in the Windows Server 2012 guest operating system does not continue to the cluster creation stage.
  5. vSphere 5 Storage vMotion is unable to rename virtual machine files on completing migration
    This issue is resolved in this release. To enable this renaming feature, you need to configure the advanced settings in vCenter Server and set the value of the provisioning.relocate.enableRename parameter to true.

Release notes

For more information check out the official release notes: