Product version

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

Concept

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

Functionalities: Basic Functionality

Product version: 1.8, 1.9

10/13/2016

SmartStruxure Server Device Replacement Using Restore

arrow1_rotation

SmartStruxure Server Device Replacement Using Restore Workflow

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

Supported Cases of SmartStruxure Server Device Replacements

The following cases of SmartStruxure server device replacements are supported using restore:

Replacing a SmartStruxure server device with a SmartStruxure server device of the same SmartStruxure server device type
Replacing Automation Server with AS-P

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

Notice
Loss of data If you replace an Automation Server with an AS-P, 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, 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 module by removing the terminal block at the top of the terminal base.

SmartStruxure Server Device Names

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

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

Important:

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

Standalone SmartStruxure Server Device Site

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

The SmartStruxure server device only stores one backup set at a time. Therefore, you should create a backup set when the SmartStruxure server device 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 SmartStruxure server device.

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