Are Your Backups Worthless? Part 2: SureBackup

Sure-BackupIn part one of this series, we discussed how success notifications from your backup tool of choice can create a false sense of confidence that backup restores will work when needed. We also took a look at SureBackup, a component of the Enterprise and Enterprise Plus editions of Veeam Backup and Replication that performs automated restore testing. As promised, we’re going to dive into each of the SureBackup components. Go grab a cup of coffee and get comfortable, as there’s a lot of information that follows….

 

The Virtual Lab

A virtual lab, created by Veeam Backup, is normally a tool an IT admin would use to perform testing in an isolated environment. For example, a team of developers could spin up a group of SQL virtual machines (VMs) and test code changes without affecting production VMs. Veeam takes this technology further to spin up VMs from a restore to see if they actually work.

Here’s how to set-up a virtual lab in Veeam Backup 7.0 for VMware. Note: the following steps have been pulled directly from Veeam’s support site, sans screenshots.

To get started…

Open the Backup Infrastructure view, select the Virtual Labs node under SureBackup in the inventory pane and click Add Virtual Lab > VMware on the ribbon.

Open the Backup Infrastructure view, right-click the Virtual Labs node under SureBackup in the inventory pane and select Add Virtual Lab > VMware.

 

Step 1. Specify a Name and Description

At the Name step of the wizard, enter a name and description for the new virtual lab. The default description contains information about the user who created the lab, as well as the date and time when the lab was created.

 

Step 2. Select a Host

Selecting an ESX(i) Host for VM Backups Verification

To select an ESX(i) host for VM backups recovery verification:

  1. Click Choose to select an ESX(i) host on which the new virtual lab will be created. You can select a standalone ESX(i) host or an ESX(i) host being part of a cluster or vCenter Server hierarchy.
  2. For every new virtual lab, Veeam Backup & Replication creates a dedicated folder and a resource pool to which all tested VMs, VMs from the application group and the proxy appliance are placed. By default, the folder and the pool have the same name as the virtual lab. To change the name of the destination folder and/or resource pool, click Configure and enter the necessary names in the Destination Options section.

You cannot create resource pools in clusters with disabled DRS. If the destination host is a part of such a cluster, the Create a designated resource pool option will be disabled in the Destination Options window. See more details from VMware.

You cannot create folders on standalone ESX(i) hosts or ESX(i) hosts that are managed by the vCenter Severs  but are added to Veeam Backup & Replication console as standalone hosts. To overcome this situation, add the corresponding vCenter Server to the Veeam Backup & Replication console.

 

Step 3. Select Datastore

Click Choose to select a datastore on which redo logs for verified VMs should be placed. Redo logs are auxiliary files used to store all changes that take place when a VM runs from a read-only backup. As soon as the recovery verification job completes, redo logs are deleted.

 

Step 4. Set Up a Proxy Appliance

At this step of the wizard, you should configure proxy appliance settings.

  1. To enable automatic recovery verification of VMs, select the Use proxy appliance in this virtual lab check box. The proxy appliance acts as a gateway that provides access from the Veeam backup server to VMs started in the isolated virtual lab. If you do not select this check box, Veeam Backup & Replication will perform only heartbeat tests for VMs during verification. You will only be able to manually test VMs and perform manual item-level restore via the VM console.
  2. To change a name of the proxy appliance, click Configure in the Proxy appliance VM settings section and specify the necessary name. By default, the proxy appliance uses the virtual lab name that you have specified at the Name step of the wizard.
  3. To select a production network in which the proxy appliance should be created, click Configure in the Production network connection section. Specify an IP address for the proxy appliance in the production network and settings of the DNS server to be used. You can choose to automatically obtain an IP address and DNS server settings or set them manually.
  4. If you want to allow access to the Internet for VMs in the virtual lab, select the Allow proxy appliance to act as internet proxy for virtual machines in this lab check box. In the Port field, specify a port for HTTP traffic. By default, port 8080 is used. In the Production proxy field, you can optionally specify an IP address or a fully qualified domain name of an Internet-facing proxy server that VMs should use to access the Internet.

If you assign to the proxy appliance an IP address from the same network where the Veeam backup server is located, Veeam Backup & Replication will automatically add a new route to the routing table on the Veeam backup server. If you assign to the proxy appliance an IP address from a different network, you will have to manually add a new route to the routing table on the router in the production network. If you do not add a new route, tests and application scripts will fail and you will not be able to access VMs in isolated networks.

 

Step 5. Select a Networking Mode

Select the type of network settings configuration. This step differs for virtual labs used for VM backups and VM replicas verification.

Selecting a Networking Mode for VM Backups Verification

Veeam Backup & Replication offers two networking modes for the virtual lab in which VMs from backups are verified:

Basic single-host (automatic configuration). This networking mode is recommended if all VMs you plan to verify, VMs from the application group and Veeam backup server are located in the same production network. In this case, Veeam Backup & Replication will automatically define all networking settings and create the virtual lab on an ESX(i) host.

Advanced single-host. This networking mode is recommended if VMs you plan to verify and/or VMs from the application group are located in different networks. In this case, you will have to manually define settings for isolated networks in the virtual lab. Veeam Backup & Replication will use the specified parameters to create the virtual lab on an ESX(i) host.
If this option is selected, the New Virtual Lab wizard will include additional steps for customizing network settings.

 

Step 6. Specify Isolated Networks

This step is available if you have selected the Advanced networking option at the Networking step of the wizard.

At this step of the wizard, you should create isolated networks to which verified VMs and VMs from the application group will be connected and map these networks to production networks where initial VMs are located.

To add a network:

  1. Click Add.
  2. From the Production network list, select a production network in which a VM from the application group or a verified VM resides.
  3. In the Isolated network field, specify a name for an isolated network that should be mapped to this production network.
  4. In the VLAN ID field, enter an identifier for the created network. In the advanced multi-host virtual lab, VLAN IDs help ensure that the created network is isolated from the production environment. Alternatively, you can manually connect the DVS you plan to use to the isolated network. To learn more, see Advanced Multi-Host Virtual Lab.

You can map several production networks to the same isolated network. The production networks you plan to map to the same isolated networks must have the same network masks and pools of IP addresses for mapping to be configured correctly.

 

Step 7. Specify Network Settings

At this step of the wizard, you should specify settings for every created isolated network and define how production networks should map to networks in the isolated virtual lab.

Communication between production networks and isolated networks is carried out through vNIC adapters that are added to the proxy appliance. A new vNIC adapter is added for every isolated network.

To add a vNIC adapter for an isolated network:

  1. At the Network Settings step of the wizard, click Add.
  2. Select a network to which you want the vNIC adapter to be connected. Specify an IP address that the proxy appliance should have in the isolated network and a subnet mask of this isolated network. Typically, the IP address set for the proxy appliance coincides with the IP address of the gateway in the corresponding production network.
  3. Once you specify the IP address, Veeam Backup & Replication will automatically configure a masquerade IP address for accessing VMs in the virtual lab from the production network. You can change the masquerade network IP address if necessary.
  4. Select the Enable DHCP service on this interface check box and specify settings of a virtualized DNS server if necessary.
  5. Click OK.
  6. To enable communication between isolated networks, select the Route network traffic between vNICs check box. When you select this option, make sure that the IP address of the proxy appliance in the isolated network matches the IP address of the gateway in the production network.

Network addresses for different network adapters should belong to different networks. For example, if the first network adapter has address 192.168.0.1 with mask 255.255.255.0, and the second one — 192.168.0.2 with mask 255.255.255.0, such configuration will not work. In this situation, you need to assign to the second adapter the IP address from a different network, for example, 172.16.0.1.

 

Step 8. Specify Static IP Mapping

This step is available if you have selected the advanced networking option at the Networking step of the wizard.

At this step of the wizard, you can specify static IP address mapping rules to make VMs in the virtual lab accessible from any machine in the production network.

To add a new rule:

  1. Click Add.
  2. In the IP Address Mapping window, specify settings of a new rule:
  3. In the Isolated IP filed, specify a production IP address of a VM that will be started in the virtual lab and that you plan to access from the production environment.
  4. In the Access IP field, specify an IP address from the production network that you want to use to access this VM in the virtual lab. For a static IP address, you should use an IP address from the production network that is not yet allocated to any machine.

For example, the DNS server you plan to start in the virtual lab has IP address 192.168.1.2 in the production network. To set static mapping for the DNS server, in the Isolated IP field, you need to define its production IP address — 192.168.1.2. In the Access IP field, you need to define any unallocated IP address from the production network, for example, 192.168.1.48. After a virtual lab is created and VMs are started in the virtual lab, you will be able to access the DNS server in the virtual lab from the production environment using IP address 192.168.1.48.

 

Step 9. Apply Parameters

Review the parameters of the virtual lab you create. You can go back to any previous step to adjust the parameters. If everything is fine, click Next to create the virtual lab.

Always use Veeam Backup & Replication to modify or delete a virtual lab. If you change lab settings or delete any of its components from outside (for example, using vSphere Client), the lab will be corrupted and its component such as the created vSwitch, resource pool and so others will remain in the virtual infrastructure.

So, that’s it for setting up the Virtual Lab.

“Um…I thought you said that Veeam would do this for me automagically? What’s with all the work?” Well, there are a few reasons for that. First, Veeam doesn’t “know” what your virtual infrastructure looks like, so the above steps help with “describing” the environment to Veeam. Secondly, as mentioned before, a virtual lab can be used for other purposes besides validating a restore.

Having granular control over what a virtual lab consists of provides flexibility and added functionality. On to the next component of the SureBackup toolset:

 

The Application Group

Ever booted up an Exchange server without a domain controller present?  It will stare at you as though you’ve lost your mind.  Veeam understands that a valid restore test requires that dependent VMs be running, so they allow for the creation of an application group. An application group is a group of VMs that have dependencies on each other.  For example, you might want to test a restore of an IIS server that’s providing web services tied to a backend SQL server.  VM dependencies are important to understand, because you can’t test functionality of certain VMs without that understanding.  Let’s return to Veeam’s support site to see how to build out an application group.

Getting started:

To create a new application group, do either of the following:

Open the Backup Infrastructure view, select the Application Groups node under SureBackup in the inventory pane and click Add App Group > VMware on the ribbon.

Open the Backup Infrastructure view, right-click the Application Groups node under SureBackup in the inventory pane and select Add Application Group > VMware.

 

Step 1. Specify an Application Group Name and Description

At the Name step of the wizard, enter a name and description for the new application group. The default description contains information about the user who created the group, as well as the date and time when the group was created.

 

Step 2. Select VMs

At the Virtual Machines step of the wizard, you should add VMs to the created application group. You can add VMs from VM backups or VM replicas.

Veeam Backup & Replication supports mixed application groups. You can add to the same application groups VMs from backups and VMs from replicas. Keep in mind that all VMs from the application group must belong to the same platform — VMware or Hyper-V, and must have at least one valid restore point created by the time the SureBackup job starts.

Adding VMs from VM Backups

To add a VM from the backup to the group, click Add Backup and select where to browse for VMs:

From Infrastructure to browse the virtual environment. Because VMs from the application group are started from VM backups, you need to make sure that VMs you have selected for the group have been successfully backed up at least once by the time you plan to run a SureBackup job.

From Backups to browse existing backups.

 

Step 3. Specify Recovery Verification Options and Tests

After you have added necessary VMs to the application group, you should specify a role, VM startup options and select tests to be performed for each VM in the application group.

To be able to perform tests, Veeam Backup & Replication requires VMware Tools to be installed on the verified VM. If VMware Tools are not installed, the VM will be started but tests will not be performed.
VMs without VMware Tools can still be used as auxiliary VMs that should be started to enable proper work of verified VMs or VM replicas. In this case, you do not need to select any role for such auxiliary VM.

Select the necessary VM in the list and click Edit on the right.

Role settings

On the Role tab, select the role that a VM performs. Veeam Backup & Replication offers the following predefined roles for VMs:

  • DNS Server
  • Domain Controller
  • Global Catalog
  • Mail Server
  • SQL Server
  • Web Server

VM roles are described in XML files stored in the %Program Files%\Veeam\Backup and Replication\Backup\SbRoles folder. You can add your own roles. To do this, you need to create a new XML file and specify role and test scripts settings in it. For details, see Creating XML files with VM Roles Description.

Once you select the necessary role, Veeam Backup & Replication will automatically configure startup options and provide predefined test scripts applicable for the chosen role. You can use these settings or specify custom ones using the Startup Options and Test Scripts tabs.

To verify VMs that perform roles other than those specified in the list, you will have to manually configure startup options and specify test scripts to be run against these VMs.

Startup Options

On the Startup Options tab, specify VM startup setting.

  1. In the Memory section, specify the amount of memory that you want to pre-allocate to the VM on the system boot. The amount of pre-allocated memory is specified in percent. The percentage rate is calculated based on the system memory level available for the production VM. For example, if 1024 MB of RAM is allocated to the VM in the production and you specify 80% as a memory rate, 820 Mb of RAM will be allocated to the verified VM on startup.
  2. In the Startup time section, specify the allowed boot time for the VM and timeout to initialize applications on it.
  3. In the Boot verification section, specify when the VM should be considered to have been booted successfully:
  • VM heartbeat is present. If you select this option, Veeam Backup & Replication will perform a heartbeat test for the verified VM.
  • VM responds to ping on any network adapter. If you select this option, Veeam Backup & Replication will perform a ping test for the verified VM.

Before you start a SureBackup job, make sure that the firewall on the tested VM allows ping requests.

Be careful when specifying the Maximum allowed boot time value. Typically, a VM started by a SureBackup job requires more time to boot than a VM started regularly. If an application fails to be initialized within the specified interval of time, the recovery verification process will be finished with the timeout error. If such error situation occurs, you will need to increase the Maximum allowed boot time value and start the job again.

Test Scripts

On the Test Scripts tab, specify what test scripts should be run to verify a VM. When you select a VM role, Veeam Backup & Replication automatically assigns a predefined script that will be run to verify applications inside the VM.

If you want to verify a VM that has some other role not listed on the Role tab, do the following:

  1. Click Add.
  2. In the Test Script window, select Use the following test script.
  3. In the Name field, specify a name for the script.
  4. In the Path field, define a path to an executable script file that should be run to verify the VM.
  • If you have your own custom script, define a path to it.
  • If you do not have a custom script, you can use Veeam’s standard utility, Veeam.Backup.ConnectionTester.exe, that probes application communication ports. The utility is located in the installation folder of Veeam Backup & Replication: %Program Files%\Veeam\Backup and Replication\Backup\Veeam.Backup.ConnectionTester.exe. Specify this path in the Path field.
  1. In the Arguments field, specify an IP address of the tested VM and the port that you want to probe. You can use the %vm_ip% variable to define the VM IP address or the %vm_fqdn%variable to define the VM fully qualified domain name.
  2. Click OK to add the configured test.

To edit test settings, select the test in the list and click Edit. To delete a test, select it in the list and click Remove.

If a VM performs several roles running a number of applications at once, you can verify their work by adding several verification scripts. For such VMs, it is recommended to specify the maximum startup timeout value and allocate the greatest amount of memory.

 

Step 4. Review the Application Group Summary and Finish Working with Wizard

After the group is created, review the application group summary and click Finish to exit the wizard.

Okay, troops – we’re almost home.  Now that we have a Virtual Lab and an Application Group, we can move on to creating the SureBackup job.

SureBackup

This is where the “automagically” part of this whole thing actually happens.  Here are instructions for:

 

Creating a SureBackup Job

To create a new SureBackup job, do either of the following:

  • Open the Backup & Replication view. On the Home tab, click SureBackup Job > VMware on the ribbon. Note that the SureBackup Job button becomes available only after you create or connect a virtual lab.
  • Open the Backup & Replication view, right-click the SureBackup node under Jobs in the inventory pane and select SureBackup > VMware. You can use this method if you already have at least one SureBackup job. If there are no SureBackup jobs, the SureBackup node will not be available in the inventory pane. In this case, you can right-click the Jobs node in the inventory pane and select SureBackup > VMware.

 

Step 1. Specify Name and Description

Enter a name and description for the new SureBackup job. The default description contains the time at which the job was created and user who created it.

 

Step 2. Select a Virtual Lab

From the Virtual lab list, select one of existing virtual labs in which recovery verification should be performed. The list contains all virtual labs that were created or connected to the Veeam backup server. Information about the selected virtual lab is displayed in the Virtual lab info section.

 

Step 3. Select an Application Group

At this step of the wizard, you should define an application group that should be used to enable full functionality of verified VMs.

You can select an application group for recovery verification or skip this step. If the application group is not selected, you must link a backup job to the created SureBackup job at the next step. In this case, when the SureBackup job is started, Veeam Backup & Replication will only run VMs from the linked backup job in the virtual lab and verify them.

To select an application group:

  1. From the Application group list, select the application group containing all VMs required to properly run applications and services on VMs that you want to test.  The list contains all application groups that were created on this Veeam backup server. Refer to the Backup Status column in the Application group info list to make sure that the backups for VMs in this group are available.
  2. To leave VMs from the application group running after the SureBackup job is finished, select the Keep the application group running once the job completes check box. If you select this option, the lab will not be powered off when the SureBackup job completes and you will be able to perform application item-level restore (U-AIR) and manually test VMs started in the virtual lab.

 

Step 4. Link a Backup or Replica Job to the SureBackup Job

At this step of the wizard, you should select VM backups or replicas that you want to verify with the created SureBackup job. Once you run a SureBackup job, Veeam Backup & Replication will start VMs from the application group in the required order and then boot and verify VMs from the linked backups or replicas.

You can link a backup or replica to the SureBackup job or skip this step. If you do not link a backup or replica to the SureBackup job, Veeam Backup & Replication will only start VMs from the application group in the virtual lab and verify them. You have an option not to link a backup or replica to the SureBackup job only in case you have selected an application group at the previous step of the wizard.

To link a backup or replica job to the SureBackup job:

  1. Select the Link jobs check box.
  2. Click Add.
  3. In the Select Job window, select the necessary backup or replica job(s).
  4. In the Process simultaneously up to … VMs field, specify the maximum number of VMs that can be started at the same time. For example, if you select to start thee VMs at the same time, Veeam Backup & Replication will create three streams in which one verified VM will be started. When the VM has been tested and powered off, the next VM will be started in the available stream. After all VMs are verified, VMs from the application group will be powered off or will be left running if the corresponding option has been selected at the previous step of the wizard.

To remove a backup or replica job from the list, select it and click Remove.

 

Step 5. Specify Recovery Verification Options and Tests

After you link a backup job with VMs you want to verify, you should define roles, specify startup options and select tests to be performed for these VMs.

If all VMs in the linked backup(s) perform the same role, you can specify startup options and test settings for the whole backup job in bulk. If VMs have different roles, you can granularly set startup options and select tests to be used for each VM in the backup job.

  • To specify startup options and select tests for the whole backup job, select the job in the list and click Edit on the right.
  • To specify startup options and select tests for each VM in the backup job individually, select the job in the list and click Advanced on the right. Click Add and select the necessary VM in theAdd Object window. Select the added VM in the list, click Edit and specify recovery verification settings as described below.

If you specify startup options and tests individually for a VM, Veeam Backup & Replication will apply these options and tests only. Options and tests specified at the level of the SureBackup job will be ignored for this VM.

To be able to perform tests, Veeam Backup & Replication requires VMware Tools to be installed on the verified VM. If VMware Tools are not installed, the VM will be started but tests will not be performed. VMs without VMware Tools can still be used as auxiliary VMs that should be started to enable proper work of other VMs. In this case, you do not need to select any role for the VM.

Role settings

On the Role tab, select the role that a VM performs. Veeam Backup & Replication offers the following predefined roles for VMs:

  • DNS Server
  • Domain Controller
  • Global Catalog
  • Mail Server
  • SQL Server
  • Web Server

VM roles are described in XML files stored in the %Program Files%\Veeam\Backup and Replication\Backup\SbRoles folder. You can add your own roles. To do this, you need to create a new XML file and specify role and test scripts settings in it. For details, see Creating XML files with VM Roles Description.

Once you select the necessary role, Veeam Backup & Replication will automatically configure startup options and provide predefined test scripts applicable for the chosen role. You can use these settings or specify custom ones using the Startup Options and Test Scripts tabs.

To verify VMs that perform roles other than those specified in the list, you will have to manually configure startup options and specify test scripts to be run against these VMs.

Startup Options

On the Startup Options tab, specify VM startup settings:

  1. In the Memory section, specify the amount of memory that you want to pre-allocate to the VM on the system boot. The amount of pre-allocated memory is specified in percent. The percentage rate is calculated based on the system memory level available for the production VM. For example, if 1024 MB of RAM is allocated to the VM in the production and you specify 80% as a memory rate, 820 Mb of RAM will be allocated to the verified VM on startup.
  2. In the Startup time section, specify the allowed boot time for the VM and timeout to initialize applications on it.
  3. In the Boot verification section, specify when the VM should be considered to have been booted successfully:
  • VM heartbeat is present. If you select this option, Veeam Backup & Replication will perform a heartbeat test for the verified VM.
  • VM responds to ping on any network adapter. If you select this option, Veeam Backup & Replication will perform a ping test for the verified VM.

Before you start a SureBackup job, make sure that the firewall on the tested VM allows ping requests.

Be careful when specifying the Maximum allowed boot time value. Typically, a VM started by a SureBackup job requires more time to boot than a VM started regularly. If an application fails to be initialized within the specified interval of time, the recovery verification process will be finished with the timeout error. If such error situation occurs, you will need to increase the Maximum allowed boot time value and start the job again.

Test Scripts

On the Test Scripts tab, specify what test scripts should be run to verify a VM. When you select a VM role, Veeam Backup & Replication automatically assigns a predefined script that will be run to verify applications inside the VM.

If you want to verify a VM that has some other role not listed on the Role tab, do the following:

  1. Click Add.
  2. In the Test Script window, select Use the following test script.
  3. In the Name field, specify a name for the script.
  4. In the Path field, define a path to an executable script file that should be run to verify the VM.
  • If you have your own custom script, define a path to it.
  • If you do not have a custom script, you can use Veeam’s standard utility, Veeam.Backup.ConnectionTester.exe, that probes application communication ports. The utility is located in the installation folder of Veeam Backup & Replication: %Program Files%\Veeam\Backup and Replication\Backup\Veeam.Backup.ConnectionTester.exe. Specify this path in the Pathfield.
  1. In the Arguments field, specify an IP address of the tested VM and the port that you want to probe. You can use the %vm_ip% variable to define the VM IP address or the %vm_fqdn%variable to define the VM fully qualified domain name.
  2. Click OK to add the configured test.

To edit test settings, select the test in the list and click Edit. To delete a test, select it in the list and click Remove.

If a VM performs several roles running a number of applications at once, you can verify their work by adding several verification scripts. For such VMs, it is recommended to specify the maximum startup timeout value and allocate the greatest amount of memory.

 

Step 6. Specify Additional Job Settings

On the Settings step, you can specify additional settings for the SureBackup job:

  1. If you want to receive SNMP traps, select the Send SNMP trap check box. SNMP traps will be sent only if you configure SNMP settings in Veeam Backup & Replication and on the recipient’s computer. To learn more, see Specifying SNMP Settings.
  2. If you want to receive notifications by email, select the Send email notifications to the following recipients check box. In the field below, specify a recipient’s email address. You can enter several addresses separated by a semicolon. Email notifications will be sent only if you configure general email notification settings in Veeam Backup & Replication. To learn more, see Specifying Email Notification Settings.
  3. (For VM backups only) If you want to validate the backup file with a CRC check and make sure the file is not corrupted, select the Validate consistency of virtual machines’ backup filescheck box. You can optionally exclude VMs being a part of the application group from this test. To do this, select the Skip validation for application group check box. To learn more, seeRecovery Verification Tests.

If you select the Keep the application group running once the job completes option at the Application Group step of the wizard, the Skip validation for application groupoption will be automatically enabled.

 

Step 7. Specify the Job Schedule

At the Schedule step of the wizard, you can select to manually run the SureBackup job or schedule the job at specific time, for example, after the corresponding backup job completes.

  1. To specify the job schedule, select the Run the job automatically check box. If this check box is not selected, the job is supposed to be run manually.
  2. Choose the necessary schedule option for the job:
    • Daily at to start the job at specific time every day, on week days or on specific days.
    • Monthly at to start the job once a month on the specified day.
    • After this job to chain the job. Typically, a SureBackup job should run after the linked backup job completes: in this case, the SureBackup job will verify the backup created by the corresponding backup job. To create a chain of jobs, you should define the time schedule for the first job in the chain. For the rest of the jobs in the chain, at the Schedule step of the wizard, select the After this job option and choose the preceding job from the list.
  1. In some cases, the linked backup job may not complete until the SureBackup job starts. If Veeam Backup & Replication finds out that the backup job is still running, the SureBackup job will fail to start. To overcome this situation, select the If some linked backup jobs are still running, wait up to check box and specify the necessary time period in the field on the right. In this case, if the linked backup job is still running, Veeam Backup & Replication will wait for the defined period of time and check the backup job after this period elapses.
    • If the linked backup job is finished within the specified period, the SureBackup job will start.
    • If the backup job is still running, the SureBackup job will not be started.

 

Step 8. Review the Job Summary and Finish Working with Wizard

Review the summary of the created recovery verification job. Select the Run the job when I click Finish check box to start the created job right after you finish working with the wizard; then click Finish.

 

That was indeed a lot of material! But here’s the good news: It will take most IT admins less than an hour to step through this whole guide, and that’s well worth the peace of mind of knowing that your backups are working, not worthless.

“I have the Standard version of Veeam Backup and Replication. What do I do?” Naturally, you could consider upgrading. But if you aren’t ready for that just yet, keep an eye out for part three of this series where we will discuss how to perform manual restore testing.

Need help setting up a functional backup and replication system? Give us a shout, either by email or phone: 502-240-0404.