Product version

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

Concept

Products: AS-B, Edge Server, Enterprise Central, Enterprise Server, AS-P, Virtual Project Servers

Functionalities: Basic Functionality

Product version: 2024, 7.0

12/3/2024

Field Server Replacement Using Restore

arrow1_rotation

Field Server Replacement Using Restore Workflow

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

Supported cases of field server replacements

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

Replacing a field server with a field server of the same field server type
Replacing Automation Server with an AS-P server

To replace Automation Server with an 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.

Field server names

Typically, field servers and WorkStations can acquire different identifiers and user-assigned names. For example, a field server has a network identifier, AS-000E00, which is used internally but is difficult to remember. For convenience, you can also assign a descriptive field server name, such as Main Lobby-AS, to locate this field 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 field server. Specifically, you use the static IP address or fully qualified domain name to locate the new field server on the network. To reconfigure the default TCP/IP settings on the new field server to match those of the replaced field servers, you use the Automation Server Web Configuration utility.

If your network uses DHCP, a new field 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 field server on the network. By default, DHCP is turned off on field servers. To enable this and other network settings on the new field server, you use the Device Administrator. For more information, see EcoStruxure BMS Server Administration Overview .

Important:

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

Standalone field server site

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

The field server only stores one backup set at a time. Therefore, you should create a backup set when the field 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 field 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 field servers in the group. Unlike the field server, which only stores one backup set at a time, the Enterprise Server can store multiple backup sets for each field server. From the AS Archives folder, you can select a stored backup set that was created when the field 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 field 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 field server. Therefore, be sure to log onto the field server before restoring the field server in WorkStation. For more information, see Saving a Field Server Backup Set to Another Location .