Regularly back up the server, application, and database files listed in Table 64:
Essbase index file
Essbase data file
Essbase Kernel file that contains control information used for database recovery
Transaction control table
Free fragment file for data and index free fragments
Outline file, which does not store data but stores all metadata for a database and defines how data is stored
Application file containing application settings
Database file containing database settings
Linked Reporting Objects
Essbase security file
Backup of the Essbase security file
Essbase Server configuration file
.otl, .csc, .rul, .rep, .eqd, .sel
Database artifact files
[a] Back up all .ind files related to a database because a single database can have multiple .ind files.
[b] Back up all .pag files related to a database because a single database can have multiple .pag files.
[c] Shut down the Agent before backing up the essbase.sec.
When performing a file system backup, use the file system backup software of your choice. You can back up specific directories or files, or you can back up the entire Essbase directory structure. Be sure to back up data on every disk volume. See Specifying Disk Volumes.
If any Essbase databases must be running at the time of the backup, follow these steps:
To place a database in read-only mode, use a tool:
After you perform the backup, return the database to read-write mode.
Begin archive does not perform the backup; it protects the database during the backup process. If you cancel the BEGINARCHIVE ESSCMD command or the alter database begin archive MaxL statement and you receive a “can’t cancel” message, the system may be in the final stage of writing items to the drive and has reached the point where the operation cannot be cancelled.
To back up data, use a third-party backup utility to back up the files listed in archive.lst and the files listed in Table 64, Files to Back Up, or back up the entire Essbase directory structure.
To return the database to read-write mode, after performing a backup, use a tool:
When exporting data to a text file; the data is not compressed. The text export file contains data only and does not include control, outline, or security information.
You can use text export files to load data from the source database into databases on other platforms. The option to export a database in column format enables you to manipulate the export file and use it with a rules file to load the data back or to another database.
If the outline changes between the time that the export file is created and reloaded (and the new outline contains all the members found within the export file), the load time might be significantly higher than if the outlines were identical.
During a database export, users cannot write to the database. After an export has started, users can do read operations. Exports of large databases require considerable amounts of time, during which users can only read the data.
To export data, use a tool:
Calculation script (block storage only)
DATAEXPORT calculation commands
The columnar format provides a structure to the exported data, so that it can be used for further data processing by applications other than Essbase tools; for example, relational databases. In non-columnar format, sparse members identifying a data block are included only once for the block. Because the export file in non-columnar format is smaller than in columnar format, reloading a file in non-columnar format is faster.
Some file management systems do not support text files larger than 2 GB. On any operating system, if Essbase anticipates that an export file exceeds 2 GB, it creates two or more export files, as needed. The requested file name for the main file is used. An underscore and a sequential cardinal number are appended to the names of the additional files, starting with _1. For example, if the requested file name is expJan.txt and the exported data would exceed 4 GB, Essbase creates three files, naming them expJan.txt, expJan_1.txt, and expJan_2.txt. Exported data files can be reloaded in any sequence.
This section discusses recovery procedures.
Essbase Technical Reference
When you reload data that has been exported, the data is marked as input data. If you reload data exported from level 0 blocks or input blocks, you must recalculate the database after reloading. When Essbase recalculates the database, it recalculates every data block.
If you export all data in a database and then reload, Essbase marks all blocks in the database as input blocks. Consequently, if you try to clear data, no data is cleared because the database contains no non-input blocks.
When you reload data that has been exported, Essbase also marks the data blocks as dirty. If you had calculated the database prior to exporting it, to save time during the next calculation, you should set the status of the blocks as clean. If you had not calculated the database prior to exporting it, it is not necessary to set the status of the blocks as clean.
To restore the database, delete these file, restart the database, and reload from data files or from export files backed up prior to the corruption.