--------------------------------------------------------------------------------
Modified 15-FEB-2011 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
1. Putting Applications in Read-Only Mode.
2. Stopping Each Application.
3. Complete Shutdown of Essbase Server.
4. Exporting the Database
5. Using the internal backup functionality in EAS.
References
--------------------------------------------------------------------------------
Applies to:
Hyperion Essbase - Version: 6.5.4.0.00 to 11.1.1.3.00 - Release: 6.5 to 11.1
Information in this document applies to any platform.
Goal
How to backup Essbase Databases
How to create a backup of Essbase
Backup of Essbase Databases
Create Essbase Backups
Backing up Essbase
Essbase Server backup
Solution
There are several different options for preparing your Essbase server and applications for backup.
It is very important that the files be in the proper mode before backups are performed.
There have been instances where the backup utility has corrupted one or more of the files used for storing data.
In these cases it was necessary to delete the files
dbname.esm,
dbname.ind,
dbname.tct,
ess0000*.ind, and
ess0000*.pag
on all volumes for the specific database and then reload the database or restore from backup.
These five files work together to make up the data in the database.
Once one of these files gets corrupted, your entire database is corrupted.
Three methods for preparing your database for tape backup or backup to a different file system are listed below.
They are intended to give a general idea about the structure of your ESSCMD script.
1. Putting Applications in Read-Only Mode.
The BEGINARCHIVE and ENDARCHIVE needs to be done on each database that you wish to backup.
This is a good method if your business is 24x7.
The drawback is that it will need to be updated every time a new database is added.
1) Set the database in read-only mode:
LOGIN "Servername" "Username" "Password";BEGINARCHIVE "AppName" "DbName" "filename";LOGOUT;EXIT;
2) Run Backup Utility.
3) End the read only mode on the database.
LOGIN "Servername" "Username" "Password";ENDARCHIVE "AppName" "DbName";LOGOUT;EXIT;
2. Stopping Each Application.
This ensures the files are not in use.
Applications will load when a user logs in to them and starts accessing data.
This method is useful as it allows the Essbase server to remain running.
If you have users who might be logging in while the backup is running you need to disable logins or shutdown the server.
Note:
Oracle recommends that you do shutdown the Essbase server at least once a month to purge any garbage that might have collected in memory.
1) To unload an Application from memory:
LOGIN "Servername" "Username" "Password";
UNLOADAPP "AppName"
LOGOUT;
EXIT;
2) Run Backup Utility.
Be aware that an Essbase Application is started as soon as a user logs on to it.
Stopping it from running will not prevent this.
3. Complete Shutdown of Essbase Server.
Drawback: Need to restart Essbase server when finished with backup.
This method will prevent people logging in and starting applications while the backup procedure is running.
1) Shut down the Essbase Server.
SHUTDOWNSERVER "Servername" "Username" "Password";
2) Run Backup Utility.
You can add bells and whistles to the basic ESSCMD script examples.
LOGOUTALLUSERS or DISABLELOGIN are commonly used.
The syntax for LOGOUTALLUSERS is:
LOGOUTALLUSERS "
It affects all users on the server except for the user issuing the command and other Administrators.
These commands will not work if there is a process running such as a calculation.
OUTPUT is also a useful command to use in your ESSCMD scripts as is the Error Handling as described in the Database Administrator's Guide.
When you run your backup utility it is important to make backups of the Application and Database directories as well as the Essbase.sec and Essbase.bak files from the Essbase\bin directory. The Essbase server must be stopped to successfully back up the .sec and .bak files.
The files that are necessary for the database to run are:
dbname.db (dbname.dbb is a backup of this file created upon successful startup of the database)
dbname.otl
dbname.ind
dbname.esm
ess0000*.ind (This will exist only if there is data in the database)
ess0000*.pag (This will exist only if there is data in the database)
dbname.tct
If Essbase is spanning drives it is necessary to make a backup of the ess0000*.* files on the other volumes.
ESSCMD scripts can be called from other batch scripts. To do this put a line like the following in a .bat file to call ESSCMD:
%ARBORPATH%\BIN\ESSCMD
4. Exporting the Database
Another option for backing up your data that works best with databases smaller than approximately 2GB is the Export command.
This is implemented through Essbase Administration Services (EAS) or ESSCMD.
The export file is limited to 2GB and must be written to one volume on the server (unless you do a parallel export - in that case multiple export files will be created).
Once the export file grows beyond 2GB a new export file will be created.
The export file cannot be spanned to multiple volumes.
The advantage of the export file is that in addition to creating a good backup file, it also checks for data integrity while performing the export because it checks every block to see if the corresponding page and index files match.
The disadvantage of the export file is that because it goes through every block (page and index files), it does take more time than just running tape backup software or copying the files.
A good approach that many companies employ is to run the export file once a week/month. In the event of corruption, restore from the last good export and reload any data that was loaded since the export was created.
Export has three different ways to export data. All data, Input level data, or Level 0 data. The determination of Level 0 and input is based upon the sparse dimensions. For example, if you choose Level 0 data for export, you may have data at upper level dense member combinations. (i.e. Using Sample Basic as an example, a block made up from New York -100-10 may contain QTR1 data inside of it.) The export files are text files that can be used to restore the database by reloading through ESSCMD or EAS. Export files can only be reloaded if members are not removed from the outline.
All Data Export: This is the most comprehensive and also most expensive in terms of space/size for your export file. Using this will not only give the largest export file, but it will also take the longest to run. If your total size of your database is small (2G or less), then you can use this method. Restoring from this method will not require recalculation since all the information is present in the export file.
Input Level Export: If you input your data in different sparse levels (sparse parent blocks " Level 0 Blocks), this is the method that you would want to employ. If you have a database that is over 2G when fully calculated, this will enable you to bring the size of the export file under the 2GB maximum. Another advantage is that if the corruption lies in a non-input block that exists as a result of a calculation (of the input blocks), you will be cleansing your database of the corruption by exporting the good blocks. Restoring from this export method will require recalculation to build upper level blocks that exist as a result of the input blocks being calculated.
Level 0 Export: If you only load at 0 level sparse blocks (All block combinations are Level 0 sparse members) and/or if you have a large database, this is probably the best method to use for exporting. This, like the previous export method will allow you to reduce your export file by not exporting calculated blocks. Just as in the previous example, if corruption exists in upper level blocks, it will not be a problem, since the export file will not contain the upper level blocks that may contain the corruption. Restoring from this export method requires recalculation to build the upper blocks that come into existence as a result of the Level 0 blocks being calculated.
If you are using export to backup your data, you need to be sure to make copies of the other important files on your system. These files include calc scripts (.csc), rules files (.rul), outline files (.otl), report scripts (.rep), ESSCMD scripts, and security files (...\Essbase\bin\Essbase.sec and Essbase.bak). Essbase must be shut down to successfully back up the security files.
5. Using the internal backup functionality in EAS.
In version 11.1.1.x and later, EAS contains a backup functionality for the data within Essbase.
A right click on the database node and selecting "ARCHIVE DATABASE" will create a complete backup of the database in a combined file that can be specified by the user.
References
NOTE:583342.1 - Restore an Essbase Application From Backup
http://download.oracle.com/docs/cd/E12825_01/epm.111/epm_backup_recovery.pdf
Related
--------------------------------------------------------------------------------
Products
--------------------------------------------------------------------------------
Middleware > Enterprise Performance Management > Essbase > Hyperion Essbase
Keywords
--------------------------------------------------------------------------------
SECURITY; RESTORE; DATA; ARCHIVING; EXPORT; INTEGRITY; READ-ONLY; BACKUP DATABASE
Errors
--------------------------------------------------------------------------------
ERROR HANDLING
Back to top
Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement Rate this document Article Rating
Rate this document
Excellent
Good
Poor
Did this document help you?
Yes
No
Just browsing
How easy was it to find this document?
Very easy
Somewhat easy
Not easy
Comments
Provide feedback for this article. Please use 'Contact Us' for other feedback.
Important Note: this feedback may be anonymously visible to other customers until processed by Oracle Support.
Cancel
No comments:
Post a Comment