Vyatta NOS documentation

Learn how to install, configure, and operate Vyatta Network Operating System (Vyatta NOS), which helps to drive our virtual networking and physical platforms portfolio.

system config-management commit-archive location <location>

Enables automatic archiving of configuration revisions to a specified location every time a change is committed.

set system config-management commit-archive location location
delete system config-management commit-archive location location
show system config-management commit-archive location

When this option is not set, system configuration is archived locally, but is not archived remotely, on commit.

location
Multinode. A location for the configuration archive. Archives are transferred by any of the following file-transfer methods and their general formats:

scp:// user: passwd @ host / dir

ftp:// user: passwd @ host / dir

tftp:// host / dir

where user is the user name on the host, passwd is the password associated with the user name, host is the host name or IP address of the remote server, and dir is the directory path in which to save the file. The saved file contains the original file name ( config.boot ) followed by the host name of the local system, date (YYYYMMDD), and time (HHMMSS). For example, config.boot-R1.20110126_193402 is the config.boot file from R1 saved on Jan 26, 2011 at 7:34:02pm.

You can define more than one archive location by creating multiple location configuration nodes.

Configuration mode

system {
   config-management {
      commit-archive {
         location location
      }
   }
}

Use this command to enable automatic remote archiving of configuration on commit.

The system automatically archives configuration on commit. These archives are stored locally in the /config/archive directory and the number of revisions to keep is set by using system config-management commit-revisions <revisions>.

The system config-management commit-archive location <location> allows you to archive an unlimited number of configuration revisions to a remote location by using FTP, SCP, or TFTP as the file transfer method. The archive operation occurs in the foreground.

However, for this command to succeed with SCP, the router must have the public key of the SCP host. To provide the public key to the router, log in to the SCP host using SSH (SCP uses SSH as its underlying protocol to copy the file) and say 'yes' to the public key that is presented by the SCP host.

Use the set form of this command to enable remote archiving of configuration revisions and specify the location of the archive.

Use the delete form of this command to disable remote archiving of configuration revisions.

Use the show form of this command to view remote archiving of configuration.