|How to backup HFM application for disaster recovery|
| ||Modified 15-FEB-2010|| |
Applies to:Hyperion Financial Management - Version: 220.127.116.11.00 to 18.104.22.168.00 - Release: 9.2 to 11.1
Information in this document applies to any platform.
GoalTo describe how to backup the HFM database for Disaster Recovery.
There is no single, detailed white paper document on disaster recovery because each method is different and customer specific; however; there are general procedures and guidelines that are recommended.
1. To preserve application integrity, perform standard backup and restoration procedures as dictated by the RDBMS vendor. The database files should be backed up according to standard RDBMS procedures. Once the database is up, you would need to update the UDL file to point to the new database with a user who has access to the database. Please assure that you are backing up the entire database to a file or other media, NOT just the tables.
2. Information can be found in the HFM Install guide; within the section called, "Backing Up Database Information"; which includes a table that lists the various backup and restore tasks.
3. You can also make back-up copies of the application. To make backup copies of applications, extract and save application files. For instructions on extracting files, see the Hyperion Financial Management Administrators Guide http://download.oracle.com/docs/cd/E12825_01/nav/portal_5.htm .
Extract and save these application file types to the Temp directory on the application server:
Security files (*.sec)
Metadata files (*.xml or *.app)
Member Lists files (*.lst)
Rules files (*.rle)
Data files (*.dat) - all applicable scenarios and years with data
Journals files (*.jlf) - all applicable scenarios and years with journal data
Back up all of these files:
Data Explorer grid files (*.hde)
Web data grid files (*.xml)
Web Data Entry Form files (*.wdf or *.grd)
System Report files (*.rpt, *.xml, or *.html)
EPM Backup and Recovery guide can be found here: