Hello,
Our current protocol for updating 3CX versions is to bring up a staging system with it's own license and FQDN to which we restore a backup of the target production system minus the license and FQDN. We then register test deskphones, apps, etc. and fully QA. This allows us to create a thorough update protocol specific to the site before applying the update to the production system.
With configuration only backups not yet available for V20 and the new version only supporting backups locked to the FQDN and license, going forward, what would be the suggested practice to test a new 3CX version against a production configuration?
Thank you!
Our current protocol for updating 3CX versions is to bring up a staging system with it's own license and FQDN to which we restore a backup of the target production system minus the license and FQDN. We then register test deskphones, apps, etc. and fully QA. This allows us to create a thorough update protocol specific to the site before applying the update to the production system.
With configuration only backups not yet available for V20 and the new version only supporting backups locked to the FQDN and license, going forward, what would be the suggested practice to test a new 3CX version against a production configuration?
Thank you!
