Veeam supports several recovery scenarios and offers flexible options for them. To choose a scenario, consider your organization’s policies and requirements and decide on the following:
- Will you need to recover your database to the moment when the certain Microsoft SQL Server VM restore point (backup or replica) was created, or to any point in time, maybe within the interval between two restore points?
In the latter case, database will be restored to the closest VM restore point before the moment you specify, and then transaction log replay will bring the database to the necessary state. So, you will need to enable backup of Microsoft SQL Server transaction logs in the backup job settings.
- Should you support more granular recovery and be able to roll back your databases to a state before undesired transaction?
For the most granular restore, you will need to enable backup of the transaction logs and ensure the staging SQL Server availability and proper configuration.
- Do you plan to restore your database to the original Microsoft SQL Server, or to a different server?
Make sure that Veeam can communicate with target server over the network, and check that account you plan to use for restore has sufficient permissions. Also, check for proper target SQL Server version (later version database cannot be restored to earlier version server).
- Will you mostly restore objects to their original location on a production SQL server? You can optimize data flow at restore - for that, examine the location of repository server and target SQL server to find out if they are located in the same site with Veeam backup server.
- If all these components are in the same site, Veeam Explorer will utilize Mount Service running on Veeam backup server for mount operation:
- If repository and production (target) SQL Server VM are located in a remote site (separately from Veeam backup server), then it can be reasonable to deploy Veeam Backup & Replication console in that remote site and launch Veeam Explorer from that console, initiating mount operation locally in the site where console is running.
- Should you maintain database restores by yourself, or will you delegate restore rights to another user (group of users)? In the latter case, it is reasonable to use Enterprise Manager functionality for delegated restores of application items.
To implement the necessary scenario, you should, in particular, do the following:
- Decide on the required level of restore granularity and configure the necessary SQL Server VM backup job settings.
- Use the appropriate SQL Server VM file-level recovery option when choosing VM’s restore point.
- Provide user account (under which Veeam Explorer for Microsoft SQL Server will be launched) with sufficient rights on target SQL Server.