request deployment backup

none

Back up your current Routing Director network configuration and telemetry data. Backup files are available at export/paragon-shell/backup.

config

Back up only your current Routing Director network configuration information.

max-disk-write-rate-mbps rate

Specify a maximum disk I/O limit (in Mbps) only for the VictoriaMetrics DB when backing up Routing Director configuration. If this option is not used and no rate is specified, the default rate of 800 Mbps is applied for the VictoriaMetrics DB.

delete backup-id backupID

Delete the backed-up file with the specified backupID. You can delete only those files present on the node that you are logged on to. To view a list of available backup files, see show deployment backup.

download

backup-id backupID

storage-location path

user username

password password

Download a backed-up file from a remote location.

Download options include:

• backup-id backupID—ID of the backup file.

• storage-location path—Path where the backup file is stored remotely. Enter the location in the following format:

  scp://host:port/path or sftp://host:port/path

• user username—Username to log in to the remote location.

• (Optional) password password—Password to log in to the remote location. If you do not enter the password, you will be prompted to enter it.

telemetry (none | max-disk-write-rate-mbps rate)

Back up only your current Routing Director telemetry information.

Telemetry options include:

• none—Back up telemetry information from all supported databases.

• max-disk-write-rate-mbps rate—Back up telemetry information from all supported databases, but apply maximum disk I/O limit (in Mbps) for backing up telemetry information only from the VictoriaMetrics DB. If this option is not used and no rate is specified, the default rate of 800 Mbps is applied only for the VictoriaMetrics DB when backing up telemetry data.

upload

backup-id backupID

storage-location path

user username

password password

Upload the backup files to a remote location.

Upload options include:

• backup-id backupID—ID of the backup file.

• storage-location path—Path where the backup files must be stored remotely. Enter the location in the following format:

  scp://host:port/path or sftp://host:port/path

• user username—Username to log in to the remote location.

• password password—Password to log in to the remote location. If you do not enter the password, you will be prompted to enter it.

schedule

trigger-time schedule

node nodeIP

storage-location remote-path

user username

password password

type (full | config | telemetry)

max-disk-write-rate-mbps rate

Schedule periodic backups.

Scheduling options include:

• trigger-time schedule—The cron expression of the backup schedule.

• node hostname—Hostname of the node on which you want to execute the backup scheduling command and store the backup job logs. Use the kubectl get nodes command on the Linux root shell to determine the correct hostname.

• storage-location remote-path—Path where the backup files must be stored remotely. Enter the location in the following format:

  scp://host:port/path or sftp://host:port/path

• user username—Username to log in to the remote location.

• password password—Password to log in to the remote location. If you do not enter the password, you will be prompted to enter it.

• type (full | config | telemetry) —Back up your current Routing Director network configuration information, telemetry information, or both. If not specified, both configuration and telemetry information are backed up.

• max-disk-write-rate-mbps rate—Specify maximum disk I/O limit (in Mbps) only for the VictoriaMetricsDB when scheduling a backup. If no rate is specified, a rate of 800 Mbps is applied only to the VictoriaMetrics DB when scheduling a backup.

Rerun this command to edit an existing backup schedule.