4.3. Diseño de la propuesta
4.3.11. Procedimiento de los ensayos de laboratorio
4.3.11.5. Ensayo con cilindros de hormigón
When a recovery verification job is running, you can monitor how tests for verified VMs are performed and see their results in the real-time mode. To see the status of VM tests, right-click a necessary recovery verification job and select Realtime Statistics from the shortcut menu.
The Verification Job Session window displays statistics for all VMs that are started during the recovery verification job – VMs from the application group in the specified order, and VMs from the linked backup job. For your convenience, these VMs are marked with different icons. The recovery verification process includes the following steps:
1. Getting virtual lab configuration. Veeam Backup & Replication gets information about configuration of the virtual lab where verified VMs should be started.
2. Starting virtual lab routing engine. Veeam Backup & Replication starts a proxy appliance used as a gateway to provide access to the virtual lab.
3. Publishing. Veeam Backup & Replication creates an NFS-datastore with a VM backup and registers it on the selected ESX server. Veeam Backup & Replication does not deploy the whole VM from the backup file, it deploys VM configuration files only. Virtual disks are deployed per force and per required data blocks.
4. Updating configuration. Veeam Backup & Replication updates configuration files for VMs that should be run in the isolated network.
5. Registering. Veeam Backup & Replication registers the verified VM on the selected ESX host.
network.
To be able to perform tests for a verified VM without errors, Veeam Backup & Replication needs to know that the VM is ready for testing. To determine this, Veeam Backup & Replication waits for the VM to reach a "stabilization point"— that is, waits for the VM to boot completely and report it is ready for tests. After the stabilization point has been established, Veeam Backup & Replication can start performing heartbeat tests, ping tests and running test scripts against the VM.
Veeam Backup & Replication establishes the stabilization point with the help of VMware parameters that it gets from the VM. Depending on the VM configuration, it uses one of the three algorithms to do that:
•
Stabilization by IP. This algorithm is used if the VM has VMware Tools installed, there are NIC(s) and mapped network(s) for these NIC(s). In this case, Veeam Backup & Replication waits for an IP address of the VM for mapped networks, which is sent by VMware Tools running in the VM. The sent IP address should be valid and should not change for a specific period of time.•
Stabilization by heartbeat. This algorithm is used if the VM has VMware Tools installed but there are no NIC(s) and mapped networks for them. In this case Veeam Backup & Replication waits for a corresponding heartbeat signal (Green or Yellow) to come from the VM. As well as in the first case, the signal is sent by VMware Tools running in the VM.•
Stabilization by Maximum allowed boot time. This algorithm is used if the VM has neither VMware Tools installed, nor NIC(s) and mapped networks for them. In this case, Veeam Backup & Replication will simply wait for the time specified in the Maximum allowed boot time field, which is considered to be a stabilization period for the VM. Once this time interval is exceeded, Veeam Backup & Replication will consider that the VM is successfully booted and is ready for testing.Note: The stabilization process cannot exceed the value specified in the Maximum allowed boot time field. If the stabilization point cannot be determined within the Maximum allowed boot time, the recovery verification process will be finished with the timeout error. For this reason, you should be careful when specifying this value — typically, the VM started within the frames of a SureBackup job requires more time to boot if compared to a regular VM startup. When such an error situation occurs, you will need to increase the Maximum allowed boot time value and start the job once again.
Once the stabilization point has been established, Veeam Backup & Replication runs ping, heartbeat tests and performs test scripts against the verified VM.
8. Pinging. Veeam Backup & Replication checks if the VM responds to the ping requests or not. If the VM has no NIC(s) and mapped networks for them and/or has no VMware tools installed, the ping test will not be performed, and a notification will be written to the session details.
9. Performing heartbeat test. Veeam Backup & Replication checks whether the VMware Tools heartbeat signal (Green or Yellow) is coming from the VM or not. If the VM has no VMware Tools, the test will not be performed, and a notification will be written to the session details.
10. Application initialization. Veeam Backup & Replication waits for the applications installed in the VM (for example, SQL Server, web server, mail server) to start. The application initialization period is defined in the corresponding properties of a
SureBackup job, and by default equals to 120 sec. However, depending on the software installed in a VM, the application initialization process may require more time than specified in the SureBackup job settings. If applications installed in a VM are not initialized within the specified period of time, test scripts can be completed with errors. If such an
11. Running test scripts. Veeam Backup & Replication runs scripts to test whether the application installed in the VM is working correctly or not. If the VM has no VMware Tools installed and/or there are no NIC(s) and mapped networks for them, Veeam Backup & Replication will skip tests that use variables such as %vm_ip% and so on, as the IP address of the VM cannot be determined.
Test results are written to the session details. To define whether the script has completed successfully or not, Veeam Backup & Replication 5.0 uses return codes. If the return code is equal to 0, the script is considered to complete successfully. Other values in the return code mean that the script has failed.
12. Powering off. After all tests have been performed, SureBackup powers off the verified VM.
13. Unregistering. Veeam Backup & Replication unregisters the verified VM on the selected ESX host.
14. Clearing redo logs. Veeam Backup & Replication deletes redo logs that were created to store changes made to the VM while it is running from the backup file.
15. Unpublishing. Veeam Backup & Replication unpublishes the content of the backup file on the ESX host.
Once the verified VM is powered on, its name is displayed as a hyperlink. You can click the link to open the VM console (just like in the vSphere Client) to see what is happening inside a VM, or perform manual testing. To open the VM console, click the VM name link in the list of verified VMs.
After the verified VM is started and the application running there is initialized, you can start U- AIR wizards right from the Realtime statistics window to perform granular application item- level recovery. To do so, right-click the verified VM and select a corresponding command from the shortcut menu. Depending on the type of a running VM, you can start the Active
Directory item recovery wizard, Exchange item recovery wizard, or SQL item recovery wizard.
clicking it in the list and selecting the Start command from the shortcut menu. If the application group has already been powered off by that time, it will be started again. After that, you can open the VM console and perform verification and testing manually.
Note: To define whether the script has completed successfully or not, Veeam Backup & Replication 5.0 uses return codes. If the return code is equal to 0, the script is considered to complete successfully. Other values in the return code mean that the script has failed.