How Does Veeam SureBackup Work?
Veeam SureBackup leverages Virtual Lab technology to create an isolated environment where backups can be tested without impacting production workloads. This ensures backup integrity and recoverability by automatically booting virtual machines (VMs) from backups and performing a series of validation tests. Below are some core Components of SureBackup;
- Virtual Lab: A sandboxed environment where VMs are powered on for testing.
- Application Group: A set of dependent VMs required to validate specific applications or workloads.
- SureBackup Job: The automated process that boots the backup and runs integrity tests.
Below is the “SureBackup” testing process. Once configured, SureBackup automatically executes a sequence of tests;
- Heartbeat Test: Ensures the VM is running by checking VMware Tools or Hyper-V integration services.
- Ping Test: Verifies network connectivity of the VM.
- Application Test: Custom scripts validate application-specific functionality.
At the end of the process, SureBackup generates a detailed verification report, giving administrators confidence that their backups are fully recoverable. Below is a step-by-step execution:
- Mounting the Backup: Veeam boots VMs directly from the backup without requiring a full restore.
- Running Tests: OS boot validation, application service checks, and network response verification are performed.
- Generating the Validation Report: A final report is created, indicating the status of the tested backups.
Configure SureBackup in Veeam Backup and Replication
Below is a step-by-step guide to setting up SureBackup in Veeam Backup & Replication.
Step 1: Create a Virtual Lab
Open Veeam Backup & Replication and navigate to Backup Infrastructure.
Right-click Virtual Labs and select Add Virtual Lab.
Choose the ESXi or Hyper-V host where the isolated lab will be created.
Specify Host to Run VM
Please, specify the host to run the VMs on
Configure the network settings to avoid conflicts with the production environment as described below.
- Role of the Proxy Appliance:
- It acts as a gateway between the isolated test environment and the production infrastructure, ensuring tests run without affecting live systems.
- Difference Between Proxy Appliance and Network Mapping:
- The Proxy Appliance redirects and filters traffic between the test environment and production.
- Network Mapping, on the other hand, defines how the test VMs’ IP addresses are translated to avoid conflicts with production.
- Key Proxy Appliance Settings:
- Selection of host and datastore for deployment.
- Choosing the network mode:
- DHCP (automatic IP assignment) or Static IP (manual configuration).
- IP masquerading rules, allowing test VMs to communicate with production without conflicts.
- Custom routing rules, if necessary, to enable data traffic with external networks.
You can modify or configure your Proxy as shown below.
Configure the network to enable VMs to run in a single or multiple production network.
Isolated Network Configuration:
- Define the Isolated Network to prevent conflicts with production.
- Enable Masquerade Addressing to translate production IPs to test-lab IPs.
- Map Production Networks to Isolated Networks, ensuring VM communication inside the lab.
Network Settings
Define the Network Settings as shown below
- Proxy Appliance: Acts as a gateway for test VMs, allowing controlled access to production resources if needed.
- Configure Static or DHCP IP assignment for the Proxy Appliance.
- Define custom routing rules to allow or restrict external network access.
Step 2: Define an Application Group
Navigate to the Backup Infrastructure and then to Application Groups.
Right-click and select Add Application Group.
Select the VMs that need to be tested.
Define the boot sequence and dependencies (e.g., ensure a database server starts before an application server).
Configure Startup Options:
- Boot Order & Delays: Define the sequence in which VMs start to ensure dependencies are met (e.g., a database server starts before an application server).
- Startup Timeout: Sets a maximum wait time for a VM to boot successfully before considering it failed.
- Graceful Shutdown: Enables proper VM shutdown at the end of the test instead of a forced power-off.
- Custom Scripts: Optionally add pre- or post-boot scripts to automate additional checks.
Step 3: Create a SureBackup Job
Navigate to Backup & Replication and click on Jobs.
Click SureBackup Job and select Create SureBackup Job.
Assign a name to the job and select the Virtual Lab created earlier.
Configure test options:
- Heartbeat Check – Ensures the VM’s OS has booted successfully.
- Ping Test – Verifies network connectivity.
- Application Test – Runs custom scripts to validate application functionality.
Set the test schedule and notification preferences.
Finish and save the job.
Step 4: Run and Review SureBackup Results
- Locate the SureBackup job in the Jobs section.
- Right-click and select Start to manually execute the test or wait for the scheduled run.
- Once completed, review the Session Log and generated reports to analyze test results.
- If any issues are detected, investigate and resolve them before relying on the backup in a real recovery scenario.
Some applications require network services to be available during boot. Ensure proper network configurations in the Virtual Lab or recovery environment. If performing Instant Recovery on a production host, ensure it has enough CPU, RAM, and storage performance to handle the additional workload.
If the recovery takes too long or fails, check Windows Event Viewer and Veeam logs for insights into potential causes.
I hope you found this guide on “Ensuring Backup Integrity and Reliable Recovery with SureBackup” very useful.
