Each time you start Essbase Server, Essbase creates a temporary file, named tempessbase.sec, that is used to validate the Essbase security file (essbase.sec). When Essbase Server successfully starts using essbase.sec, tempessbase.sec is deleted and Essbase creates a security backup file, named essbase_timestamp.bak.
You can manage the number of security backup files 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.
NUMBEROFSECFILEBACKUPS configuration setting: Specifies the maximum number (2 to 10) of security backup files that Essbase creates and maintains. When the limit is exceeded, Essbase deletes the security backup file with the oldest timestamp and creates the latest backup file.
By default, Essbase maintains a minimum of two versions of essbase_timestamp.bak.
SECFILEBACKUPINTERVAL configuration setting: Specifies the amount of time Essbase waits before creating a security backup file.
By default, Essbase creates a new security backup file every 300 seconds (which is five minutes).
ENABLESWITCHTOBACKUPFILE configuration setting: Specifies whether Essbase automatically loads a valid security backup file at startup if the essbase.sec file is invalid.
By default, Essbase does not load a security backup file at startup if the security file is invalid.
Also see Reconciling the Essbase Security File to the State of Essbase on an External Disk.
The content of essbase_timestamp.bak is encrypted.
Note: | Essbase automatically creates a backup of the security file before and after migration (essbase.bak_preUPM and essbase.bak_postUPM). See Migrating Essbase to EPM System Security. |