A disaster recovery strategy allows you to plan for unexpected outages to ensure you can continue auditing SQL Server activity and policy compliance.
When you implement IDERA SQL Compliance Manager in your production SQL Server environment, consider preparing a disaster recovery strategy to minimize audit data loss should the Collection Server become unavailable. Use the following procedures and guidelines to implement a new disaster recovery strategy or modify an existing disaster recovery strategy.
Identify how often to back up the Repository databases
The frequency at which you back up the Repository databases depends on the following factors:
- How often your audit settings change
- How often your SQL Server environment changes as you add new servers and databases or remove older servers and databases
- How much audit data you collect in a given time period
- How much risk you are willing to incur
The backup frequency should reflect your maintenance needs and allow you to meet future compliance requirements.
Schedule routine backups of the Repository databases
After you identify the appropriate backup frequency for your compliance needs, use a tool such as Idera SQL Safe to schedule routine backups of the Repository databases.