Backing Up, Restoring, and Cloning the SmartServer (Release 3.3 and Prior)
For SmartServer 3.4 and higher, see Backing Up, Restoring, and Cloning the SmartServer.
The SmartServer ships with an SD Card inserted into the appropriate slot on the device. The CMS database is located on the SD Card. This SD Card must remain inserted in the SmartServer whenever power is applied to the SmartServer.
The CMS Storage widget provides the ability to view system information including internal flash memory, CPU utilization, and log sizes, as well as to perform system and database backup, restore, and cloning operations. It also provides the ability to change logging settings (data and/or event logging, and storing on an SD Card).
The Storage widget can be used to erase the CMS database stored on your SD Card and all the contents on the SD Card from the Storage widget. See Managing the SmartServer SD Card for more information about these operations, as well as how to delete specific SmartServer system and database files and to reformat the SD Card.
The SmartServer system and database information that is backed up or stored can be also be used to configure another SmartServer. The following sections describe available methods to do so:
- Backing Up and Replacing a SmartServer – the backup/replace method can use a backup for the same SmartServer only, or a replacement SmartServer.
- Exporting and Importing a SmartServer Configuration – the export/import method saves the SmartServer configuration for deploying to multiple SmartServers. Typically, this method is used when building up your network.
Cloning and Deploying a SmartServer to Multiple Systems (Release 3.4) – the backup/cloning method backs up the SmartServer configuration and data. This method preserves the Host Name, Install Code, Serial Number, but changes the apollo password, MAC Addresses, and Segment ID (SID).
Warnings
You cannot clone a target SmartServer 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.
Saving the SmartServer apollo password
You should save the apollo password for any backed-up SmartServer system image. If you restore a system image onto a new SmartServer, then that SmartServer will have its password changed to the old SmartServer's password (from the image file).
If you use the CLONE tab to restore an image onto a new SmartServer, then the apollo password, MAC Addresses, and SID will be changed on the new SmartServer to what is stored on the image file. Host Name, Install Code, and Serial Number are not changed.
If you use the SYSTEM tab or DATABASE tab to restore an image onto a new SmartServer, then the apollo password, Serial Number, Host Name, MAC Addresses, Install Code, and SID will be changed on the new SmartServer to what is stored on the image file.
This section consists of the following:
Modifying Logging Settings
The Storage widget provides the ability to set logging operations to save data logging and/or save event logging, as well as to save logging on an SD Card.
To modify the logging settings, perform the following steps:
Open the Storage widget.
Note: To best view all of the information on this widget, click the /wiki/spaces/TEMP/pages/44631776 (
). 
- Click the Edit button (
). 
Note that the Edit button changes to a Save button (
).
- Select the appropriate checkbox (that is, Save data logging, Save event logging, and/or Store on the SD Card).
- Click the Save button () for logging changes to take effect.
The new logging settings are stored in the Storage widget.
Backing Up the System or Database
You can back up the contents of the flash memory in your SmartServer so that you can recover from a hardware failure of your SmartServer. You can back up the entire memory image that includes all the SmartServer system files as well as the database that stores your system configuration. This is called a system backup. You can also back up the SmartServer database without the system files. This is called a database backup. To backup the system or database, follow these steps:
Open the Storage widget.
Note: To best view all of the information on this widget, click the /wiki/spaces/TEMP/pages/44631776 ( ). 
- Click BACKUP.
A confirmation dialog box appears.
- Select BACKUP SYSTEM or BACKUP DATABASE for the backup operation.
A message similar to the following appears:
System backup
Database backup - Click OK to proceed with the desired backup operation.
Restoring the System or Database
You can restore a system or database backup to a new SmartServer to recover from a hardware failure of a SmartServer. You can also restore a system or database backup to restore a previously saved configuration. To support restoring a backup, you must first create a backup as described in the previous section. To restore a system or database image, follow these steps:
To restore a backup to a new SmartServer, remove power from the new SmartServer.
Remove the SD Card from the SmartServer.
Insert your SD Card with the backup image to be restored into the SmartServer.
Open the Storage widget.
Note: To best view all of the information on this widget, click the /wiki/spaces/TEMP/pages/44631776 ( ). Click RESTORE.
The Restore dialog box appears displaying the name of the system image to be restored.
Use the SYSTEM and DATABASE tabs to select the type of restore operation you want to perform.
System restore
Database restore
If more than one file is available, a dropdown list will appear allowing you to select the desired file as shown in the example below.
Dropdown list for a system restore with multiple backup files
Dropdown list for a database restore with multiple backup files- If multiple backup files are available, then select the file you want to use from the dropdown list for the restore operation.
Multiple system files example
Multiple database files example Click RESTORE to proceed with the restore operation.
This feature overwrites the new SmartServer's Serial Number, Host Name, MAC Addresses, Install Code, SID, and apollo password.
A message similar to the following appears:
System restore
Database restore- Click OK to proceed with the desired restore operation.
Cloning the System
cloning is available with SmartServer IOT 2.7 Update 1 and higher.
To clone a SmartServer system, perform the following steps:
Open the Storage widget.
Note: To best view all of the information on this widget, click the /wiki/spaces/TEMP/pages/44631776 ( ). Click RESTORE.
The Restore dialog box appears.
Select the CLONE tab on the Restore dialog box.
The Restore dialog box appears displaying the name of the system backup file to be used for the target SmartServer.
If more than one file is available, a dropdown list will appear allowing you to select the desired file as shown in the example below.
- If multiple backup files are available, then select the file you want to use from the dropdown list for the clone operation.
Click RESTORE.
Warnings
This feature preserves the new SmartServer's Serial Number, Host Name, and Install Code, but changes the apollo password, MAC Addresses, and SID. 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.
A confirmation dialog box appears.
Click OK in the Confirmation dialog box to start the cloning process.
Messages similar to the following will appear on the console: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...
To ensure full functionality after the reboot process completes, perform the following steps:
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.- Verify target SmartServer IoT operations.