IMPORTANT ANNOUNCEMENT: On May 6, 2024, Carbon Black User eXchange (UeX) and Case Management will move to a new platform!
The Community will be in read-only mode starting April 19th, 7:00 AM PDT. Check out the blog post!
You will still be able to use the case portal to create and interact with your support cases until the transition, view more information here!

App Control: What Are the Best Practices for Backing Up the Das Database?

App Control: What Are the Best Practices for Backing Up the Das Database?

Environment

  • App Control Server: All Supported Versions
  • Microsoft SQL Server: All Supported Versions

Question

What are the best practices for backup up the App Control database (das)?

Answer

  • The App Control database uses the "Simple" recovery model. The "Full" recovery model should not be used to avoid a performance penalty and excessive database log growth.
  • The automated database backup feature built into the Console is not designed for deployments of more than 100 endpoints.
  • For deployments of more than 100 endpoints a Maintenance Plan should be created via SQL Server Management Studio.
  • Recommended frequency for full backups is no more than 2-3 per week. More frequent backups could impact server performance.
  • Backups may impact performance and should be avoided during busy times (such as App Control Server maintenance tasks, typically between midnight and 6AM)
  • Backups should not be stored on the same drive as the App Control database.

Additional Notes

  • More information can be found in the SQL Backup section of the Operating Environment Requirements found on VMware Docs > Server Documentation > OER > SQL Backups.
  • Differential backups are not recommended as the "das" is a constantly changing database.

Related Content


Labels (1)
Tags (2)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎09-09-2020
Views:
1069
Contributors