Veeam Backup & Replication 9.5 Install – Back to Basics.

Sometimes it is good to go back to basics, somethings change between different versions of software and the installation process isn’t always the same. Sometimes, you may have never installed that piece of software before, but the only installation guide is 3 versions in the past and they have since introduced the need for IIS for a new web portal or something. So here we go in the first post of my new Veeam series “How to install Veeam Backup and Replication” 

  1. Download the latest Veeam VBR ISO from the support download page. 
  2. Depending on version downloaded, you may need to extract the ISOs from the ZIP
  3. Mount the “VeeamBackup&Replication” ISO and open the setup.exe
  4. Click the install icon for Veeam Backup & Replication.
  • Read and Accept the EULA (You can’t proceed if you don’t agree) 
  • If you have a license file, attach it. Otherwise, you will get 30 days free trial
  • Choose your components to install. 
    • Veeam Backup & Replication– This is the main application for configuring and running backup & replication tasks.
    • Veeam Backup Catalog– Used to index the files into a GuestOS backup file for easy restoration. 
    • Veeam Backup & Replication Console– The console is the GUI used to perform tasks and configure Veeam Backup & Replication. 
  • The System Configuration check is used to ensure the correct components are available and installed ready for Veeam B&R to install and configure.
    If there are components showing as Failed, click on the “Install” button to get them installed.  
  • One installed, re-run the check and ensure each component passes. Click “next”. 
  1. Review the default configuration, this includes directory locations, ports and SQL instances. You can select “Let me specify different settings” if you need to make any changes. Click Install to continue. 
  • Wait until installation completes. The installation will take approx. 10 minutes, and if there is an update as part of the install, you will see this occur towards the end of the process. 
  • You will be notified once completed. 
  • Double click on the Veeam icon on the desktop to open the console and put in your Username and password and click connect.
  • By default, the Component update will open up and require you to run the update on any components that require it. They will be listed. Select and apply the updates.
  • Under “Inventory” > “Virtual Infrastructure” > select “ADD SERVER” > Select type of server (in this case, VMware vSphere). NB:You will need to run this process before you can set up your proxies.
  • Input your vCenter (or host) details for Veeam to connect to. 
  • Add your server credentials into the credential manager. 
  • Trust the certificate if it is Self-signed. Please see KB2806 regarding 9.5U3 self-signed Cert bug. 
  • Confirm settings are all correct and click “finish”. 
  • Confirm under “Virtual Infrastructure” > VMware vSphere” that you can see your vCenter hierarchy. 
  • Under “Backup Infrastructure” > “select Backup Proxies”

  • Add in your proxy server’s IP/hostname and a description
  • Add your credentials for the proxy server, or reuse pre-configured.
  • Wait for components to all install. 
  • Confirm the Proxy service details
  • Once you click “finish”, you will return back to the VMware Proxy screen, here you will be able to set your Transport Mode and Datastores. 
  • Select “Choose” for Transport Mode. This will show you a number of options with descriptions to help you choose the correct transport mode to meet your infrastructure requirements. If unsure, select Automatic Selection.
  • Once you continue on, you will have the opportunity to set up traffic rules where you can create bandwidth restrictions. Here you can get granular and create policies for certain IPs. 
  • Once you have finished setting up your proxy, you will then need to set up your repository for storing your backups and/or replications. Select “Backup Repositories” and Set up a new repository. Start off by giving your repo a name. 
  • Veeam offers support for a number of different types of repositories. Select the best option for your infrastructure. (This tutorial will just be a Windows Server.) 
  • Under “Server” choose the repository server from the list or click  “Add New…” server. Once added click the “Populate” button to see the capacities and free space available. Once identified, select the disk you want to use. 
  • In your Repository settings, you can setup the path for which you want your backups to go to. Once set, click the “Populate” button again. Veeam also offers Load Control to assist with your bandwidth and disk performance for your backups, use and adjust as required. 
  • With Windows Server 2016, Microsoft introduced ReFS, their new volume format that allows for greater capabilities. Veeam acknowledges these abilities and advises you of the benefits of using ReFS over NTFS.  *Proceeding will not prevent you from using the Datastore. NB: ReFS is reasonably resources heavy.
  • Under Mount Server, you can set which server will take the load when mounting a restore point with Instant VM Recovery, SureBackup or On-Demand Sandbox. If you have the ability to provide write caching for the mount server, you can enable vPower NFS Service to assist with those mount points.
  • Once all configured, the review stage will confirm if any of the additional components will need to be installed on the new Backup Repository. Once confirmed, you can apply and let Veeam set up the repository. 
  • During the apply process, you will be able to confirm all steps completion. 
  • Once your infrastructure is configured, it is down to business and time to test and create your first Backup job. Under “Backups”, Right click and Select “New Backup Job.” Set a Name and then select your Virtual Machines you would like to backup.  
  • Click recalculate to ensure the total size is updated to reflect the size of the disks to backup. You can also exclude objects from being backed up. 
  • Select your proxy, if you have a Proxy server setup, then choose that one. Otherwise, if you did not setup a proxy earlier, you can use VMware as the Backup Proxy, however this will be a slower process. 

  • Select your Repository for the backup job. In this screen, you can also set the amount for restore points you want to keep and any advanced settings such as additional scripts, Email notifications, backup modes (Incremental, Active Full, etc.) etc. 
  • The Guest Processing page is used to configure the backup job to leverage Application Aware processing and also file indexing and exclusions, and much more.
  • The schedule is fairly self-explanatory. Here you can configure how often the job will run and how many retry attempts before failing the job. 
  • Once all settings have been configured, apply the configuration and if appropriate, Run the job once created. 

  • Watch the progress and if there are any errors, adjust your components where required. 

Rubrik Full Bare Metal Recovery

Recently I wrote a post on Rubrik’s latest major release, 5.0 Andes. That’s 5 major releases since the very beginning in January, 2014 and shipping the first Brik in November of the same year.  Much like the appliances themselves, that is just an incredible speed to get up and operational to send onsite to a customer! You can check out the full timeline here.


I do however want to dig a little bit deeper into some of the items that were released as part of the 5.0 announcement. There were a number of things I had already mentioned, but for this post I want to go further into the Windows Bare Metal Recovery.

So why do we want to deal with physical servers, isn’t everything virtualized? Well, no. Not everyone’s environments are virtualized as there are many reasons why an enterprise may need to continue to run physical machines for licensing or hardware requirements,  and it is imperative that they are backed up accordingly and even more-so easily recoverable in the event of a failure.

Rubrik have now met this need with their full Windows Bare Metal Recovery (BMR) feature as part of the Rubrik 5.0 Andes release, backing up at block level while ensuring even the MBR/GPT partitions are secured. BMR isn’t new to Rubrik, but in the past it started only protecting file sets and files, in 4.2 it was able to protect volume partitions, however, now in 5.0 Rubrik offer FULL BMR by introducing the Volume Filter Driver (VFD) which can be installed optionally to work with the Volume Shadow Copy Service (VSS) and is used for Change Block Tracking (CBT) to decrease backup times.

On first run, the Rubrik Backup Service (RBS) will capture a Crash-Consistent Volume-based snapshot and backed up onto the Brik and is stored as Virtual Hard Disk v2 (VHDX) which makes it easily available for P2v. Once captured, then incremental snapshots are taken with the VFD checking and creating a bitmap of changed blocks to ensure faster backup windows.

The ease of backup is incredibly simple, and recovering from a disaster is just as good. You will need to use the Rubrik WinPE Tool to assist in making you WinPE boot image, but once created, you can then boot your target system into the PE. This environment will allow you to log in and mount the samba share and kick off the restore PowerShell script. BMR also support Live Mount which will allow you to mount your required volume snapshot that you want to restore from. As the first part, the script will obtain and prepare you disk layouts prior to copying down your boot partitions and data. Once the restore is completed, reboot and then you can login and confirm that all the volumes are intact and all data is there and accessible. If you are migrating to a different physical tin, then sensible target hardware needs to be considered, however there is no requirement to match the original source hardware.

One last feature of the 5.0 release is the ability to migrate from a physical machine. There are 3 options for migration;

  • P2V: Migrate from physical to virtual, either VMware vSphere or Microsoft Hyper-V
  • P2P: Migrate from physical to similar or dissimilar physical hardware
  • P2V: Migrate from Physical to the cloud, whether it is Microsoft Azure or AWS

It really is just that easy to do and those who are still bound by physical servers can breathe again knowing that Rubrik can take care of their Full BMR needs, as well as being able to meet the Enterprises’ requirements of off-site long term storage by pushing to the cloud.