Disaster Recovery Instructions (May 2008):

I. Preparing for Disaster Recovery:

1. While logged into the EE web application, choose the Administrative Tasks menu choice.
2. Under Database Utilities, choose Generate Disaster Recovery Archive.
3. Verify the TNS Names entry is correct, enter the password for the EE user, and press: Submit.
4. Watch the updates on the screen as the process begins.
5. Your system is now backed up and can be restored to this point in time.

Alternately

1. You can use a command line similar to this to automate the Preparation (for example nightly)
2. java -cp "C:\Program Files\Elements\common\lib\ojdbc14.jar";"C:\Program Files\Elements\webapps\ee\WEB-INF\lib\server.jar"; com.ee.server.servlets.disasterRecovery.DisasterRecovery "C:\Program Files\Elements\webapps\ee\WEB-INF\sql\dr" "C:\Program Files\Elements\conf\Catalina\localhost\ee.xml"

Check the log from the most recent Preparation with the Disaster Recovery Log (Last Run) filter.

II. Doing a Disaster Recovery Restore:

1. Ensure that the Webserver service is shutdown, and no one is logged into ORACLE as the EE user.
2. The Recovery Archives will be on the Webserver box, in thewebapps\ee\WEB-INF\sql\dr directory in your Elements install directory.
3. Find the Restore Archive directory you wish to use, and unzip the zipfile of the same name that into the same directory, overwriting any files that may already exist there.
4. Go to the webapps\ee\WEB-INF\sql directory in your Elements install directory and create the EE user on the New Destination database by running the MAKE_EE script logged into SQL*Plus as the sys as sysdba user where <xxx> is the desired password the EE user should be created with. @make_ee <xxx>
5. Associate any pre-existing roles that the EE user had before with the new EE user by running the SET_EE_ROLES script logged into SQL*Plus as the sys as sysdba user: @dr\<restore_archive_directory>\set_EE_Roles (ex: @dr\Disaster-Recovery-2008-05-23-090836\set_EE_Roles)
6. While still in thewebapps\ee\WEB-INF\sql directory, connect in SQL*Plus as the EE user on the destination database and run: @ee_roles.sql @ dr\<restore_archive_directory>\make_EE_roles (ex: @dr\Disaster-Recovery-2008-05-23-090836\make_EE_Roles)
7. Run the import into the destination database from a command line prompt run using  xxx as the  EE User Password,yyy as the TNS Names entry for new database,zzz as the name of the .DMP file in the Recovery Archive zip (ie, dr\ Disaster-Recovery-2007-01-29-091456\Disaster-Recovery-2007-01-29-091456.dmp) imp EE/xxx@yyy file=zzz.DMP FROMUSER=EE TOUSER=EE (ex imp ee/xxx@yyy file=dr\Disaster-Recovery-2008-05-23-090836\Disaster-Recovery-2008-05-23-090836.dmp FROMUSER=EE TOUSER=EE)
8. While still in the webapps\ee\WEB-INF\sql directory, connect in SQL*Plus as the EE user on the destination database and run: @ee_drop_policies Still in SQL*Plus, as EE run the DISASTER_RECOVERY update procedure: EXEC DISASTER_RECOVERY;
9. Still in SQL*Plus, view a log of the Recovery procedure by running this script: @ee_dr_log_view

   Take care of any listed errors, and the log will say if it is OK to just rerun the EXEC DISASTER_RECOVERY part or, if the entire DR Recovery process will need to be completed again after the error is taken care of.

10. Still in SQL*Plus create any external user Synonyms on EE tables by running: @ee_make_user_synonyms
11. Still in SQL*Plus turn on the policies by running: @ee_add_policies
12. EXIT SQL*Plus before doing anything else to reset the context.
13. Copy any files in the Restore Archive uploads directory into the webapps\ee\uploads directory in your Elements install directory. (Note: The uploads Recovery directory may not exist depending on your installation).