The candidate and running databases can be saved to or loaded from files in the host OS. This can be used to make backups, copy configurations to other routers, or similar purposes.
The filenames can take an absolute path and filename, or the path may be omitted to save the file in the directory from which the TNSR CLI was invoked by the administrator. When saving, this file must be writeable by the TNSR backend daemon. When loading, this file must be readable by the TNSR backend daemon.
The best practice is to store backup configuration files in a secure location to prevent unauthorized access to sensitive information.
Saving the running configuration as a backup:
tnsr# config tnsr(config)# configuration save running backup.xml
Loading a configuration file from a backup:
tnsr# config tnsr(config)# configuration candidate load backup.xml tnsr(config)# configuration candidate commit