Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

request system snapshot (Junos OS with Upgraded FreeBSD)

 

Syntax

Release Information

Command introduced in Junos OS Release 15.1 for MX240, MX480, MX960, MX2010, and MX2020 routers and EX9200 switches.

Command introduced in Junos OS Release 17.3 for SRX5400, SRX5600, and SRX5800 devices.

Command introduced for all platforms using Junos OS with upgraded FreeBSD. To find which platforms in which releases use Junos with upgraded FreeBSD, see Feature Explorer, enter freebsd, and select Junos kernel upgrade to FreeBSD 10+.

Description

Junos OS with upgraded FreeBSD has two types of snapshots: recovery snapshots and non-recovery snapshots. Non-recovery snapshots are the ones taken with the request system snapshot command. Non-recovery snapshots are essentially lists of software components and configuration files, which can be helpful when major software or configuration changes are occurring and establishment of a known stable system baseline is required. Recovery snapshots are the ones taken with the request system snapshot recovery command. Recovery snapshots, shown as recovery.ufs files, are full copies of the packages and configuration taken at the time the snapshot command is issued. QFX with TVP platforms do not support these commands.

On the router or switch, back up the currently running and active file system partitions to standby partitions that are not running. Non-recovery snapshots are named snap.date.time and stored in the /packages/sets directory.

Caution

After you run the request system snapshot command, you cannot return to the previous version of the software, because the running and backup copies of the software are identical.

Options

noneOn the router or switch, back up the currently running and active file system partitions to standby partitions that are not running. Specifically, this creates a non-recovery snapshot named snap.< date>.< time> which is stored in /packages/sets.
delete snapshot-name(Optional) Delete a specific non-recovery snapshot from /packages/sets. Wildcards are supported, so request system snapshot delete snap* deletes all snapshots.
load snapshot-name(Optional) Load a specific snapshot from /packages/sets.
media type(Optional) Specify the boot device the software is copied to:
  • usb—(MX960 routers only) Copy software to the device connected to the USB port.

recoveryCreate a recovery snapshot and store it in the /oam volume.

Additional Information

Before upgrading the software on the router or switch, when you have a known stable system, issue the request system snapshot command to back up the software, including the configuration, to the /packages/sets file systems. After you have upgraded the software on the router or switch and are satisfied that the new packages are successfully installed and running, issue the request system snapshot command again to back up the new software to the /packages/sets file systems.

The snapshot script (which is the script that generates output for non-recovery snapshots) does not generate XML output. In such cases, the < output> tag is used.

user@host> request system snapshot | display xml

This is documented in <rpc-reply> in the Junos XML Management Protocol Developer Guide.

Required Privilege Level

maintenance

List of Sample Output

request system snapshot recovery

request system snapshot

show system snapshot

request system snapshot delete

Output Fields

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

Sample Output

request system snapshot recovery

user@host> request system snapshot recovery

request system snapshot

user@host> request system snapshot

show system snapshot

user@host> show system snapshot

request system snapshot delete

user@host> request system snapshot delete snap.20150112.122106