Restoring the primary server to normal operation

NOTE: This procedure assumes that the Main (rebuilt) Primary system is configured as it was prior to the performed failover as well as Carbonite (Double-Take) application is installed and its services are running but the PrinergyDB and PrinergyDbRestore Replication sets are NOT CREATED. However, if Primary was fixed w/o redeploying new image, make sure these two replication sets are STOPPED

If this is not the case, rebuild Primary from scratch using the following steps:

1. Reinstall and configure the main Primary with the same Windows OS and Prinergy version as before, matching EPM+ server. H/W Options:
1. From a saved Ghost: If the saved (ghost) image is matching the current running EPM+ Windows OS and Prinergy version, restore the server using that saved image and go to step 2. If Prinergy version is inferior, upgrade Prinergy.
2. From scratch: Deploy WIM image of current running EPM+ Windows OS and Prinergy version. If Prinergy version is inferior, upgrade Prinergy.

                 Note: You may need to release the License ID in PLAS.

       2. Restore the Prinergy Configuration from the latest available Prinergy daily backup by using the rehost tool.  You must keep the same server name and IP address as prior to the failover. There’s no need to restore the database with the rehost tool.

       3. Install Carbonite (Double-Take) but do not create the PrinergyDB and the PrinergyDbRestore Replication Sets. 

           Very important Note: Creating the PrinergyDB replication set on the Primary might break the entire database restore.

       4. Check for successful starting/running Prinergy on the main Primary.

After the main primary server is repaired, revert to using it as the primary server and using the Hot Standby server as a secondary server.

When you switch the Hot Standby failover server back to secondary server status, the Prinergy system resumes normal operations with Hot Standby protection again ready to use when needed. The original primary server and all secondary servers and render stations are connected correctly.
warning: If you do not follow the procedure for reverting to normal operations correctly, the database may become corrupted.

If you are reverting after a planned failover, verify that you have a current Oracle database backup and that you have performed a cold database backup before you return the Hot Standby server to secondary mode.

Important: You must perform this procedure in the exact, numbered sequence that follows. Failure to do so can permanently corrupt the database and require restoring the database from backup.

1. On the primary server, log into Double-Take Console, and confirm that the PrinergyDB replication job is stopped.
   Important: You must disconnect the PrinergyDB replication job otherwise the database will be corrupted.
2. Stop Prinergy on all servers.
3. Verify that the primary server's network cable is connected.
4. On the failover server, switch the failover server to a secondary server again by selecting Administrator > Revert to Secondary.
   Note: To save time when performing test with large databases, you can skip the remaining steps which restore the Oracle data files. However, any work done while the system is in failover mode is lost.
   Important: Take a cold database backup of the failover server database in case the restoration procedure is not followed correctly causing database corruption:
   
   1. On the failover server, make sure the Oracle services are stopped. The Revert to Secondary operation should have stopped the Oracle services but confirm this before taking the cold backup.
   2. Make a copy of the C:\Oracle\oradata folder and the J:\Oracle folder
5. Run the DisableOracle.cmd script and verify that there are no errors.
   1. On the primary server, run the DisableOracle.cmd script, located at <SystemDrive>:\Program Files\Vision Solutions\Double-Take\creo\. When prompted, confirm that you want to stop and disable Oracle.
   2. Check the output of the DisableOracle.cmd script for errors. If there are errors, do not proceed. Contact your service representative.
6. Enable the PrinergyDbRestore job, by performing the following actions:
   1. On the failover server, in the Double-Take Console, select Manage Jobs.
   2. Under View Job Details, confirm that Target route is set for primary server IP address
   3. Right-click the PrinergyDbRestore job, and select Start.
   4. Wait for the Activity to become Protecting and the Mirror Status to become Idle.
   5. Right-click the PrinergyDbRestore job, and select Stop.
      Note: If there is an unexpected interruption, such as a power outage, you can restart the restore process from the step to run DisableOracle.cmd and onwards. The restore process overwrites the unusable database on the primary server with the still-good copy from the failover server.
7. On the primary server, start Oracle by running the EnableOracle script at <SystemDrive>:\Program Files\Vision Solutions\Double-Take\creo.
8. From the primary server, start Prinergy on all servers. Ensure Prinergy is operating properly before proceeding to the next step.
9. Reconfigure Double-Take to replicate the data onto the failover server again by performing the following actions:
   1. In the Double-Take Console, select Manage Jobs.
   2. Right-click the PrinergyDB job and select Start.
   3. Wait for the Activity to become Protecting and the Mirror Status to become Idle.
10. If an InSite Prepress Portal or InSite Storefront server is connected to the Hot Standby server, redirect the InSite server to the primary server:
    1. From the Start menu on the InSite server, select Run.
    2. Type ICU, and click OK.
    3. Press Enter to stop InSite.
    4. In the InSite Configuration Utility wizard, click Next until the Prinergy primary Server Information dialog box appears.
    5. Type the Primary Server Name and IP address of the primary server.
    6. Click Next until the Configuration Summary window appears, and click Apply.
    7. Click Next until the Diagnostics dialog box appears, and click Close.
    8. At the command prompt, type:
       net start InSite
exit
    9. Restart Prinergy services, and verify that the InSite system is operating properly.
11. If Creative Workflow server or Business Link-based software (running on a separate server) is connected to the Hot Standby server, redirect them to the primary server. See the user documentation for this software, or contact your service representative.
12. If Rules Based Automation is used, switch any dependencies on the hot standby server back to the primary server:
    • If remote triggers are used between rule sets, redirect these remote triggers back to the primary server.
    • If remote triggers are coming from external systems, redirect these remote triggers to the primary server.
13. Once confident that everything is working correctly, perform the starting database replication procedure.