Autorecovery of Configuration, Licenses, and Disk Information

Overview

The autorecovery feature is supported on dual-partitioned devices. With this feature, information on disk partitioning, configuration, and licenses is recovered automatically in the event it becomes corrupted.

In devices running FreeBSD Release 12 or later, you cannot back up data with the autorecovery feature. Instead, back up data using snapshots. To learn if your device is running FreeBSD Release 12 or later, issue the show version command and look for the fbsd_builder_stable string in the module names. If the string includes the number 12 or later, your device is running FreeBSD Release 12 or later.

Autorecovery provides the following functions:

• Detects corruption in disk partitioning during system bootup and attempts to recover partitions automatically.

• Detects corruption in the Junos OS rescue configuration during system bootup and attempts to recover the rescue configuration automatically.

• Detects corruption in Junos OS licenses during system bootup and attempts to recover licenses automatically.

How Autorecovery Works

The feature works in the following ways:

• The request system autorecovery state save command backs up important data such as disk partitioning information, licenses, and Junos OS rescue configuration.

• Once the backup copies are saved, the copies are used to check the integrity of the working copies of the data on every bootup.

• The working copies are automatically recovered if any corruption is detected.

How to Use Autorecovery

You use autorecovery in the following ways:

• Prepare the router for deployment with the necessary licenses and configuration.

• After you finalize the state, issue the request system autorecovery state save command to back up the state.

• After you save the state, integrity check and recovery actions (if any) occur automatically on every bootup.

• If subsequent maintenance activities change the state of the router by adding licenses or updating the configuration, you need to issue the request system autorecovery state save command again to update the saved state.

• Issue the show system autorecovery state command any time to view the status of the saved information and the integrity check status of each saved item.

• Issue the request system autorecovery state clear command to delete all backed up data and disable autorecovery, if required.

Data That Is Backed Up in an Autorecovery

The following data is backed up during the autorecovery process:

• Rescue configuration (regenerated from the current configuration)

• License keys

• BSD labels (disk-partitioning information)

Data is backed up only when you issue the request system autorecovery state save command. Disk-partitioning information is backed up automatically from factory defaults (for new systems), on installation from the boot loader, and on snapshot creation.

Troubleshooting Alarms

Table 1 lists types of autorecovery alarms, descriptions, and required actions.

Considerations

• Devices must have dual-root partitioning for autorecovery to work.

• The request system configuration rescue save command regenerates the rescue configuration from the current Junos OS configuration and then saves it. Therefore, issuing the save command overwrites any existing rescue configuration.

• In general, the saved contents of the rescue configuration are not updated automatically. If you add licenses, you must issue the request system autorecovery state save command again.

  The rescue configuration is backed up. If /config is corrupted, the system boots from the rescue configuration.