Make backup copies of the AMD configuration regularly. Note that a configuration can only be restored for the same AMD version.

Complete Backup

Backing up the current AMD configuration requires:

  • An operating, fully configured AMD device.

  • Installed RUM Console and a user with privileges to perform administrative tasks on the listed devices.
  • An external medium or access to another computer that is independent of the AMD device.

Important:

Note that the following procedures will not back up your private SSL keys used for OpenSSL decryption.

  • To backup the OpenSSL keys, back up the /usr/adlex/config/keys folder on the AMD.
  • To backup the other SSL keys, refer to the SSL card manufacturer's official procedures.

Manual monitoring configuration backup

  1. Log on to the AMD as user root.

  2. Issue the ndstop command on the Linux command line to stop all AMD traffic monitoring services.

  3. Save the existing AMD configuration.

    Save the contents of the configuration directory /usr/adlex/config.

    Use an appropriate method to save this directory to an external medium or another computer.

    In this example, the tar command is used to archive the configuration directory and the scp command is used to copy the archive to a remote backup machine.

    [root@amdprobe /]# tar -czf  amd_config.tar.gz  /usr/adlex/config/

    Next, copy the archive to the remote backup machine:

    scp amd_config.tar.gz username@backup_machine_IP_address:backup_directory

    where username is the login name of the user account to use on the remote backup machine, backup_machine_IP_address is the backup machine's IP address, and backup_directory is the directory to which the backup file will be copied.

    Important:

    There are several other ways to back up directories. Regardless of the method you choose, be sure to preserve the user rights for the directory and files that are backed up. This is required because the files located in the config directory have different owners.
  4. Issue the ndstart command on the Linux command line to restart the AMD software.

AMD settings and configuration export

This procedure is designed to export vital AMD settings and monitoring configuration for diagnostic purposes. While it can be used to regularly back up settings and configuration, there is no simple way to restore the information from this type of backup, so it should be used for preserving the AMD configuration snapshot.

  1. Access the RUM Console.
  2. Navigate to Devices and Connections ► Manage Devices.  
  3. Click on the AMD you want to back up and select the Export diagnostic information option from the context menu.

  4. Optionally, you can include a fragment of monitored data. Using the begin and end settings, you can specify the time range covered by the included fragment. This option is specifically useful when diagnosing problems related to monitoring data.
  5. Click Download to download a timestamped compressed file containing:
    • AMD boot logs
    • Core dumps
    • Information about the operating system
    • Information about the hardware (memory, CPU, average load, devices, network interfaces)
    • Monitoring configuration (any settings related to software services, licenses and monitoring)

Complete Restore

You should have available the following:

  • Access to media with the backup or a backup computer used to store the saved configuration.

  • Administrator privileges for the AMD device.

  • Knowledge of how the backup was performed, such as which path was saved.

The following example assumes that the configuration directory was archived without including the full path using the tar command.

To restore your backup configuration:

  1. Log on to the AMD as user root.

  2. Issue the ndstop command on the Linux command line to stop the AMD traffic monitoring software.

  3. Restore the AMD configuration from the archive.
    Choose the appropriate restoration method, depending on whether you saved the back up to a disc (CD or DVD) or on a remote backup machine.

    Important:

    Icon

    Regardless of the method used to back up the AMD configuration, be sure to preserve the user rights for the directory and files that you restore. This is required because the files located in the config directory have different owners.

     

    • If the back up file is on a disc:

      1. Mount the media drive where the back up is stored.

        [root@amdprobe /]# mount /dev/cdrom /mnt

        If there is no system output, use the mount command to ensure you have access to the backup media. See whether the output includes the path to the media. For example:

        [root@amdprobe /]# mount
        
        /dev/hdc on /mnt type iso9660 (ro)
      2. If the backup command included the full path to the config directory, ensure that the working path is a root directory of the AMD device and execute the following command to unpack the archive:

        [root@amdprobe /]# cd /usr/adlex/config/
        [root@amdprobe /]# tar -xzvf /mnt/amd_config.tar.gz
    • If the backup file has been created following the Complete Backup procedure and is located on a remote backup computer:

      1. Copy the configuration saved on the backup machine to the system root on the AMD machine.
        scp username@backup_machine_IP_address:backup_directory amd_config.tar.gz

      2. Unpack the archive.

        [root@amdprobe /]# tar -xzvf amd_config.tar.gz
  4. Issue the ndstart command on the Linux command line to restart the AMD traffic monitoring software.

 

  • No labels

2 Comments

  1. Please remove the '-' from the following commands. tar does not require '-' ibefore of the flags:

    tar -czf  amd_config.tar.gz  /usr/adlex/config/

    tar -xzvf amd_config.tar.gz


    '-' before of the flags produces error when it is ran in cmd.


    1. Hello Krassimire,

      We have tested the commands included in the examples and the "tar" command accepts the flags with and without the "-" (dash). The error you see probably relates to another issue. Perhaps there is a problem with file/directory write permissions?