A practical guide for “Essbase Backup and Recovery Part II”

A practical guide for

“Essbase Backup and Recovery Part II”

Backup & Recovery: Back and recovery is one of the most important strategies one should define as an administration activity. Backing up Essbase database is important to prevent data loss and other objects from any kind of loss. You take backup of database and other Essbase artifacts so that you can safeguard your important data and objects. .

We can restore the Essbase database to the point we took backup last time. For example the backup cycle is once in a week i.e every Sunday, so if the database fails on Tuesday we loss the data till Tuesday. The frequency of data backup depends on many scenarios. One of the new features that were introduced in the EPM 11.1.1.0 release is the ability to restore an Essbase database back to its original state after a database failure. Typically, restoring a database from a backup always restores the database back to the point in time when the backup was taken. In part-I of Essbase backup and recovery we are focused to basic backup and recovery strategies. Next release of this doc will talk about the Replay transaction feature.

Database Archive and Replay

When the backup operation performs the database should be in read only mode. During backup there could have been transaction that happened after that backup. But the new transactions are not backed up. We could restore the database only to the point of time of the backup. It is possible to restore the new transactions/data loads related data as well using the Database Replay feature.

The archive works in 3 steps.

1. Database should be in read-only mode by using the begin archive command.

2. Manually backup all the files listed in the archive file generated as part of the begin archive command.

3. Revert the database to the normal mode by using the end archive mode.

The backup operation can perform using the Archive and Restore feature in Essbase system 11.

Maxl Script for getting information about the necessary backup file

Now the above MaxL will create the archive list file shown below. This all are basic data base backup files which have to back up.

You can take back up of all files mention in “Bisp.lst” file in to a dedicated space. In system 11 you can take back up through Maxl script.

Open the folder path and you can validate weather script run successfully or not. One new file “BispBD.arc” created at the specified path.

Through the admin console you can generate archive file without creating Maxl script. Right click on database and select “Archive Database”.

You can restore the same archive file through below Maxl script.

alter database 'Bisp'.'BispBD' restore from file 'H:\DataBase\BispBD.arc';

Enable Transaction Logging

You need to enable transaction logging through Essbase configuration file. For enabling transaction logging you pass some commands in to the Essbase configuration file.

By fallowing process you can easily understand Replay option.

1. Archive the database

2. Update the data in Essbase using Excel Add-in

3. Restore the database

4. Refresh Excel report the modified data would have been lost and show previous data

5. Enable Replay to see whether you are getting the updated data from Excel Add-in

Archive, Restore Database and Replay Option

Step#1:- Open excels sheet build report using “BispBD” as database.

Here is very simple Essbase report. You can concentrate actual data for first quarter.

Step#2:- Right click on database select “Archive Database”, give file name click ok…

This is the default location for archive file.

F:\Hyperion\products\Essbase\EssbaseServer\app

Step#3:- Now submit data into the existing report through lock and send method.

Step#4:- Unload the database

Step#5:- Restore the cube back using the Restore option. Right click on database and select “Restored Database”.

Step6#:- Again get back to the Excel report and refresh the report you will have the same data that you had before the updating data.

Step#7:- Now Right click on database and select replay the transaction click ok

Step#8:- Again go back to the Excel sheet and Refresh the report. Report will show the same data that you had updated from Excel

Display Transaction

When you perform backup through archive database and restored the database, transactions that occurred during backup are not included in the restore. You can post backup transactions can be captured and replayed. Thus a backup database can be recovered to the most recent state before the interruption occurred.

How you can display transactions?

Right click on database and select “Display Transactions”, specify the output file path then click ok…..

On the execution the output file will generate in to the specified folder. You can see detail transaction in to the output file.

You can also view the transaction list in to admin console. Right click on database and select “Display Transaction” click ok without specify output file path.

Replay Transaction

Replay Transactions is for restore the transactions that happened after the backup. Suppose you want restore all transactions which is in the transaction list then you need to select all the transactions check box true and click Replay button.

If you want to restore a particular transaction select that transaction from the list and click Replay button.

You can also use replay option through admin console right click on database select replay transaction.

Click ok…

Migrating Hyperion Essbase Cube
11.1.1.3 to 11.1.2

Life Cycle Management

In Essbase one of most attractive features of version 11.1.1.3 is Life Cycle Management. You can perform LCM tasks through shared service.

URL for opening shared services http:// :28080/interop/index.jsp

Life cycle management migrate all applications or individual “artifacts” between environments. If there is common environment, then you can migrate directly from application to application. Shared service used for migration when there is common environment.
You can take back up of all artifacts through Life Cycle Management utility.

1. Definitions of all databases within the applications
2. Outlines
3. Substitution Variables
4. Rule Files
5. Calculation Scripts
6. Report Scripts
7. Excel Files
8. Location Aliases
9. Security Filters

Migration Types LCM Utility

Use application to file system then from file system to the targeted application, when you are performing migration from one version to another version.

Application to File System Migration – If you have multiple Essbase applications registered in different shared services. Then this utility migrate all the necessary artifacts on to the file system. Then you can move the extracted artifacts to the target machine. In the next step again use the utility from file system to the target application.

Application to file system

This is the Essbase source application and database to perform LCM operations.

All file are in the “Mydata” folder before migration.

Log in to shared service.

This is the Group of application for different products.

List of Artifacts

The source application is “Bcub” and “Mydata” is source database. This is the list of artifacts, select artifacts to be migrated.

Select all calculation script, Excel files, location aliases and report scripts.

Select rule files, Security file, variable and Text file. After all selection of artifacts, click on Define migration…….

Source Application for migration
Click next

Select the destination for migration; you can simply migrate to any application into file system. New folder will create inside the native directory.

View of destination place

Complete migration summary for migration. Now execute migration then click ok or you can launch migration status report ………………..

Migrated report status

Newly created folder has all migrated artifacts.

Backed up artifacts

All artifacts folders backed up successfully. Backup files stored in “ \import_export\admini@Native Directory\” folder.

All backup files are in XML format. You can move all this files in other environment; were ever you want.

Calc Script

Some other information also stored inside the info folder.

Listing -> Listing file save the entire folder detailed information.

Open listing file into wordpad and can see the listing file information.

Sourceinfo -> Source information file save application version, variable, metadata information.

File system to application

All backup of artifacts is stored in the “Mydata” folder. Select all artifacts to recover application from file system to Essbase application.

Copy this newly created folder and past inside the native directory of destination server folder.
Hyperion 11.1.1.3 Source folder

Hyperion 11.1.2 Targeted folder

Login in to shared service

Open file System you will find same folder information through shared services, which you pasted inside the native directory..

Select all migrated artifacts and click on define migration.

Source application

Destination application

Destination application information

If your performing LCM migration second time for the same application then you can select “Overwrite Artifacts” option.

Migration summary
Click on “Execute Migration” then “Launch Migration Status Report”.

Migration completed successfully

Open application and check migrated artifacts.

Calc script, excel files and location aliases

Report script and rule files

All artifacts have migrated from 11.1.1.3 to 11.1.2.

Security file, substitution variables and text files

Migrated application outline.

Cross check the all files are migrated in to new application. This folder shows migrated files.

Migration Check List

You can create one migration check list, and check the status after migration.

Migration Check List

Log File

One log file creates during migrating application artifacts using LCM utility.
This log file keeps all the information of migration process.