Updating on redundant systems

When the system is in operation and the primary server becomes inoperative, or if you take it offline to perform maintenance or make changes, you can revert to the standby server with minimal or no interruption to the system.

When the primary server is brought back online, the system returns control of the I/O devices to the primary server.

First, make your desired changes, such as the following tasks:

• See topics within the Define one I/O device in a project section to learn how to add an I/O device.
• Remove an I/O device from a project
• Update TGML diagrams on redundant systems
• Update alarm thresholds on redundant systems

After implementing changes, do the following:

Compile and restart a redundant system to implement changes

Before you begin, observe the following:

notice

LOSS of data

Backup your primary and standby projects prior to implementing changes in a redundant system.

Failure to follow these instructions can result in a loss of data.

• For details, see Back up the Power Operation Studio project. If you encounter issues, Restore the Power Operation Studio project.
• When updating projects on redundant systems, always begin with the standby server (the non-active server) unless it is not possible to do so.
• Verify that both the primary and standby servers are running.
• If using any event notifications, it is recommended that you put the system into maintenance mode while implementing changes during failover, as this may trigger changes for miscellaneous alarms and events.

To compile and restart a redundant system to implement changes:

1. Implement your changes on the standby server.
2. In Power Operation Studio, verify that the active project is selected > select Compile. Even if the project is compiled, it is recommended that you compile again.
3. (Optional) Select Setup Wizard > select Next through to the end of the Computer Setup Wizard. Do not change any settings.
4. Open the Power Operation Runtime Manager.
5. In the Runtime Manager, confirm all Citect processes show their status as Running. It is recommended that you confirm all processes are also running on the primary server, as the standby server will need to be restarted.



6. Select Restart All. Confirm that all processes restart and resume their Running status.
7. Confirm your changes are present on the standby server.
8. When the confirmed changes are complete, back up the standby server's project by navigating to Power Operation Studio and select Backup.
9. In the Backup Project window, select the Save Included Projects checkbox.



10. Browse to the location where you want to store the backup file.
11. Maintain the default options enabled. Select OK.
12. When complete, copy the backup to the primary server.
13. On the primary server, open Power Operation Studio.
14. In the Projects window, with the Active Project selected, from the Backup drop-down menu, choose Restore.
15. In the Restore Project dialog, browse to and select the project backup copied from the standby server.
16. In the Included Projects section, select the Select all included projects checkbox. Select all projects, with the exception of PLS_Include. Do not overwrite PLS_Include with any backup.
17. In the To section, enable the Current Project radio button.
18. In the Options section, clear the Configuration files checkbox.
19. Select OK.
20. In the warning, select Yes.
21. When the restore is complete, compile the project.
22. When the compile is complete, select Setup Wizard > select Next through to the end of the Computer Setup Wizard. Do not change any settings.
23. When the Setup Wizard is complete, confirm the new project has the changes added on the Standby project.
24. When all changes are confirmed, open the Power Operation Runtime Manager.
25. In the Runtime Manager, confirm all Citect processes show their status as "Running". It is recommended that you confirm all processes are also running on the primary server, as the standby server will need to be restarted.
26. Select Restart All. Confirm that all processes restart and resume their Running status.
27. Confirm your changes are present on the standby server.
28. (Optional) Restart disabled or stopped notification services.