Essbase Best Practice: Essbase Security File Auto Backup Intervals

By default, Essbase will automatically backup the Essbase security file, Essbase.sec, every 300 seconds (5 minutes).  Most customers find the frequency of the default backup interval overhead to be unnecessary given their security update needs. It is recommended to change the default setting before the “build” and “go-live” phases to have better Essbase.sec file backups proportionally spaced between backups and improve overhead.

Typically, during the build phase when security is being created for the first time or updated frequently, it is recommended to set the auto backup interval to every 4 to 8 hours. The reason for the longer backup interval is to give administrators the time needed to process all of the writes made to the Essbase.sec file before the next scheduled backup. This will mean that a good and complete backup can be then taken.

Typically, during the “go-live” phase or once live in production when security is in maintenance mode, it is recommended to set the auto backup interval to every 1 to 2 hours. The reason for the shorter backup intervals is to capture the random security updates done throughout the day by the administrators. If there is minimal or no changes to security on a business-as-usual basis, potentially making frequent security backups an unnecessary overhead, backup intervals could be increased to every 12 hours.

If security updates are handled during a batch process, it may make sense to turn off the auto backup interval and take manual backups of the Essbase.sec as needed. Whatever is determined to be the best fit for a given project, changing the default backup interval is highly recommended to suit the needs of the deployment.

In order to change the default Essbase security file auto backup interval, the Essbase configuration settings in the Essbase.cfg file needs to be added. For example:


For more details on these settings, please refer to the Oracle® Essbase Technical Reference and the Oracle® Essbase Database Administrator's Guide:


Post a Comment:
  • HTML Syntax: NOT allowed