Backup/restore props and procedure

Discovered a system on its lips last week. Just recovered it successfully from a backup, albeit older due to MS taking it upon themselves to reset some custom firewall settings. Thank you to the folks who have worked hard to make the backup/restore process reliable.

I thought I’d share the basic procedure we’ve used multiple times, as there are some little tricks that make it go much faster/smoother.

Preface: Some of this is specific to Windows Server (Hyper-V and IIS/FTP) environments…

  1. We always restore to the same major version as the crashed system. So download the ISO, create a new VM, and do the basic setup. Do NOT activate at this time.
  2. Yum update and reboot.
    3.Login to the GUI. Do not activate. Update modules until all are current.
  3. On the new system, run a local backup. This is required to create the directory where it will look for files to restore later.
  4. Use WinSCP to copy the backup file from which we will restore to /var/spool/asterisk/backup/Default_backup. Again, this directory will not exist until a local backup is run.
  5. Chmod the backup file you just coped to 777 (we use WinSCP to do this).
  6. Modify postfix to not use IPv6 (pretty sure this change is not included in backups).
  7. Shut down the broken system (if it’s running).
  8. Shut down the new system.
  9. Copy the MAC from the broken system to the virtual NIC on the new system. This will result in the new system getting the correct IP via DHCP.
  10. Start the new system.
  11. Login to the GUI and restore from local backup. Make sure to choose the file you uploaded (there will be two files). Also make sure to check all boxes.
  12. Login to and unlock the activation for the broken install. Note the deployment ID.
  13. Go to System Admin and follow the prompts to activate. Choose the option to use an existing deployment ID.
  14. Apply the config and then go through the module update process again.

Again, we’re grateful to everyone who has working on the Backup/Restore module to make it what it is now- something that admins can rely on in an emergency.


Important to note that the Backup operation is quite different in 15, so all of the backup module specific stuff above is for FreePBX 14 or lower.

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.