A couple of weeks ago, I went out to one of my Schools and tried to replace their On-Premise FreePBX 16 with a shiny new FreePBX 17 virtual machine - I got all the way to restoring the Backup, but when I did, it didn’t throw any errors but I had no extensions (Zero!). Weird, but I still had the original machine, so I generated another backup and then tried to restore it again and…same thing - no extensions.
I ran out of time to work on it anymore, so I set it aside to work on other things.
Today, I tried to replace one of my FreePBX 16 machines on Vultr.
Same drill - Make sure the machine is fully up-to-date, run a Backup, load up a Debian 12 and then run the FreePBX 17 install script, and then finally, restore the backup.
Again, no errors, but when I was done, no extensions and only my Emergency Outbound Route (?).
I did some Google-Foo, and I saw a couple of posts about a similar problem, but no solution.
So I restored the old machine (it’s the same Virtual Machine) and used Bulk Handler to export every setting it could, copied all my Outbound Routes (they were simple) and then reloaded Debian 12 and ran the FreePBX 17 install script again.
I then used Bulk Handler to import all the exported settings - my Extensions were there.
Then I restored the Backup and it DELETED MY EXTENSIONS!
So I re-imported the Extensions using Bulk Handler and then finally recreated my Outbound Routes and I once again had a working machine now on FreePBX 17.
LOTS of extra work, but at least it works - I hate the Backup App with a passion that burns like fire…
Hopefully somebody sees this before they get stuck the way I did.