In Hyperion Essbase version 11.1.2.1 we can manage the number of security backup files (essbase_timestamp.bak) that Essbase maintains; the interval at which the security backup files are created; and whether to switch to the latest, valid security backup file on startup if the essbase.sec file is invalid.
We have to setup following settings in Essbase.cfg file to activate this feature.
1) SECFILEBACKUPINTERVAL configuration setting: Specifies the amount of time Essbase
waits before creating a security backup file.
2) NUMBEROFSECFILEBACKUPS configuration setting: Specifies the maximum number
(up to 10) of security backup files that Essbase creates and maintains. By default, Essbase maintains two versions of essbase_timestamp.bak.
3) ENABLESWITCHTOBACKUPFILE configuration setting: Specifies whether Essbase loads
a valid security backup file at startup if the essbase.sec file is invalid.
Pre-upgrade Security File Backup
When you upgrade to Essbase 11.1.2.1 from an earlier release, a backup of the security file for the earlier release is created before the security file is upgraded. The security file backup,Essbase.Bak_preUpgrade, is in ARBORPATH/bin. Unlike the essbase_timestamp.bak file, which regularly backs up the latest state of Essbase security, this pre-upgrade backup file is kept intact and is not subsequently updated by further operations.
