Cloning, Migrating, Backup Oracle Governance Risk Compliance Manager

APPLIES TO:

Oracle Governance, Risk and Compliance Manager Version 6.0 to 7.8
Information in this document applies to any platform.

SYMPTOMS:

What tools are available or best methods for cloning or migrating Business Processes, Risks, Controls, etc from a test environment to a production environment? Can a backup and restore to another system accomplish a system migration?

CHANGES:

New Installation

CAUSE:

Looking for a method of migrating a GRCM system from one server to another.

SOLUTION:

Backing up the GRCM system includes making a copy of the GRCM file system, Stellent Content Server file system,
Windows registry, IIS web server, and the database. A copy of these should be made at the same point in time,
where there are no updates to the GRCM system. When you restore these from backup they can not be out of sync
or the Business Processes may be corrupt. A restore would be copying over the existing file system, registry, and
database. After a file system restore it is recommended to complete rebuild the search collection on the Stellent
Content Server.
Moving a GRCM installation, Content Server file, Windows Registry, IIS and database to another system requires a
consulting services engagement. There are no tools or supported processes to follow in order to migrate or clone
the installation. If you require assistance for the cloning or migrating of data, the Oracle Consulting Services can be
engaged to assist. Oracle support strongly recommends that all migrations and cloning of data be performed by an
Oracle Consulting Services engagement.
Below are some general steps which in theory could work in cloning GRCM data but that have not been tested and
will NOT be supported in any way. For GRCM data cloning, the typical CMU/archiving steps will not work correctly
since the archive will not archive over any data in a current workflow. For GRCM data, there is usually quite a few
items that are in an active workflow.
1. Shutdown all content server and GRCM services for the Development Instance and the Production Instance.
2. Backup production file system and database if desired. It would probably be good to backup all development data as well.
3 Export out the entire Development database.
4. In Production, import the exported copy of the Development database and overwrite all Production Database
information.
5. Copy over all of the directories and files in the Development content server install directory to the production file
system. (Ex: C:/stellent/idcm1).
6. Edit the content server config files and change host names, installation locations, and DB info to match
Production system.
7. Edit the GRCM config files to match any differences between the Development and Production data like the map
document content id values.
8. Restart all services and check the event viewer for any errors.
9. Rebuild the Content Server index.
10. Check the Web server instance name and host name may need to be changed.

Note that the above steps are not a supported solution, and have not been tested, but rather some general conceptual instructions for cloning GRCM data. If you follow the above steps and run into any problems, Oracle support will NOT assist in resolving the issues.