Versions Compared

Old Version 8

changes.mady.by.user Nina Cardillo (Unlicensed)

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.

...

Info

For SmartServer 3.4 and higher, see Cloning and Deploying a SmartServer to Multiple Systems (Release 3.4). 

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.

Warning
titleWarnings

Using the Storage widget → RESTORE button → CLONE tab preserves the new SmartServer's Serial Number, Host Name, and Install Code, but changes the apollo password to the old SmartServer's password, as well as the MAC Address and Segment ID (SID) and MAC Addresses. In most cases, when you restore a database backup onto a new SmartServer, you will use theCLONE tab. 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. 

Using the Storage widget → RESTORE button → SYSTEM tab or DATABASE tab overwrites the new SmartServer's Serial Number, Host Name, MAC AddressAddresses, Install Code, SID, and apollo password.

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.

...

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

...

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

  • 591273
  • 591273
  • 591273Creating 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

...

  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 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 Storage widget.

    Note

    Note 1: If the Storage widget does not appear on the CMS, you will need to add it to the dashboard /wiki/spaces/TEMP/pages/44631776.

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



  9. Click BACKUP. 



  10. Click BACKUP SYSTEM in the Confirmation dialog box.


  11. Click OK in the Confirmation dialog box to start the backup process. 

...

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

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 section 591273steps in the section Restoring the Source SmartServer Backup File to the Target SmartServer below.

Using Ubuntu

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

...

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

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:

Notewarning

Note: Do not clone a target SmartServer with the same backup file more than once, and do not put two SmartServer clones on the same network.

  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 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 Storage widget.

    Note

    Note 1: If the Storage widget does not appear on the CMS, you will need to add it to the dashboard /wiki/spaces/TEMP/pages/44631776.

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



  9. Click RESTORE. 



  10. Select the CLONE tab on the Restore dialog box and select the backup file that was copied to the SD Card from the drop-down menu as shown in the example below.C

     Cloning 
    Warning
    title
    Warnings

    Cloning preserves the new SmartServer's Serial Number, Host Name, and Install Code, but changes the apollo password to the old SmartServer's password, as well as the SID and MAC Address and SIDAddresses. 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. 




  11. Click RESTORE.



  12. Click OK in the Confirmation dialog box to start the restore process. 

    Messages similar to the following will appear on the console:

    Code Block
    Broadcast message from rebootmanager daemon (Tue 2020-03-10 15:15:02 BST)
System going down to perform restore...
going down for reboot NOW

====================================================================
============  Adesto Apollo 2 Backup/Restore Utility  ==============
====================================================================
Version 1.2

 * Initializing... OK

SDCard: /dev/mmcblk2p1

 * Checking required files...
file 'restore' is present.
file 'preserve' is present.
file backups/SmartServer-System-Backup-2020-03-10-114532.tgz is present.

Required files are present.

 * Checking files integrity...
e77de975a4eabefc339dae6f132d8803 - OK
Files validated.

 * Mounting partitions... OK

Filesystem           1K-blocks      Used Available Use% Mounted on
none                    868600         0    868600   0% /dev
/dev/mmcblk2p1        30634944   1935896  27119836   7% /mnt/mmc_restore
/dev/mmcblk3p2         3232312   2164084    884320  71% /mnt/mmc_main
/dev/mmcblk3p1           16128      8707      7422  54% /mnt/mmc_main/boot
/dev/mmcblk3p5          884676      7268    815252   1% /mnt/mmc_main/var/apollo

 * Preserving Identity...OK

 * Unmounting partitions... OK

 * Formatting partitions...

 * Mounting partitions... OK

Filesystem           1K-blocks      Used Available Use% Mounted on
none                    868600         0    868600   0% /dev
/dev/mmcblk2p1        30634944   1935932  27119800   7% /mnt/mmc_restore
/dev/mmcblk3p2         3232312      5756   3042648   0% /mnt/mmc_main
/dev/mmcblk3p1           16128         1     16128   0% /mnt/mmc_main/boot
/dev/mmcblk3p5          884676       904    821616   0% /mnt/mmc_main/var/apollo

Always mount sdcard for restore.

 * Restoring System... OK

 * Restoring original identity...OK

 * Syncing... OK

 * Unmounting partitions... OK

Procedure Complete.

Rebooting in 5 seconds...


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

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

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


    2. Verify target SmartServer operations.

...