You can use the Restore function to re-use the configuration data from a backup set in a new standalone automation server. Rather than manually configuring your preferred automation server configuration, you can save time and configure the standalone automation server from a backup set.
The backup set used can originate from an automation server that is or has been part of a multi-server configuration.
To store a backup set in another location, you save a selected backup set to a folder on your WorkStation PC or network drive.
For more information, see Backup Sets .
The restore function to re-use configuration data from a backup set is supported for all protocols supported by EcoStruxure Building Operation software, except for BACnet and b3 BACnet.
The LonWorks devices connected to the automation server are not the same as the LonWorks devices that are to be connected to the duplicate. When you create a duplicate from an automation server, all Neuron IDs in the duplicate are deleted. This is also a way to avoid network conflicts.
After you created the duplicate, you add new Neuron IDs to the duplicate. You then commission all LonWorks devices on the new automation server.
For more information, see LonWorks Device Workflows .
When you duplicate a SpaceLogic device from a backup set all passwords are deleted on the duplicate for security reasons. The only exception is the default admin password. The administrator is forced to change the password at the first logon at the duplicate. All users must be given new passwords by the administrator.
To create a new automation server in a multi-server configuration, using a locally stored backup set, you need to make the backup set available for restore on the multi-server system. You add a new automation server to the Enterprise Server and select the backup set in the Create Object Wizard.
For more information, see Creating an Automation Server from a Backup Set .
You use a locally stored backup set to duplicate another automation server configuration in a standalone automation server. You then import the backup set to a client and restore to the new standalone automation server.
For more information, see Duplicating an Automation Server Using Restore .
Use the following workflow to duplicate an automation server from a backup set.
Backup an automation server that has the configuration you want to use in the new standalone automation server.
For more information, see Backing Up EcoStruxure BMS Servers Manually .
Copy the backup set to a local directory.
For more information, see Saving an Automation Server Backup Set to Another Location .
Log on to a new standalone automation server.
For more information, see Logging on to WorkStation as an EcoStruxure Building Operation User .
Import the backup set.
For more information, see Importing a Backup Set to Automation Server .
Use the Restore configuration with new IDs function to duplicate the configuration data from the imported backup set in the new standalone automation server. The communication settings from the backup set are not duplicated.
For more information, see Duplicating an Automation Server Using Restore .
When you restore a standalone automation server, you are logged off and need to log on manually after the restore is complete.