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:
- Reinstall and configure the main Primary with the same Windows OS and Prinergy version as before, matching EPM+ server. H/W Options:
- 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.
- 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.
- 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.
- 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.
- 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.
...