Lifecycle Management does not replace the need for a physical backup of servers and content. Because Lifecycle Management can export most application artifacts, it is well-suited for archiving application content. You can use Lifecycle Management for the following use cases:
Making a temporary backup of artifacts when a business user wants to edit the application content. For example, if a change must be made to a dimension in Essbase or Planning, to ensure that the changes can be reverted if something goes wrong, you can perform an Lifecycle Management export of the dimension before making edits. This exported dimension will serve as a temporary backup. Then you can edit the dimension in the product.
Archiving artifacts before performing an import: If you are migrating content from a test system to production, you may want to archive the production artifacts by exporting them and checking the same into any version control system.
Note: | Lifecycle Management can be used only as a logical backup and recovery solution and is not recommended as a solution for backing up and recovering data. Many products provide their own data backup and recovery solutions. These solutions are documented in the Oracle Hyperion Enterprise Performance Management System Backup and Recovery Guide. |