Backing Up Configuration Files to External File Servers

You can back up configuration files to an external file server using SFTP or SCP. Backing up configuration files externally ensures that you have a set of configuration files in case of local file failure. It is good practice to perform external configuration backups before upgrading, downgrading, installing service patches, or making changes to network hardware.

Do not use this procedure for event broker services in PubSub+ Cloud. Using this procedure in PubSub+ Cloud may result in a degradation of service. Instead, see Backing up Event Broker Services for more information.

When to Externally Backup

It is important that you backup configuration files to an external file server regularly (using either SFTP or SCP) to ensure that you have a set of backup files available in case your current local configuration database becomes corrupted or otherwise unusable.

Solace recommends that you perform at least one configuration backup to an external file server daily. Furthermore, external backups should be done in the following circumstances:

before upgrading or downgrading an event broker
before installing a service patch for installed event brokers
before making any major changes to the network hardware
before deploying a large number of new network devices

Do not attempt to start, stop, or reset the event broker at any point during the backup process.

Externally Backing Up Config Files Using CLI

To back up a configuration file to an external file server using SFTP or SCP from the event broker using a CLI user account, follow this procedure:

Ensure that you have a file server on the event broker network to which you have IP connectivity.

Enter the following User EXEC command:
```
solace> enable
solace#
```
Enter one of the following commands to copy the desired configuration file to the external file server (using either SFTP or SCP) from the event broker:
```
solace# copy current-config sftp://[<username>@]<ip-addr>/<remote-pathname>
```
Or
```
solace# copy current-config scp://[<username>@]<ip-addr>/<remote-pathname>
```
Where:
<username>is your SFTP or SCP username
<ip-addr> and <remote-pathname> point to the location (either an SFTP server or an SCP server) where the current configuration file is to be copied.

Externally Backing Up Config Files Using File Transfer

Backing up a configuration file to an external file server (using SFTP or SCP) from an event broker can also be done using a File Transfer user account created through the username Global CONFIG command.

Example:

[remote_machine]# sftp pascal@192.168.1.208:configs/backup ./appliance86-backup.1730.cfg

Connecting to 192.168.1.208...

Password: <password>

Fetching /configs/backup to ./appliance86-backup.1730.cfg
/configs/backup 100% 34MB 4.9MB/s 00:07

Provide feedback