Recovering using the backup master domain manager

If the Symphony file is corrupt on a master domain manager, it can be regenerated using the backup master domain manager.

The regeneration of the Symphony file causes some minor loss of data. The following procedure indicates what is lost.

The prerequisite for the procedure is to have a backup master domain manager already available. A backup master domain manager is a fault-tolerant agent in the master domain with its fullstatus attribute set to yes.
Note: If you have not already created a backup master domain manager, the Symphony file cannot be recovered and the processing it contains is lost.
The procedure requires you to take the following steps on either the master domain manager or the backup master domain manager:
Note: The steps must be followed in strict order; each step description below is prefaced by the identification of the workstation on which it must be performed.
  1. On the backup master domain manager, do the following:
    1. Issue the switchmgr command.
    2. Verify that the backup master domain manager is acting as the master domain manager.
  2. From the new master domain manager set the job "limit" on the old master domain manager to “0”, using conman or the Dynamic Workload Console.

    This prevents jobs from launching.

  3. On the original master domain manager do the following:
    1. Shut down all IBM Workload Scheduler processes
    2. Rename the Sinfonia file and the corrupt Symphony file (any names will do).
  4. On the current master domain manager (previous backup master domain manager) do the following:
    1. Verify that it is linked to all agents except the old master domain manager.
    2. Shut down all IBM Workload Scheduler processes (unlink from all agents).
    3. Rename Sinfonia as Sinfonia.orig
    4. Copy Symphony to Sinfonia

      You now have identical Symphony and Sinfonia files.

  5. On the original master domain manager do the following:
    1. Issue a StartUp from the operating system's command line, to start the netman process.
    2. Verify that the process remains active.
  6. On the current master domain manager (previous backup master domain manager) do the following:
    1. Issue a StartUp from the operating system's command line, to start the netman process.
    2. Issue a conman start, or use the Dynamic Workload Console to start the current master domain manager.
    3. Issue a link to the original master domain manager.

      This action sends the Symphony file to the original master domain manager.

  7. On the original master domain manager do the following:
    1. Verify that the Symphony file is present and is the correct size (same as on the current master domain manager (previous backup master domain manager)
    2. Verify that all IBM Workload Scheduler processes are active.
  8. On the current master domain manager (previous backup master domain manager) verify that the original master domain manager is linked.
  9. On the original master domain manager do the following:
    1. Set the job "limit" on the old master domain manager to the previous level, using conman or the Dynamic Workload Console.

      Jobs can commence launching.

    2. Verify that the original master domain manager has the current job status for all agents.
    3. Issue the switchmgr command to switch control back to the original master domain manager.

Following this procedure some information is lost, in particular, any events that were suspended on the master domain manager when you started the recovery procedure.

If this procedure cannot be performed, try using the procedure that uses the logman and ResetPlan commands: Recover using the logman and ResetPlan commands.