This document outlines the recommended strategies for upgrading to ClearSCADA 2009 R2.

For details on version compatibility of clients and servers as well as server-server for redundancy, please refer to the ClearSCADA Version Compatibility Matrix.

ClearSCADA 2009 R1

ClearSCADA 2009 R1 Standalone Server (includes all R1 Service Packs)

• Shut the server down.
• Upgrade the server to ClearSCADA 2009 R2.
• Restart the server.

ClearSCADA 2009 R1 Main and Standby Servers with no Clients

• Shut the standby server down.
• Upgrade the standby server to ClearSCADA 2009 R2.
• Restart the standby server.
• Wait for the server to fully synchronize with the main server and go into the standby state.
• Shut the main server down. The upgraded standby server will take over as the main server.
• Upgrade the previously main server to ClearSCADA 2009 R2.
• Restart the previously main server. The server will synchronize with the new main server and go into the standby state.

ClearSCADA 2009 R1 Main and Standby Servers with Clients

If there are a small number of clients that can easily be upgraded:

• Upgrade each client in turn to ClearSCADA 2009 R2.
• Shut the standby server down.
• Upgrade the standby server to ClearSCADA 2009 R2.
• Restart the standby server.
• Wait for the server to fully synchronize with the main server and go into the standby state.
• Shut the main server down. The upgraded standby server will take over as the main server.
• Upgrade the previously main server to ClearSCADA 2009 R2.
• Restart the previously main server. The server will synchronize with the new main server and go into the standby state.

If there are a large number of clients or clients that cannot easily be upgraded (due to location, availability, etc.):

• Shut the standby server down.
• Upgrade the standby server to ClearSCADA 2009 R2.
• Restart the standby server.
• While the standby synchronizes with the main (and no clients are yet connected), connect to the standby using Server Configuration and configure the standby server to emulate ClearSCADA 2009 R1
• Wait for the server to fully synchronize with the main server and go into the standby state.
• Shut the main server down. The upgraded standby server will take over as the main server.
• Upgrade the previously main server to ClearSCADA 2009 R2.
• Restart the previously main server.
• While the previously main server synchronizes with the upgraded standby server (and no clients are yet connected), connect to the previously main server using Server Configuration and configure the previously main server to emulate ClearSCADA 2009 R1.
• Restart the previously main server. The server will synchronize with the new main server and go into the standby state.
• Upgrade each client in turn to ClearSCADA 2009 R2.
• When all clients are updated to ClearSCADA 2009 R2, turn off emulation on both servers (one at a time) and restart.

Notes

1. Once the ClearSCADA 2009 R1 emulation has been enabled on both the main and standby servers, either ClearSCADA 2009 R1 or ClearSCADA 2009 R2 clients can be used to connect to the servers.
2. Once all of the clients have been upgraded to ClearSCADA 2009 R2, the ClearSCADA 2009 R1 emulation should be disabled on both the main and standby servers.

ClearSCADA 2007 R1

ClearSCADA 2007 R1 Standalone Server (includes all R1 Service Packs)

• Shut the server down.
• Upgrade the server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA license on the server.
• Restart the server.

ClearSCADA 2007 R1 Main and Standby Servers with no Clients

• Shut the standby server down.
• Upgrade the standby server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA license on the standby server.
• Restart the standby server.
• Wait for the server to fully synchronize with the main server and go into the standby state.
• Shut the main server down. The upgraded standby server will take over as the main server.
• Upgrade the previously main server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA license on the previously main server.
• Restart the previously main server. The server will synchronize with the new main server and go into the standby state.

Notes

1. User favorites will not be accessible from non-ClearSCADA 2009 R2 clients.
2. Older versions of ClearSCADA allowed instances to be created without templates. This has been prevented in ClearSCADA 2009 R2. Hence, when upgrading ensure that all instances are linked to their corresponding templates. Restarting the ClearSCADA Server will convert all invalid instances into groups in ClearSCADA 2009 R2.

ClearSCADA 2007 R1 Main and Standby Servers with Clients

If there are a small number of clients that can easily be upgraded:

• Upgrade each client in turn to ClearSCADA 2009 R2.
• Shut the standby server down.
• Upgrade the standby server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA license on the standby server.
• Restart the standby server.
• Wait for the server to fully synchronize with the main server and go into the standby state.
• Shut the main server down. The upgraded standby server will take over as the main server.
• Upgrade the previously main server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA license on the previously main server.
• Restart the previously main server. The server will synchronize with the new main server and go into the standby state.

If there are a large number of clients or clients that cannot easily be upgraded (due to location, availability, etc.):

• Shut the standby server down.
• Upgrade the standby server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA license on the standby server.
• Restart the standby server.
• While the standby synchronizes with the main (and no clients are yet connected), connect to the standby using Server Configuration and configure the standby server to emulate ClearSCADA 2007 R1
• Wait for the server to fully synchronize with the main server and go into the standby state.
• Shut the main server down. The upgraded standby server will take over as the main server.
• Upgrade the previously main server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA license on the previously main server.
• Restart the previously main server.
• While the previously main server synchronizes with the upgraded standby server (and no clients are yet connected), connect to the previously main server using Server Configuration and configure the previously main server to emulate ClearSCADA 2007 R1.
• Restart the previously main server. The server will synchronize with the new main server and go into the standby state.
• Upgrade each client in turn to ClearSCADA 2009 R2.
• When all clients are updated to ClearSCADA 2009 R2, turn off emulation on both servers (one at a time) and restart.

Notes

1. Once the ClearSCADA 2007 R1 emulation has been enabled on both the main and standby servers, either ClearSCADA 2007 R1 or ClearSCADA 2009 R2 clients can be used to connect to the servers.
2. Once all of the clients have been upgraded to ClearSCADA 2009 R2, the ClearSCADA 2007 R1 emulation should be disabled on both the main and standby servers.
3. User favorites will not be accessible from non-ClearSCADA 2009 R2 clients.

ClearSCADA 2007 R0

ClearSCADA 2007 R0 Standalone Server

• Shut the server down.
• Upgrade the server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA license on the server.
• Restart the server.

ClearSCADA 2007 R0 Main and Standby Servers with no Clients

• Shut the standby server down.
• Upgrade the standby server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA license on the standby server.
• Restart the standby server.
• Wait for the server to fully synchronize with the main server and go into the standby state.
• Shut the main server down. The upgraded standby server will take over as the main server.
• Upgrade the previously main server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA license on the previously main server.
• Restart the previously main server. The server will synchronize with the new main server and go into the standby state.

Notes

1. User favorites will not be accessible from non-ClearSCADA 2009 R2 clients.
2. Older versions of ClearSCADA allowed instances to be created without templates. This has been prevented in ClearSCADA 2009 R2. Hence, when upgrading ensure that all instances are linked to their corresponding templates. Restarting the ClearSCADA Server will convert all invalid instances into groups in ClearSCADA 2009 R2.

ClearSCADA 2007 R0 Main and Standby Servers with Clients

If there are a small number of clients that can easily be upgraded:

• Upgrade each client in turn to ClearSCADA 2009 R2.
• Shut the standby server down.
• Upgrade the standby server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA license on the standby server.
• Restart the standby server.
• Wait for the server to fully synchronize with the main server and go into the standby state.
• Shut the main server down. The upgraded standby server will take over as the main server.
• Upgrade the previously main server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA license on the previously main server.
• Restart the previously main server. The server will synchronize with the new main server and go into the standby state.

If there are a large number of clients or clients that cannot easily be upgraded (due to location, availability, etc.):

• Shut the standby server down.
• Upgrade the standby server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA license on the standby server.
• Restart the standby server.
• While the standby synchronizes with the main (and no clients are yet connected), connect to the standby using Server Configuration and configure the standby server to emulate ClearSCADA 2007 R0.
• Wait for the server to fully synchronize with the main server and go into the standby state.
• Shut the main server down. The upgraded standby server will take over as the main server.
• Upgrade the previously main server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA license on the previously main server.
• Restart the previously main server.
• While the previously main server synchronizes with the upgraded standby server (and no clients are yet connected), connect to the previously main server using Server Configuration and configure the previously main server to emulate ClearSCADA 2007 R0.
• Restart the previously main server. The server will synchronize with the new main server and go into the standby state.
• Upgrade each client in turn to ClearSCADA 2009 R2.
• When all clients are updated to ClearSCADA 2009 R2, turn off emulation on both servers (one at a time) and restart.

Notes

1. Once the ClearSCADA 2007 R0 emulation has been enabled on both the main and standby servers, either ClearSCADA 2007 R0 or ClearSCADA 2009 R2 clients can be used to connect to the servers.
2. Once all of the clients have been upgraded to ClearSCADA 2009 R2, the ClearSCADA 2007 R0 emulation should be disabled on both the main and standby servers.
3. User favorites will not be accessible from non-ClearSCADA 2009 R2 clients.

ClearSCADA 2005 R1

ClearSCADA 2005 R1 Standalone Server

• Shut the server down.
• Upgrade the server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA licence on the server.
• Restart the server.

ClearSCADA 2005 R1 Main and Standby Servers with no Clients

• Shut both the main and standby servers down.
• Upgrade the main server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA licence on the main server.
• Restart the main server.
• If the main server has upgraded correctly, upgrade the standby server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA licence on the standby server.
• Restart the standby server.

Notes

1. It is important that the server that was the last to be shut down in a redundant pair is the first to be restarted to ensure that data received by this server is not overwritten by data from an older server.
2. Older versions of ClearSCADA allowed instances to be created without templates. This has been prevented in ClearSCADA 2009 R2. Hence, when upgrading ensure that all instances are linked to their corresponding templates. Restarting the ClearSCADA Server will convert all invalid instances into groups in ClearSCADA 2009 R2.

ClearSCADA 2005 R1 Main and Standby Servers with Clients

If there are a small number of clients that can easily be upgraded:

• Upgrade each client in turn to ClearSCADA 2009 R2.
• Shut both the main and standby servers down.
• Upgrade the main server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA licence on the main server.
• Restart the main server.
• If the main server has upgraded correctly, upgrade the standby server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA licence on the standby server.
• Restart the standby server.

If there are a large number of clients or clients that cannot easily be upgraded (due to location, availability, etc.):

• Shut both the main and standby servers down.
• Upgrade the main server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA licence on the main server.
• Restart the main server.
• Configure the main server to emulate ClearSCADA 2005 R1.
• Restart the main server.
• If the main server has upgraded correctly, upgrade the standby to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA licence on the standby server.
• Restart the standby server.
• Configure the standby server to emulate ClearSCADA 2005 R1.
• Restart the standby server.
• Upgrade each client in turn to ClearSCADA 2009 R2.

Notes

1. It is important that the server that was the last to be shut down in a redundant pair is the first to be restarted to ensure that data received by this server is not overwritten by data from an older server.
2. Once the ClearSCADA 2005 R0 emulation has been enabled on both the main and standby servers, either ClearSCADA 2005 R1 or ClearSCADA 2009 R2 clients can be used to connect to the servers.
3. Once all of the clients have been upgraded to ClearSCADA 2009 R2, the ClearSCADA 2005 R1 emulation should be disabled on both the main and standby servers.
4. User favorites will not be accessible from non-ClearSCADA 2009 R2 clients.
5. Older versions of ClearSCADA allowed instances to be created without templates. This has been prevented in ClearSCADA 2009 R2. Hence, when upgrading ensure that all instances are linked to their corresponding templates. Restarting the ClearSCADA Server will convert all invalid instances into groups in ClearSCADA 2009 R2.

ClearSCADA 2005 R0

ClearSCADA 2005 R0 Standalone Server

• Shut the server down.
• Upgrade the server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA licence on the server.
• Restart the server.

ClearSCADA 2005 R0 Main and Standby Servers with no Clients

• Shut both the main and standby servers down.
• Upgrade the main server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA licence on the main server.
• Restart the main server.
• If the main server has upgraded correctly, upgrade the standby server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA licence on the standby server.
• Restart the standby server.

Notes

1. It is important that the server that was the last to be shut down in a redundant pair is the first to be restarted to ensure that data received by this server is not overwritten by data from an older server.
2. Older versions of ClearSCADA allowed instances to be created without templates. This has been prevented in ClearSCADA 2009 R2. Hence, when upgrading ensure that all instances are linked to their corresponding templates. Restarting the ClearSCADA Server will convert all invalid instances into groups in ClearSCADA 2009 R2.

ClearSCADA 2005 R0 Main and Standby Servers with Clients

• Shut both the main and standby servers down.
• Upgrade the main server to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA licence on the main server.
• Restart the main server.
• Configure the main server to emulate ClearSCADA 2005 R0.
• Restart the main server.
• If the main server has upgraded correctly, upgrade the standby to ClearSCADA 2009 R2.
• Upgrade the ClearSCADA licence on the standby server.
• Restart the standby server.
• Configure the standby server to emulate ClearSCADA 2005 R0.
• Restart the standby server.
• Upgrade each client in turn to ClearSCADA 2009 R2.

Notes

1. It is important that the server that was the last to be shut down in a redundant pair is the first to be restarted to ensure that data received by this server is not overwritten by data from an older server.
2. Once the ClearSCADA 2005 R0 emulation has been enabled on both the main and standby servers, either ClearSCADA 2005 R0 or ClearSCADA 2009 R2 clients can be used to connect to the servers.
3. Once all of the clients have been upgraded to ClearSCADA 2009 R2, the ClearSCADA 2005 R0 emulation should be disabled on both the main and standby servers.
4. User favorites will not be accessible from non-ClearSCADA 2009 R2 clients.
5. Older versions of ClearSCADA allowed instances to be created without templates. This has been prevented in ClearSCADA 2009 R2. Hence, when upgrading ensure that all instances are linked to their corresponding templates. Restarting the ClearSCADA Server will convert all invalid instances into groups in ClearSCADA 2009 R2.

Other Versions

Customers who participated in the beta testing of ClearSCADA 2009 R2 should follow the instructions below for upgrading to the release version.

ClearSCADA 2009 Pre-Release Builds Standalone Server

• Shut the server down.
• Upgrade the server to ClearSCADA 2009 R2.
• Restart the server.

ClearSCADA 2009 Pre-Release Builds Main and Standby Servers with no Clients

• Shut the standby server down.
• Upgrade the standby server to ClearSCADA 2009 R2.
• Restart the standby server.
• Wait for the server to fully synchronize with the main server and go into the standby state.
• Shut the main server down. The upgraded standby server will take over as the main server.
• Upgrade the previously main server to ClearSCADA 2009 R2.
• Restart the previously main server. The server will synchronize with the new main server and go into the standby state.

ClearSCADA 2009 Pre-Release Builds Main and Standby Servers with Clients

• Shut the standby server down.
• Upgrade the standby server to ClearSCADA 2009 R2.
• Restart the standby server.
• Wait for the server to fully synchronize with the main server and go into the standby state.
• Shut the main server down. The upgraded standby server will take over as the main server.
• Upgrade the previously main server to ClearSCADA 2009 R2.
• Restart the previously main server. The server will synchronize with the new main server and go into the standby state.