In this guide i will show you how to upgrade Veeam Availability Suite™ v8 to Veeam Availability Suite™ v9 or v9.5.
The installation of a new Veeam v9 or v9.5 instance is almost the same with the exception of that you need to create a new database.
Before starting on the guide a quick recap on some nice new features of Veeam 9.
Veeam 9.5 added more features.
Below are features of v9.
- Scale out Repositories
- integration with EMC snapshots
- Veeam Cloud Connect — Now with replication
- Direct NFS Access
- On-Demand Sandbox™ for Storage Snapshots
- Backup from NetApp SnapMirror and SnapVault
- Veeam Explorer for Oracle
- Standalone Console
- Remote Office/Branch Office (ROBO) Enhancements
- Advanced Tape Support
New Storage Features and enhancements:
The Veeam® Availability Suite™ v9 has tons of enhancements and new features, but improvements around primary and backup storage will surely be one of the biggest parts of the next release.
The new Scale-Out Repositories is awesome!
The first new feature is something i waited a long time for personally, and i suspected it was about to come when the first NFS client in v8 (as a part NetApp integration). For a long time, NFS users have felt a bit like second-class citizens in the virtualization world, and the lack of direct access to an NFS storage in VDDK to read data during backup operations was surely one reason to “envy” block storage users. All of the NFS-specific issues VMware backup has had in the past years didn’t help, either. Now, in v9, something similar to Direct SAN processing mode will finally be available for NFS as well. This feature is called Direct NFS. With it, any new Veeam proxy will run a new and improved NFS client to directly access any NFS share exposed to VMware vSphere, supporting both the traditional NFS v3 and the new NFS 4.1 available in vSphere 6. With the complete visibility of single files allowed by the NFS share, NFS users will be able to backup and replicate VMs directly from the NAS array and avoid the need to cross the hypervisor layer for their activities. This will result in faster backups and an even smaller load on production workloads.
A next feature is specific to NetApp.
Added support for NetApp storage arrays in v8, one of the features was the ability to orchestrate NetApp snapshots and create SnapMirror and SnapVault copies directly from the Veeam interface using the existing scheduling capabilities. However, proper backups, with data stored outside of the NetApp infrastructure for optimal availability, were only possible using the primary array as a source. In v9, Veeam add’s more features to the NetApp integration with Backup from SnapMirror and SnapVault. By leveraging these two unique features, users will be able to execute low-impact, storage-based snapshots (also with application consistency, if desired), replicate these restore points to a secondary NetApp array using either SnapMirror or SnapVault and then take true backups of their VMs to an isolated backup storage from these secondary locations. The backup operations will not touch the primary storage at all, which preserves its maximum performance. All the needed I/O will be consumed from the secondary array, making a better use of it instead of it just being a passive target for the copies.
Speaking of storage snapshots, the last feature will make an even better use of them. So far, Backup from Storage Snapshots and Veeam Explorer™ for Storage Snapshots has been able to use storage-level snapshots for backups and restores. But those are not the only types of jobs that Veeam can do. Think about Virtual Labs for instance, which can only run VMs from backup files today. Virtual Labs are essential for most use cases, but also limited on performance for the On-Demand Sandbox™ use case. To address this, in v9, we are introducing On-Demand Sandbox for Storage Snapshots. By using existing storage snapshots in supported arrays (HP, NetApp and EMC running on VMware vSphere), we can create completely isolated, yet full speed, copies of your production environment in just a few clicks for fast and easy testing and troubleshooting. There are many use cases for this technology, but I’ll just give you one example: what about creating a new multi-VM environment, and then, thanks to quick storage snapshots, literally cloning it multiple times to deliver different test environments running at full I/O performance in just a few minutes for your developers? And imagine doing this straight from the storage array, without the need for a backup first. And I’m pretty sure all of you will have a different use case to take advantage of this new feature.
The Guide Part:
Start the setup by mounting the iso image of Veeam Availability Suite™ v9 of v9.5.
VeeamBackup&Replication_18.104.22.1680.RTM (Be aware that 9.5 does not support vSphere 6.5, you need update 1 which is not released yet.)
Before setup wil run it will check if .net has the correct version.
Click on “OK” to install .NET Framework 4.5.2.
After installation you server needs a reboot.
If you run the Backup Enterprise Manager upgrade or install this one first. After that install Backup & Replication.
On the first screen click “Next”.
Accept the term to go on with the installation by clicking “Next”.
In my case i upgrade from v8, Click “Next”.
Browse to your license file and add it, Click “Next”.
Select the appropriated service account and Click “Next”.
With an upgrade select your existing database, when installing a new instance, choose a new database. Click “Next”.
In case of an upgrade like my you will need to click “Yes” to upgrade
Click “Install” to start the installation.
Wait for installation.
Click “Finish” to end the setup.
Let’s log in for the first time in your new and shiny upgraded Veeam v9.
The interface has a small cosmetic change compared to v8.