Bugs found in backup restoration process

[Kym Busby]

I've been moving a few of my customers cloud-hosted 3CX instances to new hosts and I've encountered issues with the backup/restore process which doesn't make any sense.

All instances I've seen the issues on have been running either v16 update 3 or update 4, have had Instance Manager installed and have had automatic scheduled backups configured to an offsite FTP server.

This is the process I've been following:

1. Take full backup of ALL data via 3cx Management Console and download to local computer.
2. Shut down instance completely.
3. Spin up new instance with current 3cx Debian ISO from https://www.3cx.com/phone-system/download-links/
4. Complete initial setup, restart VM then proceed to setup from http://yourpublicip:5015?v=2.
5. Upload the backup taken in step 1, and see through to completion.

Now, once this is done, the PBX starts up fine, however there are several things that are not restored properly as well as things that should be completed as part of the process:

1. Automatic Scheduled backups are no longer configured and must be reconfigured, including the encryption key.
2. The backup location inexplicably changes to a local directory, despite still being set to FTP WITH the username and password for the offsite server still stored.
3. It is necessary to re-run the firewall checker to clear the red exclamation warning on the dashboard. This I understand, however surely could be automated as part of the restore process and then show an alert if failed.
4. Instance Manager must be reinstalled. Again, this is something that should be flagged in the restore process and automatically performed if it was previously enabled.
5. Updates: After installing from the current ISO, and restoring from the backup, I found there are several updates that need to be installed. 1 is the Windows App, then phone templates, then SIP trunk templates. Finally, you then have to go into Settings -> System Prompts to update your chosen System Prompt language (why this is in a different section I don't know). It would make more sense for these things to be included in the backup, OR some note of them being installed so they can be reinstalled automatically.

Some of this may sound petty, but to me it seems the process could be polished somewhat....