Product

• Kodak^® Prinergy^® 3.x, 4.x, with Hot Standby option
• Double-Take^®

Operating system

• Microsoft^® Windows^® 2000
• Microsoft Windows Server^® 2003

Symptoms

The Prinergy system stops responding during backup of the Oracle^® database. When Prinergy is restarted, the software may take more than 30 minutes to start up.

Both the Oracle backup and the Prinergy backup take a long time to complete. One customer reported that it took up to 21 hours for their backup to tape to finish.

Note: If you stop the Double-Take software or disconnect the PrinergyDB replication set, Prinergy responds normally during an Oracle backup, and the backup completes in a more reasonable time.

In the properties of the PrinergyDB replication set, the *.bck file is not excluded.

Cause

Older versions of the HotStandby installer included the *.bck files in the replication. The way that Oracle generates the *.bck files during replication causes the Double-Take software to slow down the system.

Solution

On the primary server, replace the PrinergyDB replication set with one that excludes the *.bck files from the replication.

Note: This problem is fixed in the HotStandby with Double-Take installer, 651-00325B Rev A or later.

1. On the primary server, open the Double-Take Management Console.
2. In the Management Console window, log on to the primary server and the failover server.
3. Select the primary server.
4. Disconnect the PrinergyDB replication set (repset).
5. Delete the PrinergyDB replication set.
6. Download the following scripts to the server desktop:
   • CreateRepset.cmd
   • GetOraclePath.cmd
7. Move the CreateRepset.cmd script to the Primary %ProgramFiles%\DoubleTake\Creo folder to replace the old version.
8. Move the GetOraclePath.cmd script to the Primary %ProgramFiles%\DoubleTake\Creo\bin folder to replace the old version.
9. Run the CreateRepset.cmd script to create the PrinergyDB replication set.
10. In the Management Console window, connect the PrinergyDB replication set to start mirroring and replication.

Technical contact(s)

Submitted by

Date submitted

15 Aug 2007