Backup Recovery Verification Tests
To verify VMs with a SureBackup job, you can instruct Veeam Backup & Replication to run predefined tests for VMs or use custom verification scripts.
Veeam Backup & Replication can verify VMs with the following predefined tests:
- Heartbeat test. When the VM starts, Veeam Backup & Replication performs a heartbeat test. It waits for a heartbeat signal from Hyper-V Integration Services installed inside the VM to determine that the VM guest OS is running. If the signal comes regularly at specific time intervals, the test is passed.
- Ping test. Veeam Backup & Replication sends ping requests to the VM from the backup server and checks if the VM can respond to them. If the VM responds to ping requests, the test is passed.
Veeam Backup & Replication uses two algorithms for detecting the IP addresses of a Hyper-V VM:
- Veeam Backup & Replication communicates with Hyper-V Integration Services installed inside the VM guest OS to to detect the VM IP address.
- Veeam Backup & Replication uses a special module in the proxy appliance to check the IP addresses of the VM started in the isolated network. This algorithm is used, for example, if the VM does not have Hyper-V Integration Services installed.
- For DNS servers, domain controllers, Global Catalog servers, mail servers and web servers, Veeam Backup & Replication uses a script that probes an application-specific port. For example, to verify a domain controller, Veeam Backup & Replication probes port 389 for a response. If the response is received, the test is passed.
- For Microsoft SQL Server, Veeam Backup & Replication uses a script that attempts to connect to instances and databases on the Microsoft SQL Server. For more information, see Microsoft SQL Server Checker Script.
|
To run the heartbeat test, you must have Hyper-V Integration Services installed inside the VM. If Hyper-V Integration Services are not installed, this test will be skipped. |
Microsoft SQL Server Checker Script
- Connects to Microsoft SQL Server instances.
- Enumerates databases on these instances.
- Employs the USE SQL statement to connect to databases and check their availability.
Credentials for Script Execution
- Microsoft Windows authentication mode. To use it, you must specify credentials for the account on the Credentials tab in the application group or SureBackup job settings.
- SQL Server authentication mode. To use it, you must pass credentials of the account to the script. You can pass credentials the following ways:
cscript C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.SqlChecker.vbs <sql server[\instance]> <username> <password> |
cscript C:\Program Files\Veeam\Backup and Replication\Backup\Veeam.Backup.SqlChecker.vbs [C:\Logs] <sql server[\instance]> <username> <password> |
|
Do not pass sensitive information using script arguments in a user interface. |
|
If you use the Microsoft SQL Server authentication mode, you may need to specify credentials of the account to connect to the machine on which Microsoft SQL Server is installed. To do this, use the Credentials tab in the application group or SureBackup job settings. |
- To exclude specific databases, uncomment the 'gDBsToExclude.Push "dbname" line in the script and specify name(s) of database(s) that you want to exclude. To exclude several databases, use a comma.
- To exclude specific instances, uncomment the 'gInstancesToExclude.Push "instancename" line in the script and specify name(s) of instances that you want to exclude. To exclude several instances, use a comma.
- To exclude the default instance, uncomment the 'gInstancesToExclude.Push "MSSQLSERVER" line.
|
Instance and database names are case sensitive. |
- 0 — test is passed successfully.
- 1 — you use a wrong syntax for the script command.
- 2 — Veeam Backup & Replication is unable to connect to Microsoft SQL Server.
- 3 — all instances are excluded from the check.
- 4 — error occurred while Veeam Backup & Replication was getting the list of databases.
- 5 — unknown error
- 6 — one or more databases are not accessible.