request system snapshot (Junos OS with Upgraded FreeBSD)

Syntax

Description

Junos OS with upgraded FreeBSD has two types of snapshots:

Recovery snapshot
Non-recovery snapshot

Recovery snapshots—Use the request system snapshot recovery command to create a recovery snapshot. The recovery snapshot contains copies of the packages and configuration taken at the time of the snapshot. The recovery snapshot is stored at recovery.ufs on the /oam volume.

QFX with TVP platforms do not support these commands.

CAUTION:

Once the platform performs a Junos OS upgrade to an upgraded FreeBSD version (Junos OS Release 15.1R1 or higher), Junos OS will automatically generate a recovery snapshot with the new Junos OS version. Thereafter, you should request a recovery snapshot every time you upgrade to a new software version.

Non-recovery snapshots—Use the request system snapshot command to create a non-recovery snapshot. The 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 establishing a known stable system baseline is required.

On the device, back up the currently running and active file system partitions to standby partitions that are not running. By default, non-recovery snapshots are named snap.date.time and are stored in the /packages/sets directory.

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

`none`	On 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.
configuration	Save a copy of the configuration files (contents of the /config and /var directories and SSH files) as part of the snapshot. This is the default.
`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 that start with "snap".
`load snapshot-name`	(Optional) Load a specific snapshot from /packages/sets.
`mediatype`	(Optional) Specify the boot device the software is copied to: `usb`—(MX960 routers only) Copy software to the device connected to the USB port.
name `snapshot-name`	Specify the name for a non-recovery snapshot.
no-configuration	Do not save a copy of the configuration files (contents of the /config and /var directories and SSH files) as part of the snapshot.
`recovery`	Create a recovery snapshot and store it in the /oam volume.

Additional Information

Before upgrading the software on the device, 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.

CAUTION:

After you have upgraded the software on the device and are satisfied that the new packages are successfully installed and running or if you have replaced one of the Routing Engines, you should also issue the request system snapshot recovery command to have a new updated recovery snapshot. Junos OS automatically recovers the Junos OS volume upon reboot, if considered defective, from the recovery snapshot, along with the configuration saved in the recovery snapshot.

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.

Required Privilege Level

maintenance

Output Fields

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

request system snapshot recovery