You can define your backup destination before you proceed with the backup configuration. If you choose not to create a backup destination, then your configuration files can be stored in the default destination directory created during system installation (/var/log/backups/). The SP2000 allows you to back up the system configuration files to use the following destination types (storage locations).
The following sections describe the configurable options when setting up a backup destination in the DSC-SP2000 Web UI using Backups > Backup Destination.
Local Directory
You can use the default backup directory /var/log/backups/, created during system installation, or designate a specific directory under /var/log/backups/ on your local system for the backup files.
The following table lists and describes the attributes on the Backup Destination Definitions Details screen if you selected the Local Directory option.
Backup Destination Definition Screen Attributes Listing and Description (Local Directory)
| Attribute | Description |
|---|---|
| Destination Type | Indicates the destination type. Select the Local Directory option. |
| Backup Destination Description | Type a name (Identifier) for your backup destination. You are limited to entering 255 characters. |
| Directory | Type the path and the directory where you want the backup files to reside (under /var/log/backups/). |
SFTP to a Remote Directory
Use Secure File Transfer Protocol (SFTP) to transfer backup files to a remote backup destination.
Before you specify an SFTP remote directory as your backup destination, ensure the remote backup destination is running an SFTP server and is ready to receive the SP2000 backup files.
The following table lists and describes the attributes on the Create Backup Destination Details screen if you selected the SFTP Remote Directory option.
Note
Before transferring backup files to a remote directory using SFTP, make sure that the SFTP server, which is external to the given SP2000 Platform, is configured with access that does not require a password.
Create Backup Destination Definition Screen Attribute Listing and Description
| Attribute | Description |
|---|---|
| Destination Type | Indicates the destination type. Select the SFTP Remote Directory option. |
| Backup Destination Description | The name or identifier of the remote SFTP backup destination server. You are limited to an entry of 255 characters. |
| SFTP Server | The remote server hostname or IP address to which you want to SFTP the backup files. |
| User Name | Your user name on the remote SFTP server. |
| Remote Directory (optional) | The remote directory path must be the absolute path. For example, /tmp/backups. |
| Maximum Number of Retries | Define the number of attempts to connect to a remote destination server or after a connection is lost (default is 10). |
| Retry Interval in Minutes | Define the time period between failed attempts to connect to the remote backup destination server (minimum of 10 minutes). |
Set up the SSH Keys
Follow this procedure to set up the SSH keys between the Signaling Platform 2000 CPUs and the off-board backup server.
Start
- SSH into the first SP2000 Management CPU as a root user.
Run the following command to push the SSH keys to the remote backup servers, where <remote_userid> and <remote server IP address> are replaced with your system's remote SFTP server username and remote server hostname or IP address (where you would like to SFTP the backup files), respectively.
ssh-copy-id -i /root/.ssh/id_rsa <remote_userid>@<remote server IP address>
Example[root@SP2K00slot ~]# ssh-copy-id -i /root/.ssh/id_rsa bkpuser@10.11.12.13 /bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub" /bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed /bin/ssh-copy-id: INFO: 1 key(s) remain to be installed – if you are prompted now it is to install the new keys gpsback@10.11.12.13's password: Number of key(s) added: 1
Try to log into the machine with the following command to make sure that only the key(s) you wanted were added. It should result in no key being found.
ssh 'bkpuser@10.11.12.13
Ensure that the key exchange worked by logging into the SFTP server and verify the backup directory access. If you are prompted for a password, the exchange did not work, and troubleshooting is required.
Example[root@SP2K00slot ~]# ssh bkpuser@10.11.12.13 [bkpuser@BKPSERVER ~]$ cd /share/backups/sp2k [bkpuser@BKPSERVER sp2k]$ exit logout Connection to 10.11.12.13 closed. [root@SP2K00slot ~]#
Tip
This process should only be required once; however, if the destination node loses the authorization keys, or if the key on the CPU changes, the keys would have to be copied again.
After you executed this procedure, the SFTP Remote Directory may be selected as a backup destination without performing the steps in this procedure.
Overview
Content Tools