Backup and restore FAQs
Answers to the most frequently asked questions covering backup and restore.
Backup and restore assistant
How do I move VLANs to a different physical interface?
Take a backup of your current configuration, restore it on the same device, then change the mapping of the corresponding physical interfaces. This only applies if the backup is from 19.5 MR4 and later and restored to XGS, virtual, and cloud appliances running 20.0 MR2 and later.
Why can't I see the backup-restore assistant?
The backup-restore assistant only appears if all the following conditions are met:
- The backup is from any appliance (XG, SG running SFOS, XGS, virtual or cloud) running 19.5 MR4 and later.
- You're restoring to 20.0 MR2 and later.
-
You're restoring to XGS, virtual, and cloud appliances.
Note
If you're restoring to XG or SG series firewalls, the assistant doesn't appear.
Can I restore a backup from 19.5 MR3 and earlier to 20.0 MR2 or later?
Yes, you can restore a backup from 19.5 MR3 and earlier to 20.0 MR2 or later but the firewall doesn't show the backup-restore assistant for interface mapping.
Which compatibility matrix applies to firewalls running versions earlier than 20.0 MR2?
Firewalls running versions earlier than 20.0 MR2 follow our backup and restore compatibility matrix. See Backup and restore compatibility check.
How can I delete a pseudo port?
To delete a pseudo port, see Replace and delete pseudo ports.
Note
Unbound pseudo ports with VLAN configurations aren't deleted.
Does restoring a backup retains the firewall's Sophos Central registration?
Sophos Central registration is only retained when you restore a backup to the same firewall from which the backup was taken.
Restoring a backup to a different firewall or an HA cluster deregisters the firewalls from Sophos Central. You must register the firewalls to Sophos Central and reconfigure Sophos Central services such as Security Heartbeat and Sophos ZTNA again. See Backup-restore in HA.