Routing
Highlighted
Routing

backup

‎05-13-2020 08:11 PM

hi all,

what is the best practice for snapshot....In the lab I tried the get a snapshot. but how to rollback? And where this snapshot sits?

 

jcluser@vMX1> show system snapshot
No non-recovery snapshots available on the Junos volume

Recovery Snapshots:
No recovery snapshots available on the OAM volume
jcluser@vMX1>
jcluser@vMX1> request system snapshot recovery
Creating image ...
Compressing image ...
Image size is 1005MB
Recovery snapshot created successfully

jcluser@vMX1>
jcluser@vMX1> show system snapshot
No non-recovery snapshots available on the Junos volume

Recovery Snapshots:
Snapshots available on the OAM volume:
recovery.ufs
Date created: Thu May 14 02:57:54 UTC 2020
Junos version: 18.2R1.9

Total recovery snapshots: 1

jcluser@vMX1>

 

4 REPLIES 4
Highlighted
Routing

Re: backup

[ Edited ]
‎05-13-2020 08:32 PM

Hi Arix,

 

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 the 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.

 

On Routers, you can simply run the "request system snapshot" command to execute the snapshot.

https://www.juniper.net/documentation/en_US/junos/topics/reference/command-summary/request-system-sn...

 

To check the location of the snapshot:

user@host> show system snapshot
content_copy
zoom_out_map
Non-recovery snapshots:
Snapshot snap.20190412.124526:
Location: /packages/sets/snap.20190412.124526            <<< LOCATION
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:                   <<< LOCATION
recovery.ufs
Date created: Thu Mar 28 07:44:25 PDT 2019
Junos version: 18.3R1.8

Total recovery snapshots: 1

 

By rollback snapshot, if you mean to delete the snapshot you took, the below should help :

user@host> request system snapshot delete snap.20150112.122106
content_copy
zoom_out_map
NOTICE: Snapshot ’
snap.20150112.122106’
deleted successfully

 

You may also want to check the below links-

"request system recover"

https://www.juniper.net/documentation/en_US/junos/topics/reference/command-summary/request-system-re...

 

Create a snapshot on OAM volume successfully:

https://kb.juniper.net/InfoCenter/index?page=content&id=KB33892&actp=METADATA

 

Hope this helps 🙂 

 

Please mark this Accepted Solution if this helps you solve your query.

Kudos are much appreciated too 🙂

Highlighted
Routing

Re: backup

‎05-13-2020 10:50 PM

Hi Arix,

 

The best practice would be to create both recovery and a non-recovery snapshots. 

Some notes about recovery snapshots:

•Only one recovery snapshot can exist on the OAM volume at a time

•Recovery snapshots can be used to recover the Junos volume

•They are also equivalent to “alternate media” boot on legacy

 

As updated by bmanvita "show system snapshot"  (non-recovery snapshot)  will be stored in /packages/sets/snap.20151121.224043. But recovery snapshot is stored in OAM volume and is not mounted to keep it pristine that means ‘show system storage’ will not show the OAM volume.  So there is no way to check via the CLI any details on the recovery snapshot info: - other than the below message when doing the command there is no other way to find out if a OAM recovery snapshot is available via the CLI.

 

 

lab@Thunder-MX480-re1> request system recover oam-volume   

NOTICE: Recovering the OAM volume ...

ada0p2 deleted

ada0 created

ada0p1 added

bootcode written to ada0

ada0p2 added

/dev/gpt/oam: 999.1MB (2046096 sectors) block size 32768, fragment size 4096

        using 4 cylinder groups of 249.78MB, 7993 blks, 32000 inodes.

super-block backups (for fsck_ffs -b #) at:

 192, 511744, 1023296, 1534848

Verified oam signed by PackageProductionEc_2015

Installing OAM volume contents ...

The OAM volume is now installed

NOTICE: Creating a recovery snapshot on the OAM volume ...

Creating image ...

Compressing image ...

Image size is 866MB

Recovery snapshot created successfully

NOTICE: OAM volume recovered

 

 

If this solves your problem, please mark this post as "Accepted Solution" so we can help others too

 

Kudos are appreciated too 

 

 

Regards,

Nadeem

Highlighted
Routing

Re: backup

‎05-14-2020 09:22 PM

Hi Arix,

 

While I was looking for something, I happened to come across the below document which might clarify all your doubts on the recovery and non-recovery snapshots.

https://kb.juniper.net/InfoCenter/index?page=content&id=KB32170&actp=METADATA

 

Do give it a read. Although it is for EX/QFX, it is very informational and relevant to our discussion here.

 

Hope it helps 🙂

 

Please mark "Accepted Solution" so that it can help others too.

Kudos would be great if you feel this post deserves it 🙂

Highlighted
Routing

Re: backup

‎05-15-2020 08:46 AM

Hi Arix,

 

Feel free to let us know, should you need any further details on this one.

 

If you find a solution that helped you, please mark it "Accepted" so that it can help others.

Feedback