- On the Hot Standby server, start Prinergy Administrator, and stop the Prinergy software on all servers by selecting File > Emergency Shutdown.
- If an InSite Prepress Portal or InSite Storefront server is connected to the Prinergy primary server, stop InSite services:
- On the InSite Prepress Portal/Storefront server desktop, double-click InSite Administrator.
- On the home page, click Maintenance.
- Click Shutdown, and type a shutdown message to notify users.
- Click Shutdown now.
- On the Hot Standby server, open Prinergy Administrator, and switch Prinergy to primary mode by selecting File > Switch To Primary.
If a message appears indicating that the license key and unique server ID do not match, you must proceed with step 5 below to manually retrieve a license after first completing step 4.
- Disable the PrinergyDb replication job by performing the following actions:
- Open the Double-Take Console on the failover server.
- Select the menu option Go > Manage Jobs.
- Right-click the PrinergyDb job, and select the Stop action.
- Check that the Hot Standby server is licensed. If necessary, retrieve or load a license for it:
- To open the License Information dialog box, select License > Manage License Key.
- If the server is licensed, go to the next step. If it is not licensed, click Add License Key.
- In the Add License Key dialog box, verify that your correct License ID is entered into the License ID box.
- In the Add License Key dialog box, verify that your correct Partner Place username is entered into the Partner Place username box.
Note: If necessary, you can create a new Partner Place account or change the one you are using from this dialog box.
- Select License Key.
- Click Retrieve.
If your server is able to communicate directly with the Product Registration and License Activation System (PLAS), your license(s) will be retrieved and you can start your system. Go to the next step.
If your server is behind a firewall or otherwise unable to communicate directly with PLAS, you will be given an opportunity to save an XML license request file.
- Save the XML license request file and transfer it to a system that has internet access.
- Use a web browser to navigate to the PLAS web page: http://ecentral.kodak.com/productregistration/fileupload.aspx.
- On the PLAS web page, click Browse, browse to the location where you saved the XML license request file, and click Open.
- To submit the request file and initiate creation of an XML license response file, click Upload file.
- Save the XML license response file, and transfer it to your Prinergy primary server.
- In the Add License Key dialog box in the Prinergy Administrator, select Load License key from file (main/trial).
- Click Browse and navigate to the location where you saved the XML response file.
- Click Read File.
- When the license appears in the the License Key field, click Apply.
- Start the Prinergy software on the Hot Standby server.
- If an InSite Prepress Portal or InSite Storefront server is connected to the Prinergy primary server, redirect the InSite server to the Hot Standby server:
- From the Start menu on the InSite server, select Run.
ICU, and click OK.
- Press Enter to stop InSite.
- In the InSite Configuration Utility wizard, click Next until the Prinergy primary Server Information dialog box appears.
- Type the Primary Server Name and IP address of the Hot Standby server.
- Click Next until the Configuration Summary window appears, and click Apply.
- Click Next until the Diagnostics dialog box appears, and click Close.
- At the command prompt, type:
net start InSite
- Restart Prinergy services, and verify that the InSite system is operating properly.
- If Creative Workflow server or Business Link-based software (running on a separate server) is connected to the Prinergy primary server, redirect them to the Hot Standby server. See the user documentation for this software, or contact your service representative.
- If Rules Based Automation is used, switch any dependencies on the primary server to the hot standby server:
- If remote triggers are used between rule sets on the primary server, redirect these remote triggers to the hot standby server.
- Remote triggers coming from external systems must be redirected to the hot standby server.
The Hot Standby server is now the primary server, and all jobs are present.