Shut Down a Redundant Server

Shutting down the redundant server might be necessary in certain conditions. For example, if you make changes to the tag database on the master server and update the run-time version (while the backup is valid), the backup server might not have current tag data.

If I/O Clients (such as SysTagMngr) are running on the backup server when the master is updated, the I/O client data in memory on the backup server is not updated.

To avoid this problem, do the following:

• When you shut down a redundant system, ensure that the backup server is shut down first, then the master.

• When you start up a redundant system, start the master first, then the backup.

This sequence ensures that the run-time data is current and synchronized.