Versions Compared

Old Version 3

changes.mady.by.user Nina Cardillo

Saved on

compared with

New Version 4

changes.mady.by.user Nina Cardillo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

Cloning is available with SmartServer 2.7 Update 1 and higher.
Info

For SmartServer 3.5 and higher, see Backing Up and Cloning a SmartServer to a Multiple Sites. 

For SmartServer 3.3 and prior, see Cloning and Deploying a SmartServer to a Multiple Systems Sites (Release 3.3 and Prior). 

...

Warning

For a clone restore, use the Devices widget, SEGMENT CONTROLLER tab → RESTORE action → Full System Restore Original Segment ID option set to No, which preserves the new SmartServer's Serial Number, Host Name, MAC Addressesaddresses, and Install Code, but changes the apollo password to the old SmartServer's password and the Segment ID (SID), which is defined from the source.  In In most cases, when you restore a database backup onto a new SmartServer, you will use this cloning feature. A You cannot clone a target SmartServer should not be cloned with the same backup file more than once; however, if you re-image the SmartServer, then you can perform another clone. In addition, you cannot put two SmartServer clones on the same network. 

For a full restore (or full replacement), use the Devices widget, SEGMENT CONTROLLER tab → RESTORE action → Full System Restore Original Segment ID option set to Yes, which overwrites the new SmartServer's Serial Number, Host Name, MAC Addresses, Install Code, SID, and apollo password. With this process, the new SmartServer has an identical image as the backed-up image.

...

Warning
titleSave the SmartServer Password from the Original SmartServer

You should save the apollo password for any backed-up SmartServer system image. If you restore a system image onto a new SmartServer, then the new SmartServer will have its password changed to the old SmartServer's password (from the backup image file).

The reference SmartServer can include the most comprehensive configuration of devices likely to be seen in the field. For subsets of the reference configuration, devices that are not present in some sites can either be ignored or deleted accordingly. Cloned Modbus and BACnet networks should be configured with the same addressing and baud rate information as the reference SmartServer IoT networks. LON networks will need their devices replacing in the CMS with the new UIDs.

...

With the exception of the Serial Number, Host Name, MAC Addresses, and Install Code which remain unique, the cloned SmartServer will be identical to the reference SmartServer (including the password).

...

Table of Contents
maxLevel3

Prerequisites

Backing up the SmartServer IoT

SmartServer IoT backups are stored on the SD Card in the /media/sdcard/backups directory (there can be multiple backup files on the SD Card).

...

Alternatively, you can install a dual-boot Ubuntu/Windows or an Ubuntu-only configuration.

Storing User Applications and Data

User applications and data should be located in the directory indicated in the APOLLO_DATA environment variable (typically /var/apollo/data). Doing so ensures that user applications and data are not affected by updates and are included in the SmartServer IoT's backup mechanism.

Connecting to the Console

To receive status updates during SmartServer IoT backup and restore operations, you need to be connected to the SmartServer IoT's  serial console port (USB micro B, 115200, 8,1,N) using a terminal emulator, such as PuTTY for Windows or microterm for Ubuntu.

PuTTY downloads are available at https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html. 

Microterm downloads are available at https://sourceforge.net/projects/microterm/.

Cloning the SmartServer IoT

The sections that follow describe the necessary steps to clone a SmartServer IoT, including:

  • Creating a Source SmartServer Backup
  • Copying the Source SmartServer Backup File to the Target SmartServer
  • Restoring the Source SmartServer Backup File to the Target SmartServer

Creating a Source SmartServer Backup

To create a source SmartServer backup, perform the following steps:

  1. Connect an Ethernet patch lead from the source SmartServer IoT's  RJ45 LAN connector to an Ethernet switch port on your local LAN with a DHCP server running (unless you are using a static IP address).

  2. Connect your PC to the same LAN and subnet as the source SmartServer IoT using an Ethernet lead. Alternatively, use the SmartServer's Rapid Fallback feature (if enabled) to set the SmartServer IoT's address to 192.168.1.222, which will allow a direct Ethernet connection from the PC to the SmartServer IoT. In this case you will have to manually configure the PC to be on the same subnet as the source SmartServer IoT.

  3. Remove any USB devices from the source SmartServer. 

  4. Connect the terminal emulator to the console port using a USB cable and power up the SmartServer.

  5. Find the SmartServer IoT's IPV4 address for the eth0 port (shown as inet addr:192.168.168.5 in the example below, third line) by entering the following command at the console: ifconfig

    A result similar to the following appears:

    Code Block
    apollo@smartserver-17q41xs:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:d0:71:07:46:eb
          inet addr:192.168.168.5  Bcast:192.168.168.255  Mask:255.255.255.0
          inet6 addr: fe80::2d0:71ff:fe07:46eb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:38427 errors:0 dropped:17168 overruns:0 frame:0
          TX packets:35507 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2909558 (2.9 MB)  TX bytes:6099630 (6.0 MB)
          Interrupt:51 Base address:0x6000

eth1      Link encap:Ethernet  HWaddr 00:d0:71:07:46:ec
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:50 Base address:0xe000

ip70      Link encap:Ethernet  HWaddr 00:d0:71:07:6f:50
          inet addr:192.168.239.128  Bcast:192.168.239.255  Mask:255.255.255.0
          inet6 addr: fe80::2d0:71ff:fe07:6f50/64 Scope:Link
          UP BROADCAST RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6538 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:380111 (380.1 KB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MULTICAST  MTU:65536  Metric:1
          RX packets:1230995 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1230995 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:170737328 (170.7 MB)  TX bytes:170737328 (170.7 MB)

apollo@smartserver-17q41xs:~$


  6. Connect to the source SmartServer IoT's CMS from a browser at:
    1. With SmartServer release 2.8 or higher: https://<IPV4 address>/cms
    2. With SmartServer release prior to 2.8: https://<IPV4 address>:8443/cms

      The CMS login window appears.



  7. Login using the username and password. Note that the username is always apollo, but the password may have been changed from the one that is printed on the rear label of the SmartServer.

  8. Open the Devices widget, SEGMENT CONTROLLERS tab and perform a full system backup as described in Backing Up the Database and/or Settings, or System section of the Backing Up, Restoring, and Cloning the SmartServer.

Continue with the SmartServer cloning process by following the steps in the Copying the Source SmartServer Backup File to the Target SmartServer section below.

Copying the Source SmartServer Backup File to the Target SmartServer

Follow the appropriate procedure to copy the source SmartServer backup file to the target SmartServer for your environment below:

  • Using Windows
  • Using Ubuntu

Using Windows

You can use an SFTP application such as WinSCP to read the backup file from the source SmartServer IoT's SD Card, then store it on the Windows PC, and finally write the backup file to the target SmartServer IoT's SD Card. 

...

Continue with the SmartServer cloning process by following the steps in the Restoring the Source SmartServer Backup File to the Target SmartServer section below.

Using Ubuntu

To copy a source SmartServer backup file to the target SmartServer, perform the following steps:

...

Continue with the SmartServer cloning process by following the steps in the Restoring the Source SmartServer Backup File to the Target SmartServer section below.

Restoring the Source SmartServer Backup File to the Target SmartServer

To restore a source SmartServer backup file to the target SmartServer, perform the following steps:

Warning

For a clone restore, use the Devices widget, SEGMENT CONTROLLER tab → RESTORE action → Full System Restore Original Segment ID option set to No, which preserves the new SmartServer's Serial Number, Host Name, MAC Addressesaddresses, and Install Code, but changes the apollo password to the old SmartServer's password and the Segment ID ( SID), which is defined from the source.  In In most cases, when you restore a database backup onto a new SmartServer, you will use this cloning feature. A target SmartServer should not be cloned with the same backup file more than once. You cannot put two SmartServer clones on the same network.

For a full restore (or full replacement), use the Devices widget, SEGMENT CONTROLLER tab → RESTORE action → Full System Restore Original Segment ID option set to Yes, which overwrites the new SmartServer's Serial Number, Host Name, MAC Addresses, Install Code, SID, and apollo password. With this process, the new SmartServer has an identical image as the backed-up image.

...

Warning
titleSave the SmartServer Password from the Original SmartServer

You should save the apollo password for any backed-up SmartServer system image. If you restore a system image onto a new SmartServer, then the new SmartServer will have its password changed to the old SmartServer's password (from the backup image file).

  1. Connect an Ethernet patch lead from the target SmartServer's RJ45 LAN connector to an Ethernet switch port on your local LAN with a DHCP server running (this assumes a new SmartServer).

  2. Connect your PC to the same subnet as the target SmartServer using an Ethernet lead. Alternatively, use the SmartServer's Rapid Fallback feature to set the SmartServer's address to 192.168.1.222, which will allow a direct Ethernet connection from the PC to the SmartServer.

  3. Remove any USB devices from the target SmartServer.

  4. Connect the terminal emulator to the console port using a USB cable and power-up the SmartServer.

  5. Find the SmartServer's IPV4 address by entering the following command at the console: ifconfig

  6. Connect to the source SmartServer IoT's CMS from a browser at:
    1. With SmartServer release 2.8 or higher: https://<IPV4 address>/cms
    2. With SmartServer release prior to 2.8: https://<IPV4 address>:8443/cms

      The CMS login window appears.



  7. Login using the username and password. Note that the username is always apollo, but the password may have been changed from the one that is printed on the rear label of the SmartServer.

  8. Open the Devices widget, SEGMENT CONTROLLER tab.


    Note
    Note: To best view all of the information on this widget, click the Expand button (  ). 



  9. Click the Action button () and select the Restore action.



    The restore view appears.



  10. Select Full System for the Backup Contents.

    The Restore Original Segment ID option is already set to No (cloning).



  11. Select the system backup file to be used for the clone operation from the Restore File dropdown list.



  12. Click RESTORE to proceed with the clone operation.

    A message similar to the following appears:




  13. Click OK to proceed with the clone operation.

    You will not be able to access the CMS during the system clone operation.

  14. To ensure full functionality after the reboot process completes, perform the following steps:

    1. Power-cycle the target SmartServer IoT to ensure full functionality.

      Note
      The target SmartServer IoT may not be accessible over the current IP infrastructure due to IP address changes, and that its password may have changed to that of the source SmartServer IoT.


    2. Verify target SmartServer IoT operations.

...