Check the active and next-boot OPNsense snapshot separately

OPNsense ZFS snapshot states distinguish the running environment from the next boot target; include later configuration changes in the rollback decision.

Resilient network core with engineered blue and gold data paths.
DSE visual intelligenceNetworks & infrastructureGuide · 3 min read
Executive summary

What you need to know

OPNsense ZFS snapshot states distinguish the running environment from the next boot target; include later configuration changes in the rollback decision.

Potentially affected

OPNsense boot-environment snapshots on ZFS; UFS and hypervisor snapshot workflows are outside this article.

DSE recommendation

DSE recommends recording both current and next-boot environments and the configuration changes a proposed rollback would discard.

Bottom line: Before selecting a firewall snapshot, name the environment running now and the one selected for the next boot. Add the intervening configuration changes to the decision so recovery does not quietly discard work the operation still needs.

Source fact: what the authority says

The OPNsense snapshot guide says snapshots require ZFS and are unavailable with UFS. Its state table uses N for active now, R for active after reboot, and NR for both. The guide provides WebGUI and boot-menu paths for selecting a saved environment. It warns that configuration changes made after the selected snapshot will be lost when rolling back, and says a configuration backup and import can become necessary.

What the source does not establish

This article addresses the documented firewall boot-environment workflow. It does not prove that a saved environment boots on the actual appliance or that a later configuration is appropriate for an earlier release. DSE keeps configuration reconciliation and service recovery as explicit follow-on decisions.

Applicability questions

  • Is the appliance using ZFS, and what environment is actually running?
  • Which environment is selected after the next reboot, and who checked that assignment?
  • What configuration changes occurred after the proposed recovery point?
  • Can the authorized operator reach the documented boot-selection path if the WebGUI is unavailable?

DSE recommendation: controlled next steps

The following steps are DSE recommendations based on the cited source.

DSE recommends a short recovery worksheet containing the current environment, next-boot environment and proposed known-good environment as three separately checked entries. Capture the observed state before changing it. Ask another operator to predict the next boot from that worksheet and resolve disagreement while the existing management connection is still available.

Maintain a dated list of configuration changes since the proposed recovery point. For an upgrade rehearsal, include a harmless later change as an explicitly proposed test input. Have its owner decide whether the recovery should discard it, reapply it or require another documented route. Keep a protected current configuration backup, but do not treat its existence as proof that importing it into an older environment is appropriate.

Prepare the management access and service checks before the reboot decision. Review the appliance’s actual console route with the person who will use it. Leave snapshot deletion and renaming outside the initial recovery step until the intended environment and required service behavior have been observed. Make the cleanup decision from the confirmed state rather than from the name that happens to sound correct.

Use unambiguous environment names and preserve the observed state flags beside them. Ask the reviewer which exact environment a power cycle would select before the exercise. Keep that prediction with the subsequent observation so a label error can be distinguished from a service fault.

Verification and evidence

Proposed verification: rehearse on an approved representative appliance or isolated arrangement using the applicable documented workflow. Record the state flags, selected boot target and observed environment after reboot. Check the proposed later configuration item and compare its resulting state with the owner’s written disposition.

Exercise the alternative management path only within the approved plan; do not deliberately strand a live firewall to demonstrate it. Retain environment names, state captures, configuration identifiers, restart times and the specific routing or application checks performed. Mark any inaccessible console path or unreconciled configuration as unresolved before relying on the recovery procedure.

Official references

Source review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.

Primary reference

Review the official source

OPNsense — Snapshots · Verified October 28, 2026

Open official reference ↗
Plan the next step

Need help applying this guidance safely?

DSE can help confirm applicability, protect service continuity, and validate the result across physical security and IT systems.

Talk with DSE