To enable Planning recovery from a failure:
Back up related components, as described in Common Backup Tasks.
Note: | Be sure to back up the Planning system database as well as all individual application databases. |
Backups of applications and related application databases must include these items:
The application in Essbase
The relational database for Planning and Oracle Hyperion Financial Reporting
Required Planning components
Tip: | Rather than back up the entire Windows registry, you can back up only these keys for Planning: HKLM/Software/Oracle* nodes and HKLM/System/CurrentControlSet/Services/Oracle*. |
Back up the full export of Essbase data. See Essbase.
Back up any calculation scripts and substitution variables associated with Essbase.
Back up the file system folder that contains Planning shared libraries:
32-bit: EPM_ORACLE_HOME/products/Planning/lib
64-bit: EPM_ORACLE_HOME/products/Planning/lib64
UNIX: Back up custom scripts, such as startup files associated with Planning.
Back up common components in EPM_ORACLE HOME/common/planning/11.1.2.0/lib.
Ensure that the backup of EPM_ORACLE_HOME/products/Planning directory includes these files, and back them up manually if it does not:
log4J.properties
essbase.properties
See also Essbase Components.