In order to run Veeam SureBackup for Linux, it requires in prior the creation of a Veeam Virtual Lab and an Application Group. Both have been covered in the previous article showing the requirements and configuration steps. At this point everything is ready to create a Veeam SureBackup job . The SureBackup job includes both configurations and the Veeam SureBackup for Linux verification will start directly from the backup file.
This article covers the simple case of verifying the backup of a single VM based on a Linux Ubuntu. In particular, in this instance there would be only the built-in tests with regard to ping and heartbeat. Since this is a vanilla machine no additional verifications are required. The idea is to show different examples from simple to more advanced. With the next article covering the built-in tests, plus the ones specific to applications (for example Microsoft Active Directory) and custom verification leveraging the Veeam SureBackup roles feature. In that case the plan is to add the configuration for an Oracle Database server. There are plenty of examples and the idea in general is to make sure the virtual machines restored from backup are working as expected. It is an exercise better done and improved whilst things are working rather than in emergency scenarios when virtual machines and pertinent services need to be restored quickly. Veeam SureBackup provides a great help with the option to automate the verification operations and provide reports on what has worked and what has not.
Let’s take a look at the first case using a simple virtual machine running a job for Veeam SureBackup for Linux using a Ubuntu VM.
Backup verification using Veeam SureBackup for Linux
From the main Veeam console and then Backup Infrastructure > SureBackup let’s add a new SureBackup job.
Next we can specify the Virtual Lab created in the previous step. Ideally it is recommended to create Virtual Labs on non Production Hosts or choose the ones with more available resources. Same recommendation goes when creating Virtual Labs specific for running “Sandbox” scenarios covered later on in a separate article.
From the Application Group let’s choose the pertinent one. In this case this group is consisting of a single VM based on Linux Ubuntu. Of course, it is possible to add more VMs for each Application Group and for each one of them use separate settings as defined in the “Role” column. This and other scenarios will be covered in the next article.
In the linked jobs the opportunity to add existing backup jobs with the option to specify how many machines from these backups should be processed simultaneously.
In the settings section the wizard provides the option to specify SNMP trap and email notification settings where to send the report with the final results. In addition, it is also possible to verify the data blocks on the backup file. It’s a very useful feature to make sure there is no data corruption on the block level.
The wizard also includes the option to schedule the verification process. So for example by running this at specific times and even after backup jobs making sure the restores are successful.
And finally a summary showing the main settings.
Now everything is ready to launch Veeam SureBackup for Linux job.
Let’s hit on the Statistic button in the ribbon. At this point Veeam Backup server prepares the Virtual Lab with the chosen configuration as per previous step. The Virtual Lab (Veeam Appliance Proxy) is created and published on the vSphere Host.
If we click on the VM itself from the Statistic window we have a breakdown of the operations the including their status.
Veeam SureBackup for Linux machine verification has completed successfully.
When clicking on Reports it provides the main info and status about the verification steps for heartbeat and ping test. In total the Veeam SureBackup job took roughly 5 to 6 minutes to complete.
The next article will cover the steps to verify a Domain Controller backup along with application verification including Master Role, Global Catalog and DNS.