Product version

Log on to rate and give feedback 1 2 3 4 5

Concept

Products: AS-B, Enterprise Central, Enterprise Server, AS-P, Project Configuration Tool

Functionalities: Basic Functionality

Product version: 3.3, 2022

7/23/2021

Automation Server Replacement Using Restore

arrow1_rotation

Automation Server Replacement Using Restore Workflow

Backup and Restore helps assure that automation server data can be restored to a replacement automation server in the event of detected failure, or to the same automation server in the event of data loss. As a precaution, you back up your automation servers regularly so that you can use the most current backup to restore the automation server data to a replacement automation server. You also configure the new automation server to match the name and the network settings of the replaced automation server so the system can identify this automation server when online.

Supported cases of automation server replacements

The following cases of automation server replacements are supported using restore:

Replacing an automation server with an automation server of the same automation server type
Replacing Automation Server with a automation server

To replace Automation Server with a AS-P server, you first need to install the server software on the new AS-P server before you can restore the configuration data and historical data from the replaced Automation Server. For more information, see Uploading and Upgrading an Automation Server .

Notice
Loss of data If you replace an Automation Server with an AS-P server, consider the difference in RS-485 bias voltage between the two servers to avoid decreased performance and reliability of the RS-485 network. For more information, see RS-485 Communications . Failure to follow these instructions can result in loss of data.

Notice

Loss of data

If you replace an Automation Server with an AS-P server, consider the difference in RS-485 bias voltage between the two servers to avoid decreased performance and reliability of the RS-485 network. For more information, see RS-485 Communications .

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

Note:

You can reuse an Automation Server terminal base (TB-AS-W1) for an AS-P server module by removing the terminal block at the top of the terminal base.

Automation server names

Typically, automation servers and WorkStations can acquire different identifiers and user-assigned names. For example, automation server has a network identifier, AS-000E00, which is used internally but is difficult to remember. For convenience, you can also assign a descriptive automation server name, such as Main Lobby-AS, to locate this automation server in Building Operation. You may encounter these two names during configuration.

Network Device Protocols

If your network uses static IP addresses or DNS server names, you need to apply a valid IP address or fully qualified domain name to a replacement automation server. Specifically, you use the static IP address or fully qualified domain name to locate the new automation server on the network. To reconfigure the default TCP/IP settings on the new automation server to match those of the replaced automation servers, you use the Automation Server Web Configuration utility.

If your network uses DHCP, a new automation server can automatically acquire TCP/IP configuration information from a DHCP server. When acquired, you use the fully qualified domain name rather than the IP address to locate the new automation server on the network. By default, DHCP is turned off on automation servers. To enable this and other network settings on the new automation server, you use the Device Administrator. For more information, see Automation Server Device Administration .

Important:

Make sure that you have a valid automation server backup set before performing a restore. A backup set can contain either configuration data only, or both configuration and historical data.

Standalone automation server site

In a single automation server site, you log onto the automation server in WorkStation to manage Backup and Restore operations. In this scenario, you need to have a valid backup set to restore the automation server in case the hardware fails or data is lost.

The automation server only stores one backup set at a time. Therefore, you should create a backup set when the automation server is functioning properly and then store this backup set in different location. You save and store a backup set on your WorkStation PC or network drive. You then can import this backup set to the automation server.

Multi-server Site

In a multi-server site, you can log onto an Enterprise Server in WorkStation to manage backup and restore operations for all the automation servers in the group. Unlike the automation server, which only stores one backup set at a time, the Enterprise Server can store multiple backup sets for each automation server. From the AS Archives folder, you can select a stored backup set that was created when the automation server was functioning properly.

To store a backup set in another location, you save a selected backup set to a folder on your WorkStation PC or network drive. You then log onto the new automation server to import this backup set to the local directory. If you do not log off from the Enterprise Server, the system uses the most current backup set stored on the Enterprise Server hard drive instead of the newly imported file on the automation server. Therefore, be sure to log onto the automation server before restoring the automation server in WorkStation. For more information, see Saving an Automation Server Backup Set to Another Location .