request system snapshot (Junos OS with Upgraded FreeBSD)
Syntax
request system snapshot <configuration> <delete snapshot-name> <load snapshot-name> <media type> <name snapshot-name> <no-configuration> <recovery>
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.
Once the platform performs a Junos OS upgrade to an upgraded FreeBSD version (Junos OS Release 15.1R1 or higher for most devices; or Junos OS Release 24.4R1 or higher for the SRX300, SRX320, SRX340, SRX345, or SRX380 devices)), Junos OS automatically generates 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. To find which platforms in which releases use Junos OS with upgraded FreeBSD, see Feature Explorer, enter freebsd, and select Junos kernel upgrade to FreeBSD 10+.
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
|
load snapshot-name |
(Optional) Load a specific snapshot from /packages/sets. |
media type |
(Optional) Specify the boot device the software is copied to:
|
| 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.
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.
user@host> request system snapshot | display xml <rpc-reply xmlns:junos="http://xml.juniper.net/junos/18.1I0/junos"> <output> NOTICE: Snapshot snap.20180105.165049 created successfully </output> <cli> <banner></banner> </cli> </rpc-reply>
Required Privilege Level
maintenance
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
- request system snapshot recovery
- request system snapshot
- request system snapshot name
- show system snapshot
- request system snapshot delete
request system snapshot recovery
user@host> request system snapshot recovery Creating image ... Compressing image . . . Image size is 777MB Recovery snapshot created successfully
request system snapshot
user@host> request system snapshot NOTICE: Snapshot snap.20190412.124526 created successfully
request system snapshot name
user@host> request system snapshot name pre-maintenance-snapshot NOTICE: Snapshot pre-maintenance-snapshot created successfully
show system snapshot
user@host> show system snapshot Non-recovery snapshots: Snapshot snap.20190412.124526: Location: /packages/sets/snap.20190412.124526 Creation date: Apr 12 12:45:26 2019 Junos version: 18.3R1.8 Total non-recovery snapshots: 1 Recovery Snapshots: Snapshots available on the OAM volume: recovery.ufs Date created: Thu Mar 28 07:44:25 PDT 2019 Junos version: 18.3R1.8 Total recovery snapshots: 1
request system snapshot delete
user@host> request system snapshot delete snap.20150112.122106 NOTICE: Snapshot ’snap.20150112.122106’ deleted successfully
Release Information
Command introduced in Junos OS Release 15.1.
Command introduced for all platforms using Junos OS with upgraded FreeBSD. To find which platforms in which releases use Junos OS with upgraded FreeBSD, see Feature Explorer, enter freebsd, and select Junos kernel upgrade to FreeBSD 10+.
configuration and no-configuration options added in
Junos OS Release 23.2R1.
name option added in Junos OS Release 23.2R1.