Backups and Rollback / Recovery / Migration in PBCS

In PBCS, you no longer have access to Hyperion servers, this is different from the your on-premise environment. Automated backup with job scheduler and archived them for days or weeks in case when a restoration or rollback is needed becomes unavailable. This posts a clear challenge to Hyperion administrators.

However, there is a good news. PBCS comes with a backup routine called Daily Maintenance. This will allow you to setup a time and automatically run backup, called snapshot. Well, the bad news is that you have to download them to you local computer/server then save them for archive purpose. See the following steps for setup.

Setting Up Service Maintenance Time - 

1) From Navigator, Tool, Daily Maintenance


2)  Select Start Time, then click Apply. The daily backup will go to Artifact Snapshot under Snapshot

3)  You can check the status from the Migration Status Report. It will show green Completed status when it ran successfully. You can then download them into your computer or any storage device via snapshot. (step 3 and 4 below)

 In a similar way, you can migrate app from one environment to another (ex. from DEV to PROD). See below steps
1) From Migration
2) Select categories and click Export button which will save the file to snapshots.
 

3) The migration status report will display the status








4) You can then download the file from Snapshots to your computer

5)  In a reverse way, you can Import the file for recovery or migration.

 6) Then select an artifact item(s) to recover or migration. Notice that you have the capability to import Essbase data.
One note here. An issue was encountered with regards to FDM migration - when there are dimensions you deleted (ex. Department, Version) in the source application (ex. DEV), after migration, you will notice that those two dimensions are doubled in the target application (ex. PRD). You will need go to the target system and delete the duplicate ones.

Comments

Post a Comment

Popular posts from this blog

ESSBASE: When to Use FIX vs. IF

Hyperion developers love FIX and IF, both are powerful tools and interchangeable in usage in certain circumncetances. There are also differences between the two. Let's take a look. FIX...ENFIX Usages and Rules Every FIX must be ended with ENDFIX. But it is optional to end the statement by ";" FIX Mbr can be any comma-delimited list of members, or member set functions FIX Mbr argument can be a combination of members from multiple dimensions           FIX(@CHILDREN(Qtr1),"Actual")                 Calc Dim(Accounts);           ENDFIX FIX Mbr list from the same dimension means "OR", cross dimensions means "AND" FIX cannot be used inside of formulas in outline, they can ONLY be used in calc scripts Cannot consolidate a dimension that is FIXed on. Following will generate an error when run          FIX(@CHILDREN(Qtr1),"Actual")                 Calc Dim(Accounts, Scenario);         ENDFIX It c
Read more

Essbase Currently Not Accepting Connections

Image
Application is currently not accepting connection. Essbase Error(1054009) There are occasions when users receive the above error message when they try to connect to Planning Essbase cluster via SmartView. This is normally caused by one of the following activities:   a) Database is being refreshed (Classic) or deployed (EPMA). Solutions: Wait till refresh to be completed. b) Allow connects under security is unchecked.  Solutions: In EAS, from application, select edit property, and under General tab. c) Connection is disabled using MaxL . Solutions:   Code examples: alter application $4 disable connects; alter application $4 enable connects ;   d) Connection is disabled using ESSCMD. Solutions: Code examples: DISABLELOGIN; ENABLELOGIN; When all of these are checked, and users are still not able to connect to the application, then the ultimate solution is to restart all Hyperion services.
Read more

HFM: Performance Tuning on Application

Image
There are three Planning Applications (seven Plan Types) are already there in Production, all perform well. After HFM was migrated from SIT to the Production environment recently, we immediately noticed the performance of HFM is not well. Normally it takes 15 seconds to open a HFM application in SIT, in production it takes over a minute to open (if after the services are recycled, it takes more than four minutes to open a HFM application). However, the consolidation time is sort of normal. (two to five minutes to consolidate a month, which contains about 400K of records). Following is the list of tuning activities, with regards to HFM tuning - 1) From DB side      a) Ask DBA to confirm that Auto Create Statistics is enabled for the HFM schema.      b) Have DBA check how frequently the SQL Server is doing automatic statistics maintenance.      c) Ask the DBA if the indexes may need to be defraged. DBA reported back -      a) Auto Create Statistics are enabled for all the
Read more