Create Full Backup script questions
Fiberoptic last edited by
I recently purchased and installed a new pfsense system, and want to have a separate backup system that I can plug-in in place of the original if it fails/fries etc.
To do the above, I want to be able to restore a box to the exact state/config of the original as quickly and easily as possible.
I have read several topics on this forum pertaining to this subject. The first and easiest solution i came across was backing up config.xml.
However, I'm using DansGuardian, and I haven't seen a firm answer to whether or not config.xml can backup package configs. Even if it does, I want to avoid having to manually copy in all my acls for DG.
I also came across the create/restore_full_backup scripts, but I'm not sure what advantages these bring over basic config.xml backup, and if the script backups fully backup all package files.
Apologies if any of these questions have obvious answers, I did do some google/forum searching before posting…
Thanks in advance
phil.davis last edited by
The configuration of everything is in config.xml including package settings.
The trickier part of really being "ready to go" with the backup system is that you need to get the actual package code/binaries onto it. If it happens to use DHCP on WAN then you can plug it in somewhere that is not the live office LAN (because that IP range will already be on the LAN side of the backup device) and let it get DHCP. Then you can do an upgrade of pfSense to the latest version and let it install all the packages… while it is running a copy of your real config.xml.
If the production WAN settings are some static IP or PPPoE or... then it only works when connected to your production ISP link. You have to either:
a) Modify the WAN settings to get it internet access from somewhere, do the upgrade, package installs, change the WAN settings back to (hopefully) the correct ones for production, or;
b) Take the production system offline for a bit (downtime), put the backup system in place, upgrade the backup with package installs..., shutdown the backup spare and put the production back online.
It is all a bit tricky to get a full operative cold spare installed and completely ready-to-go in a reliable way without interrupting production.
Maybe someone else has a good method for this?