Choose pfSense backup contents for the recovery task, not just the XML filename

Package settings, graph history, volatile databases, and SSH host identity are separate backup choices.

Source facts

Netgate documents backup options for configuration areas, package data, RRD graph data, extra captive-portal and DHCP databases, and SSH host keys. Omitting package data means packages must be reinstalled and reconfigured after restore. Extra databases are volatile, while preserving SSH host keys can help clients recognize the recovered firewall.

Source: Netgate — Making Backups in the GUI.

Applicability

This concerns the pfSense GUI backup export.

DSE recommendation

DSE recommends labeling each export with its purpose and selected options. Keep a complete recovery export distinct from a deliberately reduced troubleshooting export. Decide whether graph history and volatile lease or portal data matter for the expected recovery, and protect the resulting file as sensitive configuration. Record which identity material must remain stable when moving to replacement hardware. Avoid treating a small successful download as proof that every operational dependency is included. Require the export operator to record the selected checkboxes alongside the recovery objective. Compare that manifest with the rehearsal target before importing anything. If a deliberately excluded database or identity matters to recovery, assign its collection method rather than silently redefining completeness.

Verification

Inspect the selected backup scope and retain a protected inventory of its expected contents. Rehearse restoration on an isolated target and confirm package settings, required service data, and SSH identity behavior. Document anything that needs a separate backup method before calling the recovery set complete.

Official reference

Netgate — Making Backups in the GUI. Reviewed October 20, 2026.