How to fully backup and restore a node config

Fully backup and restore a node

This page describes how to backup and restore an Augmenta Node. This can be useful in case of hardware failure.

The data and configurations that need to be backed up can be separated in different categories.

Augmenta-Daemon config

The most important file to back up is the running configuration. This one can be downloaded from the WebUI of the node. You have to download the current settings file.

If you have to backup only ONE file, back up the current config file, it is the most important one. {.is-warning}

Another file that can be backed up it the preference.xml file.

You can also write down the output size to ensure that when restored, the node will still be calibrated in Fusion. If when restored the size does not match, you will have to re-calibrate for sure.

If you want to put the restored node in place of another (if one node has to be replaced) you can also copy the /var/snap/augmenta/common/data/uuid file, it is the unique identifier of the old node, which is used by Fusion to recognize the nodes from each others. This should allow the node to take the place of the old one when connecting to Fusion. Otherwise you would have to manually put back the parameters in Fusion (explained below).

You could also copy in bulk the /var/snap/augmenta/common folder for each node, which contains all the augmenta-daemon configurations and data. Be carefull because it also contains the license file, which must not be transfered on another machine. {.is-info}

Snap version

The snap version must be known, because if another version is used it might not be able to read the config files, or work as intended. Another interesting way to back it up would be to manually download the .snap file used and put it with the backup.

Fusion configuration

When replacing a node, do not forget to copy the transform parameters in Fusion. If something goes wrong, it should allow you to put back the node's zone in place. You will have to back up the source's Position, Rotation, Scale and zone size. (Zone size is only usefull to check if it hasn't changed).

System

Some system settings might have been changed:

• network configuration : check that the network config wasn't changed (enter nmcli con show [≤con-name>] in a terminal to list all connections (without the con-name param) or view a specific one (with con-name))

• System image : check if the replacement node's system image is the same, or if they are compatible. Check the /home/augmenta/.augmenta_image_version file to know when it was built.

• snap plugs : a user might have connected manually a snap plug

Informations

You might have to change other software's configuration. You might have software that tries to wake the nodes at some point, so you will have to change the MAC address everywhere.

Write down the new root password.

Write down the new nodes's serial number (AR ... )