Versions Compared

Old Version 3

changes.mady.by.user Nina Cardillo

Saved on

compared with

New Version Current

changes.mady.by.user Nina Cardillo

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
The CMS IMPORT/EXPORT button is available with SmartServer 3.5 and higher. For SmartServer releases PRIOR to 3.5, and with 2.7 update 1 and Higher, the CMS import/export feature is available with the CMS Settings button. 

...

Warning
title Backup and restore operations are dependent on SmartServer hardware versions

Restore operations are dependent on the SmartServer software and hardware versions for the backup and restore SmartServers. Consequently, you cannot restore a system image on all new SmartServers.

Example: If you backup a SmartServer 3.26 on a dual core SmartServer, then you cannot restore it on a new quad core that uses a Dialog PMIC, which is only supported with SmartServer 3.3 and higher. Doing so could result in the new SmartServer becoming unusable and possibly recoverableunrecoverable.

Therefore, you should backup only the settings and database (not the system) on the old SmartServer, and then on the new Dialog PMIC hardware, install SmartServer 3.3 or higher, and then restore the settings and database.

...

Cloning can be used to replicate a reference (source) SmartServer IoT to another SmartServer IoT(s), where each cloned (target) SmartServer's configuration will be identical to the reference SmartServer. Cloned SmartServers will have the same CMS configuration, external devices, external data points, custom applications, and custom web pages as the source SmartServer IoT. A clone restore preserves the new SmartServer's serial number, host name, MAC addresses, and install code, but changes the apollo password and segment ID (SID). In most cases, when you restore a database backup onto a new SmartServer, you will do so by cloning.

A full restore overwrites the new SmartServer's serial number, host name, MAC addresses, install code, SID, and apollo password. With this process, the new SmartServer will have identical image as the backed-up image. For a full restore, see Backing Up and Replacing a SmartServer for more information.

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.

...

  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 using the ifconfig command from a console connection. When using the ifconfig command from the console, either log in as root or enter sudo ifconfig. See Step 2 - Connect to Your SmartServer IoT. 

    A result similar to the following appears:

    Code Block
    apollo@smartserver-17q41xs17qes5s:~$ sudo ifconfig
eth0      Link encapeth0:Ethernet  HWaddr 00:d0:71:07:46:eb
          inet addr: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.16892.5  Bcast:192.168.168.255  Mask:3  netmask 255.255.255.0
           broadcast 192.168.92.255
        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-17q41xsfe0d:29b4  prefixlen 64  scopeid 0x20<link>
        ether 00:d0:71:0d:29:b4  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 15  bytes 1501 (1.5 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.1.19  netmask 255.255.255.0  broadcast 10.0.1.255
        inet6 fe80::2d0:71ff:fe0d:29b5  prefixlen 64  scopeid 0x20<link>
        ether 00:d0:71:0d:29:b5  txqueuelen 1000  (Ethernet)
        RX packets 173745  bytes 32293766 (32.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 22152  bytes 7542313 (7.5 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
ip70: flags=4291<UP,BROADCAST,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 172.24.25.128  netmask 255.255.255.0  broadcast 172.24.25.255
        inet6 fe80::2d0:71ff:fe0d:29b6  prefixlen 64  scopeid 0x20<link>
        ether 00:d0:71:0d:29:b6  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 86  bytes 5920 (5.9 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 4889645  bytes 335225008 (335.2 MB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4889645  bytes 335225008 (335.2 MB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
lon0: flags=67<UP,BROADCAST,RUNNING>  mtu 1280
        inet 44.137.199.120  netmask 255.255.0.0  broadcast 44.137.255.255
        inet6 fe80::2d0:71ff:fe14:bf43  prefixlen 64  scopeid 0x20<link>
        ether 00:d0:71:14:bf:43  txqueuelen 1000  (Ethernet)
        RX packets 4253  bytes 200042 (200.0 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4258  bytes 132269 (132.2 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
vlon0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1280
        inet 44.137.199.121  netmask 255.255.0.0  broadcast 44.137.255.255
        inet6 fe80::2d0:71ff:fef4:bf43  prefixlen 64  scopeid 0x20<link>
        ether 00:d0:71:f4:bf:43  txqueuelen 1000  (Ethernet)
        RX packets 4258  bytes 132269 (132.2 KB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4253  bytes 200042 (200.0 KB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
 
apollo@smartserver-17qes5s:~$


  6. Connect to the source SmartServer IoT's CMS from a browser at:

    1. With SmartServer release 2.8 or higher:

       


      Code Block
      https://<IPV4 address>/cms


    2. With SmartServer release prior to 2.8: 

      Code Block
      https://<IPV4 address>:8443/cms


      The CMS login window appears.

      Image Modified

  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. Perform a full system backup. See Backing Up, Restoring, and Cloning the SmartServer.

...

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

  1. 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).

  2. 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).

  3. 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.

  4. Remove any USB devices from the target SmartServer.

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

  6. Find the SmartServer's IPV4 address by entering the following command at the console: ifconfigusing the ifconfig command from a console connection. When using the ifconfig command from the console, either log in as root or enter sudo ifconfig. See Step 2 - Connect to Your SmartServer IoT. 

  7. Connect to the source SmartServer IoT's CMS from a browser at:

    1. With SmartServer release 2.8 or higher: 

      Code Block
      https://<IPV4 address>/cms


    2. With SmartServer release prior to 2.8: 

      Code Block
      https://<IPV4 address>:8443/cms


      The CMS login window appears.

      Image Modified

  8. 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.

  9. Open the SmartServer IoT CMS.



  10. Click the Import/Export button () located on the SmartServer app bar.



    The Import/Export dialog appears.


    Single SmartServer


    Multiple SmartServers

  11. Verify or select the SmartServers (if multiple) to be used for the restore.

  12. Select the Import Source (i.e, Upload to upload a backup file from your PC or Local Storage to retrieve a backup file from a directory on the SmartServer).



  13. If you selected Local Storage as the Import Source, set or verify Backup Location.



  14. If you selected Local Storage as the Import Source, select the full system backup file to be imported from the pulldown list.



    Or, if you selected Upload as the Import Source, select the full system backup file from your PC and place it into the Drop files to import area, or use the browse feature to navigate to the backup file on your PC.



  15. Disable the Restore Original Segment ID option (enabled by default).



  16. Click IMPORT.

    An indicator will appear showing that the restore is in progress. You will not be able to access the CMS during the system restore operation.

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

    1. Power-cycle the target SmartServer IoT to ensure full functionality. 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.

...