Two ways to backup the Planning application:
1- Using LCM to export the application in XML file which you will use it to import it into the new environment.You need also to backup the data from Essbase as well.
2- Backup all the Planning users database.
Planning Backup:
Back up these items to be able to restore to a previous state:
Planning database
Essbase outline files for all applications
Essbase security file
Essbase configuration file
Full export of Essbase data
These items require backup on an as-needed basis:
Back up recursively the entire Planning installation directories, for example: C:\Hyperion\Planning and C:\Program Files\Hyperion Solutions.
Back up the properties files (PlanningSystemDB.properties,HBRServer.properties, essbase.properties). These should have been backed up as part of the entire installation directory but are listed as a double-check measure.
On UNIX, back up custom scripts such as startup files that are associated with Oracle's Hyperion products.
Business Rules Backup:
AdminServices\storage directory
Dao.properties, Hub.properties, Locale.properties,OlapAdmin.properties, WorkflowClient.properties,HBRServer.properties, *.xml (located in the AdminServices\server directory
For detailed instructions, see the Oracle Hyperion Enterprise Performance Management System Backup and Recovery Guide. and epm_lifecycle_management.pdf
Planning Recovery:
To recover the configuration:
1. Stop Shared Services, Administration Services, Essbase, and Planning services.
2. Restore recursively the entire Hyperion directory. Using the backup tool, restore directories and files that are considered corrupted or lost.
3. Restore the Planning-specific directory recursively, for example: C:\Hyperion.
4. Restore Shared Services from the backup, using instructions in the Hyperion Shared Services Installation Guide.
5. Restore all system environment variables that were previously backed up.
6. Restore third-party Application Server directories. Using the backup tool, restore directories and files that are considered corrupted or lost.
7. Restore all registry entries pertaining to Oracle's Hyperion installation and configuration that were previously backed up.
8. Restore the entire OS System folder where it contains Planning Shared Libraries footprint, for example: C:\Windows\System. Optionally, using the backup tool, restore directories and files that are considered corrupted or lost.
9. Restore Administration Services / Business Rules database.
10. Restore the backed up Business Rules property file.
11. Restore Essbase directories, including all outline files.
12. Populate data in the Essbase database from the data backups.
13. Restore the Planning database.
14. Restore Planning property files that were backed up.
15. Restart all servers.
Business Rules Recovery:
See the Planning Configuration recovery procedures. If only data recovery is needed so that Planning and Business Rules can be rolled back to an earlier date and time, only these steps are needed.
To recover the database:
1. Restore Administration Services / Business Rules database.
2. Restore the backed up Oracle's Hyperion® Business Rules property file.
3. Restore Essbase directories, including all outline files.
4. Populate data in the Essbase database from the data backups.
5. Restore the Planning database.
6. Restore Planning property files that were backed up.
7. Restart all servers.
1- Using LCM to export the application in XML file which you will use it to import it into the new environment.You need also to backup the data from Essbase as well.
2- Backup all the Planning users database.
Planning Backup:
Back up these items to be able to restore to a previous state:
Planning database
Essbase outline files for all applications
Essbase security file
Essbase configuration file
Full export of Essbase data
These items require backup on an as-needed basis:
Back up recursively the entire Planning installation directories, for example: C:\Hyperion\Planning and C:\Program Files\Hyperion Solutions.
Back up the properties files (PlanningSystemDB.properties,HBRServer.properties, essbase.properties). These should have been backed up as part of the entire installation directory but are listed as a double-check measure.
On UNIX, back up custom scripts such as startup files that are associated with Oracle's Hyperion products.
Business Rules Backup:
AdminServices\storage directory
Dao.properties, Hub.properties, Locale.properties,OlapAdmin.properties, WorkflowClient.properties,HBRServer.properties, *.xml (located in the AdminServices\server directory
For detailed instructions, see the Oracle Hyperion Enterprise Performance Management System Backup and Recovery Guide. and epm_lifecycle_management.pdf
Planning Recovery:
To recover the configuration:
1. Stop Shared Services, Administration Services, Essbase, and Planning services.
2. Restore recursively the entire Hyperion directory. Using the backup tool, restore directories and files that are considered corrupted or lost.
3. Restore the Planning-specific directory recursively, for example: C:\Hyperion.
4. Restore Shared Services from the backup, using instructions in the Hyperion Shared Services Installation Guide.
5. Restore all system environment variables that were previously backed up.
6. Restore third-party Application Server directories. Using the backup tool, restore directories and files that are considered corrupted or lost.
7. Restore all registry entries pertaining to Oracle's Hyperion installation and configuration that were previously backed up.
8. Restore the entire OS System folder where it contains Planning Shared Libraries footprint, for example: C:\Windows\System. Optionally, using the backup tool, restore directories and files that are considered corrupted or lost.
9. Restore Administration Services / Business Rules database.
10. Restore the backed up Business Rules property file.
11. Restore Essbase directories, including all outline files.
12. Populate data in the Essbase database from the data backups.
13. Restore the Planning database.
14. Restore Planning property files that were backed up.
15. Restart all servers.
Business Rules Recovery:
See the Planning Configuration recovery procedures. If only data recovery is needed so that Planning and Business Rules can be rolled back to an earlier date and time, only these steps are needed.
To recover the database:
1. Restore Administration Services / Business Rules database.
2. Restore the backed up Oracle's Hyperion® Business Rules property file.
3. Restore Essbase directories, including all outline files.
4. Populate data in the Essbase database from the data backups.
5. Restore the Planning database.
6. Restore Planning property files that were backed up.
7. Restart all servers.
No comments:
Post a Comment