To successfully protect a Microsoft SQL Server environment several
prerequisites must be met:
- Protector Client software is installed on all nodes which are part of a Microsoft SQL Server setup
- For clustered setups, install the Protector client on each cluster node. No special installation steps are required. The procedure is the same as for standalone systems (For more details, please refer to “How to install/upgrade Protector on Windows and Linux” in the Protector User’s Guide)
- Clustered SQL Server instances must consist of a minimum of two nodes.
- For SQL Server Availability Groups, install the Protector client on all standalone or cluster nodes. No special installation steps are required. The procedure is the same as for standalone systems (For more details, please refer to “How to install/upgrade Protector on Windows and Linux” in the Protector User’s Guide).
- Availability Groups must consist of at least two replicas.
- A user account is provided for use by Protector, having the specified Microsoft SQL Server User Privileges.
- To configure protection for clustered SQL Server setups or Availability Groups, all nodes must be running and authenticated with Protector.Note: This is a requirement for the setup. Once configured scheduled or RPO based backups will work even if only a subset of the cluster nodes is online.
- For block-based data protection, ensure that:
- Databases are located on a single supported block storage.
- Databases which should not be backed up together are on separate
LUNs.Note: It is recommended that each database uses a separate set of LUNs.
Note: To apply transaction logs after an
online revert, multiple databases must not share LUNs and there must only be a single
database in a backup. See About reverting Microsoft SQL Server block-based backups for more details.