Virtual Lab
The virtual lab allows creating an isolated bubble for testing, for both automated and manual tests. Most of the configuration is centered around networking and as best practice involve the local Network Engineer during setup.
Proxy Appliance
The best practice is to put the Proxy Appliance and the VBR server in the same subnet. They require direct communication. During a Surebackup job, VBR will automatically add static routes that will push packets from the VBR server to the Proxy Appliance. The Proxy Appliance will then translate (NAT) the masquerade network to the original IP address space and send the packages to the isolated VMs.
In case the Proxy Appliance and the VBR server do not sit in the same subnet, packages need to pass through a router. If the router is not aware of these masquerade networks, it will drop the package and network will not reach the Proxy Appliance. In such cases, the Network Administrator needs to create static routes for packages to the Proxy Appliance IP for those masquerade networks.
Networking
Virtual Labs has 3 modes:
- Basic single host: This mode is mostly unusable in any environment where there is more than 1 network. The best practice is to not use this mode in any production environment.
-
Advanced single host: Use this mode if you have limited control over the network or do not have a license for VMware DVS.
This mode powers on all VMs on the same host, so it might not be suitable for “SureReplica” functionality (as it might not be possible to run all replicas on the same host) or running an application group with a number of large machines which overloads the host. - Advanced multi host: Use this mode if you have DVS switches and you have control over the network.
For testing backups on multiple nodes:
- Use Advanced multi host.
- Make sure vPower NFS is mounted on all targeted hosts.
- Disconnect Floppies and DVD/CD-ROM drives.
- Make sure the I/O redirection datastore is located on shared storage.
- Enable DRS. By default, VMs will be assigned to a single ESXi hosts. By enabling DRS, the VMs can be vMotioned to different nodes.
Isolated Networks
During the configuration, you need to create an Isolated Network for every network that has a VM connected to it and which you want to test. When selecting a VLAN, make sure that you select a VLAN that is not used in your production environment. For “Advanced multi host” this is a must to avoid any conflicts, as data is travelling over the real network. For “Advance single hosts” this is a best practice. In the last scenario, the network is usually created on top a vSwitch without any uplinks attached to it, so it should not create any conflicts. However, by using completely different VLANs, you avoid issues if the vSwitch is accidentally connected to a pNIC and you create a proper separation.
Network Settings Step
The vNIC settings by default have DHCP enabled but in most production environments, there is no DHCP but only static IP addresses are used. If DHCP is not required, it is a best practice to disable DHCP Server functionality completely to simulate the real environment.
Static Mapping
When creating a lab setup, it a good idea to include a “Jump host” in the Application group and then assign a production IP to this VM with a Static Mapping. In such setup, only a single Static mapping needs to be created to get access to the lab and the lab is accesible from other subnets.