SureBackup - Veeam Guide
SureBackup - Veeam Guide
SureBackup overview
To perform live testing of guests, SureBackup® will isolate live images from the rest of the
production environment and run pre-defined tests against them, as described in below
illustration.
This is made possible using different Veeam features such as Virtual Lab, Instant VM Recovery®
and application groups in conjunction with specific testing scenario.
Infrastructure concerns
SureBackup is relying on Veeam Instant VM Recovery feature. This means that the repository
must offer enough performance to concurently start as many concurrent IVMR sessions as
configured in the SureBackup job and the application group.
For example, if a SureBackup job is configured to test three VMs in parallel and an application
group is configured with two VMs, then the repository must offer enough IOPS to run five VMs at
the same time.
Note: it is strongly advised to keep the virtual lab appliance external network on the network
where the Veeam Backup & Replication server resides. If for any reason this is not possible
routing rules should be added in the production network to access the guests images booted
inside the virtual lab. The static routing added to the Veeam Backup & Replication server itself
will not be propagated to the network equipment.
Note: Basic-Single host configuration requires that backup server and VMs to test are connected
to the same network. As the backup server should always be in a different network than
production for security reasons, please use Advanced Single-Host Virtual labs.
Isolated networks
Each production network with unique settings used in production by verified VM should be
mirrored inside the virtual lab through the isolated network settings.
Network settings
The gateway IP address of the production networks should be used on the vNics allowing the
vLab appliance to act as a gateway for the isolated guests without reconfiguring them.
In the following illustration the production network gateway address 172.21.232.1 is assigned to
the corresponding vNic of the virtual lab appliance.
Masquerading
This parameter will allow accessing the tested guests through the vLab appliance by creating a
static route on the Veeam Backup & Replication server at virtual lab start-up. For example, if
production guest IP is 172.21.233.20, then the masquerade IP could be 172.22.233.20.
Note: It is recommended that virtual lab proxy appliance and backup server are in the same
network. If the backup server and virtual lab proxy appliance are in different networks, then the
masquerade IP range must not be already in use on the production network.
Corresponding routes will be automatically created on the Veeam Backup & Replication server
when the SureBackup job starts. These temporary routes will be used to perform network related
tests and to access the VM from the Veeam Backup Server. Once the SureBackup job is complete
these routes will be deleted.
Whenever Multi host configuration shall be used, special attention should be paid to distributed
virtual switch VLANs configuration, as the VLAN IDs configured for the virtual lab should be
unique and must be tagged on the network equipment.
Note: if for some reason the VLAN ID configured is already in use on the production
environment, the Virtual Lab will not be isolated from the production environment, causing
severe networking issues, such as duplicate IPs or Mac Addresses.