Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

request paragon backup

Syntax

Description

Back up your Routing Director network configuration and telemetry data. Configuration data includes information stored in PostgreSQL, ArangoDB, and Airflow configuration database systems, along with all available software images, and AskParagon secrets keys. Telemetry data includes information stored in database systems such as OpenSearch, TimescaleDB including Active Assurance data, and VictoriaMetrics including Insights and Pathfinder data.

Additionally, you can schedule backups, upload your backup file to a remote location outside the Routing Director cluster and download a backup file from a remote location. You can also delete the backed-up data.

Options

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.

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 paragon 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

Back up only your current Routing Director telemetry information.

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)

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.

Rerun this command to edit an existing backup schedule.

Required Privilege Level

configure

Output Fields

When you enter this command, you are provided feedback on the status of your request.

Sample Output

request paragon backup

request paragon backup config

request paragon backup delete backup-id backup-id

request paragon backup download

request paragon backup telemetry

request paragon backup upload

request paragon backup schedule

request paragon backup delete schedule

Release Information

Command introduced in Juniper Paragon Automation Release 2.0.0.

config, telemetry, upload, and download options introduced in Juniper Paragon Automation Release 2.3.0.

trigger-time and delete schedule options introduced in Juniper Routing Director Release 2.5.0.