Learn Hyperion From Ajay Kambhampati

Essbase Backups & Recovery

Ajay Kambhampati Hyperion.ajay@gmail.com

key part of a database maintenance routine includes regular backups of Essbase files and data. It is important to integrate regular database backups into production server maintenance. Must backup both Essbase files and Data. Frequency Nightly Weekly

Nightly Backups Essbase Files & Data Backing up Data

If you back up data without using a BEGINARCHIVE utility, ensure that all Essbase applications are closed and that all users are logged off during the backup process to avoid corrupting the database.

Export Process

Export Lvl0 Data to a text File Export All Data to a Text File Keep the last 6 Exports in the Archive Folder
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.

Consider exporting data to: Transfer data across platforms Back up only part of the data; for example, level 0 blocks Create an exported file in text format, rather than binary format

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.

Make sure to save a copy of the .otl file! Exports can be done in Administration Services or via Maxl script

Tools to Export Data:

Administration Services Report Writer Calculation script ESSCMD MaxL Exporting Databases Use a Report Writer script to export selected data. DATAEXPORT calculation commands EXPORT or PAREXPORT export data

Backing up Files
Should perform a backup after Essbase applications and databases, and the Agent, are shut down.

Regularly back up the server, application, and database files listed in the below Table

File
dbname.esm

Description
Essbase Kernel file that contains control information used for database recovery Transaction control table

Location
\ ARBORPATH\app\

appname \ dbname

dbname.tct

ARBORPATH\app\ appname \ dbname

\ ARBORPATH\app\

dbname.ind

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

appname \ dbname
\ ARBORPATH\app\

dbname.otl

appname \ dbname

dbname.app

\ ARBORPATH\app

dbname.db

Database file containing database settings Linked Reporting Objects

\ ARBORPATH\app\

appname \ dbname
\ ARBORPATH\app\

x.lro

appname \ dbname
essbase.bak

Backup of the Essbase security file Essbase Server configuration file Database artifact files

\ ARBORPATH\bin

essbase.cfg

\ ARBORPATH\bin

.otl, .csc, .rul, .rep, .eqd, .sel

\ ARBORPATH\app\

appname \ dbname

ESSCMD or MaxL scripts

Backing up Files during Run-time

If any Essbase databases must be running at the time of the backup, follow these steps: 1. Place a Database in Read-Only Mode 2. Perform a File Backup 3. Return a Database to Read-Write Mode

Placing a Database in Read-Only Mode Using Maxl, type alter database begin archive Using Esscmd, BEGINARCHIVE
Placing the database in read-only (or archive) mode protects the database from updates during the backup process.

The BEGINARCHIVE utility performs these tasks: Commits modified data to disk. Switches the database to read-only mode. Reopens the database files in shared, read-only mode. Creates a file containing a list of files that need to be backed up. By default, the file is called archive.lst This file is stored in the ARBORPATH\app\appname\dbname directory

Perform a File Backup

After putting the database in read-only mode, you are ready to perform the backup. Backup the files listed in archive.lst first and then all the files mentioned in the above Table

Return a Database to Read Write Mode Using Maxl, type alter database end archive Using Esscmd, ENDARCHIVE
The ENDARCHIVE utility: Returns the database to read-write mode. Re-opens database files in exclusive, read-write mode.

Weekly Backups Image Backup

Shut down all the services and then the server and then take Image Backup

Reduce Fragmentation on a regular basis

Export Data Clear Data Reload Data Calculate Data

Key Essbase files

essn.pag essn.ind dbname.esm dbname.tct dbname.ind Analytic Services data file Analytic Services index file Analytic Services Kernel file that contains control information used for databse recovery Transaction control table Free fragment file for data and index free fragments

dbname.otl

Outline file, which does not store data but does store all metadata for a Database and defines how data is stored If a problem occurs with any of these files, the entire database is corrupt and a restore from backup is required

Essbase Recovery
Restoring the File Backup
To restore a database, replace the files on disk with the corresponding files from backup. The application should be stopped, unless you are restoring from an export file. In that case, ensure the application is not accepting client connections

Restoring the Data Backup

Tools to reload Exported data
Essbase Administration Services ESSCMD MaxL Performing a Data Load or Dimension Build IMPORT import data

Restoring Corrupted Databases

If there is a problem with any one of these essential database files, the entire database becomes corrupted and Essbase Server cannot start the database: essn.pag essn.ind dbname.esm dbname.tct dbname.ind To restore the database, delete these file, restart the database, and reload from data files or from export files backed up before the corruption.

Other Important Hyperion Backups

Hyperion Administration Services: Relational database Hyperion Financial Reporting: Relational database

 Hyperion Web Analysis: Relational database Hyperion BI: Relational database Hyperion Shared Services relational database Hyperion Shared Services file directory