MS SQL 2012/2014/2016/2017/2019 Database Backups

Overview: 

The Microsoft SQL module is installed via the Commvault console after the Commvault File System Agent is installed and configured. If the servers are configured in a SQL cluster or Availability Group configuration, please note the details about the configuration in the SMC ticket that corresponds with this work effort.

Version & Requirements:

http://documentation.commvault.com/commvault/v11/article?p=system_requirements/sql.htm

System Requirements - Microsoft SQL Server iDataAgent

Requested Information in Workbook:

If you are running DBs with RECOVERY MODEL equal to FULL, and have specific needs for truncating transaction logs, please note these details in the corresponding workbook.

Defaults:

Expedient will truncate transaction logs on Full Recovery Model Databases every 24 hours. Please, list any specific Databases that need to be excluded from backups. All Databases inside of an Instance will be backed up, unless a specific list is provided for inclusion/exclusion.

Security & Permissions:

Expedient will need NT AUTHORITY\SYSTEM or a service account up with sysadmin rights added to all SQL Instances being backed up. If a service account is to be used, said account must be added to the Local Administrator group on the machine.

Special Considerations:

If any additional SQL instances are added in the future, Expedient staff must be made aware of any new instance to properly configure backups for that instance.

Transparent Data Encryption (TDE) or Always Encrypted are enabled, then the following rules apply:

• Backups are not affected. 
• If you have a storage policy that uses deduplication, then the deduplication ratio is low or non-existent. 
• If the restore destination is a different client or instance, then the SQL administrator must back up the encryption key, and present it to the destination instance.