Note: there are 2 ways for Essbase backup and recovery
Method 1:
backup = full essbase backup + transaction log backup
recovery = full essbase recovery + replay transaction log
Method 2:
backup = backup all Essbase system files
recovery=replace essbase system files with the backup files
You can backup files while Essbase is in read only mode
The Essbase should be stopped while recovery is processing in method 1 or 2.
---------------------------------------------------------------------------
Note: Essbase Outline change will NOT be logged!
Note: in the essbase.cfg file, set the SPLITARCHIVEFILE configuration to TRUE. This will split archive file to smaller size(<2 GB).
Note: Partition commands (for example, synchronization commands) are not logged and,
therefore, cannot be replayed. When recovering a database, you must replay logged
transactions and manually make the same partition changes in the correct chronological order.
When using partitioned databases or using the @XREF function in calculation scripts, you must selectively replay logged transactions in the correct chronological order between the source and target databases.
Note: for ASO Essbase,the only way is system file backup:
1 Stop the application.
2 Use the file system to copy the contents of the application directory (ARBORPATH/app/appname),excluding the temp directory
-----------------------------------------------------------------------------
Set Essbase in read only mode when backing up:
alter database begin archive
Set Essbase back to read/write after backing up:
alter database end archive
----------------------------------------------------------------------------
Use export command to export data file is also a simple option to keep text format data backup, level 0 data is ok
