Oracle Hyperion Planning Disaster Recovery Process

Oracle Hyperion Planning Disaster Recovery Process

Purpose: The below process will outline the steps to recover from an outage in the Production (PROD)
Hyperion Planning environment. 

Environment :Linux
Mountpoint:u03 this can be based on ServerAdmin Teams naming convention for the respective NAS /SAN
mount points
Recovery Steps

Task Tool Notes

Restore Cycle

1 Copy LCM backup File Using WinSCP or similar tool, copy the LCM directories from
directories system Stage Essbase to
/u03/stage/hyperion/common/import_export/admin@Nativ
e Directory
2 Copy HBR backup File Using WinSCP or similar tool, copy the HBR XML files from
files system Stage Essbase to a local machine directory.
2- Copy Reports File Using WinSCP or similar tool, copy the Reports zip files from
i backup files (this system Stage Essbase to a local machine directory.
step would not be
needed if LCM
worked
completely for
Reports)
3 Copy level zero File Copy level zero data files from the Stage Essbase server
data files system archive to the appropriate target database directory.  This
step will need to be done for all 4 applications, 5 underlying
databases: CPA_XXX, GBS_HC, XXX_XXX, XXXX_X, and
XX_XXXY.
4 Artifact inventory HSS and Connect to HSS as “admin”
– confirm each file system · Reports LCM
artifact is ·   HBR XML files (check file system)
available for ·   HSS LCM
restoration. ·  Planning LCM
·   Essbase LCM
5 Targetapplication HSS Connect to HSS as “admin”
s – confirm that ·xxxxA (Planning)
target · xxxxxO (Planning)
applications · xxxxT (Essbase)
eexist · xxxxH (Planning)

Classification: GECRB Birlasoft GDC Internal

6 Restore HSS – File 1.Connect as xadmin to HSS Stage in a PuTTY session
launch the LCM system 2.cd to
package to u03/stage/hyperion/common/utilities/LCM/9.5.0.0/bin
restore HSS to 3.  Issue command:“Utility.sh HSS_Restore_DRTest.xml”
Stage 4.When prompted, provide the user ID “admin” and the
password

7 Restore Reports– File 1.Connect as xadmin to HSS Stage in a PuTTY session

launch the LCM system 2.     cd to
package to /u03/stage/hyperion/common/utilities/LCM/9.5.0.0/bin
restore Reports 3.  Issue command:“Utility.sh Reports_Restore_DRTest.xml”
to Stage 4.When prompted, provide the user ID “admin” and the
password

8 Restore Essbase – File 1. Connect as xadmin to HSS Stage in a PuTTY session

launch the LCM system 2. cd to
package to /u03/stage/hyperion/common/utilities/LCM/9.5.0.0/bin
restore Essbase to 3.Issue command:“Utility.sh Essbase_Restore_DRTest.xml”
Stage 4. When prompted, provide the user ID “admin” and the
password

9 Restore level zero EAS Using EAS, load the level zero data file to the
and calculate XX_XXXY application.
XX_XXXY 1. Launch and confirm completion of the allocation rule
“ALLOC”.
2. Launch and confirm completion of “SDDAA”
3. Launch and confirm completion of “xxxxxxxG”
4. Launch and confirm completion of “OxxCxxLK”
1 Restore HBR EAS Since new “DR” rules will not be generated and
0 existing rules in Stage cannot be dropped, this step
will not be performed as part of the DR testing.
1 Restore XX_XXX – File 1.Connect as xadmin to HSS Stage in a PuTTY session
1 launch the LCM system 2.     cd to
package to /u03/stage/hyperion/common/utilities/LCM/9.5.0.0/bin
restore XX_XXX to 3. Issue command:“Utility.sh
Stage XX_XXX_Planning_Restore_DRTest.xml”
4.  When prompted, provide the user ID “admin” and the
password
1 Restore XXX_XXX File 1.Connect as xadmin to HSS Stage in a PuTTY session
2 – launch the LCM system 2.     cd to
package to /u03/stage/hyperion/common/utilities/LCM/9.5.0.0/bin
restore XXX_XXX 3. Issue command:“Utility.sh
to Stage XX_XXX_Planning_Restore_DRTest.xml”
4.  When prompted, provide the user ID “admin” and the
password

Classification: GECRB Birlasoft GDC Internal

 1 Restore XXXX_X – File 1.Connect as xadmin to HSS Stage in a PuTTY session
3 launch the LCM system 2.   cd to
package to /u03/stage/hyperion/common/utilities/LCM/9.5.0.0/bin
restore XXXX_X to 3.    Issue command:“Utility.sh
Stage XXXX_X_Planning_Restore_DRTest.xml”
4. When prompted, provide the user ID “admin” and the
password

1 Load each EAS Load the level zero data for each application
4 application’s data database:
1. XXXXPA:CPA_XXX
2.XXXXXPA:GBX_HC
3.  XXXXO:XXX_XXX
4. XXXX:BUDGET
5.  XXX:XX_XXXY
1 Calculate each EAS Calculate each database:
5 application’s 1. CPA_XXX:  run a calc all, which should be the default
database 2.  XX_HXX:  run a calc all, which should be the default
3.XXX_XXX: run a calc all, which should be the default
4. BUDGET: run a calc all, which should be the default
5. XX_XXXY: AXXX, xxCLxxxx, xxLCxxx, OxxxxK
1 Restore the Workspac In Workspace, navigate to the Explore directory of reports. 
6 reports e Select File | Import.  When prompted, navigate to the zip file

Validation
Cycle

1 Generate level EAS Using EAS, generate level zero extracts from each application
7 zero extract files database.
from each Name the extract files differently than the level zero file
database loaded during the restore cycle.
1 Compare and File Compare the level zero extract file loaded in the restore cycle
8 confirm system versus the level zero extracted in the prior step.  There
consistency on should be zero differences.
level zero data
1 Artifact integrity Planning In each Planning application using a mix of application roles,
9 Web confirm that each application artifact is working as expected. 
This test should cover all artifact types, including forms and
task lists.

Recovery Screen Shots

Classification: GECRB Birlasoft GDC Internal

 Copy LCM backup directories:
  Using WinSCP or similar tool, copy the LCM directories from Stage Essbase to
/u03/stage/hyperion/common/import_export/admin@Native Directory
 HBR rules in Stage mirror Production.  No action required.  NOTE – Do not take action for this step in testing.

Copy the Reports zip files.

Using WinSCP or similar tool, copy the Reports zip files from Stage Essbase to a local directory for future
import into Workspace.

 Copy level zero data files:

Copy level zero data files from the Stage Essbase server archive to the appropriate target database directory. 
This step will need to be done for all 4 applications, 5 underlying databases: CPA_XXX, PLN_HC, XXX_XXX,
XXXX_X, and XX_XXXY

The nightly backup from Prod to Stage is in a directory in Stage called /Essbase/backup/PRD_Backup.   Each
application has its own subdirectory and each day has its own ZIP folder.  See screen shot below:

Each
daily ZIP file contains two ZIP archives, use the “Essbase_app.zip” archive:

Classification: GECRB Birlasoft GDC Internal

Classification: GECRB Birlasoft GDC Internal