RedMngr Startup Operations

When BatchManagement_RedMngr starts on either the master or backup servers, it checks for the following conditions:

1. If the RedState file indicates that its server is the backup, the server operates as a backup. If no master exists, BatchManagement_RedMngr does not start. A message is generated to indicate the condition.

2. If the RedState file indicates that its server is the master, the master attempts to read the RedState file on the backup server. If a backup RedState file is not found, the RedMngr does not start and a message is generated to indicate the condition.

3. If the RedState file on the backup server is found, that file is read and its last state is determined. If the RedState of the other server is backup, the server starts as the master.

4. If the RedState file on the remote server indicates that its last state was master, the time logged to both of the RedState files is evaluated. If the RedState file on the local (interrogating) server is more recent, it starts as the master.

5. If the time in RedState file on the other server is more recent, the local (interrogating) server changes its state to backup and starts.

The Environment Display enables forcing either server to operate as the master, regardless of the RedState files on each server. In a redundant system, the Force System to Master command is enabled on the File menu of the Environment Display application.

Note: Be extremely careful when you use the Force System to Master command. When the server starts as a backup, it synchronizes all the configuration databases with those located on the master server. Therefore, if the server was previously operating as the master, the data generated during the previous processing is overwritten by the synchronization process.