Restoring the primary server

To restore the primary server to its operational status, you must schedule the server startup and switch the LoadBalanceWeight attributes so that you prevent the primary and backup server from talking to the repository at the same time.

About this task

During the recovery process, some users can experience a brief disconnect or delay, but after the primary server is back up, it resumes taking requests from the Web server.

To restore the primary server to operational status:

Procedure

  1. Make sure the primary server is powered off.
  2. In the Web server plugin-cfg file, locate the entry for the PrimaryNode01_server1 and change the LoadBalanceWeight attribute from "0" to "1".
  3. In the Web server plugin-cfg file, locate the entry for the BackupNode01_server1 and change the LoadBalanceWeight attribute from "1 to "0".
  4. Save the edits to the Web server plugin-cfg.xml file.
  5. Shut down the backup server. After it is powered off, start the primary server.
  6. When the primary server is back up and has resumed taking requests, you can start the backup server again.

Feedback

Did this help? You can provide feedback at Jazz.net (registration required): Comment in the forums or submit a bug