Restoring a V18 configuration to a new instance

[Dominique_CH]

Hi,
I'm testing restoring the backup of a live system to a test system:
- both systems are hosted and V18
- the live system was backed up w/o FQDN & license info
- the test system has a different FQDN
- the restore completes successfully
- SIP-trunks of the restored system are manually disabled for now (although they connect correctly)

So far so good, but the following is strange:
- adding the test account to my 3cx-app on my Smartphone REPLACES the live system's account. This is strange, because even if user/pwd are identical, FQDNs aren't (but changing ID/pwd makes no difference)
- luckily, "adding" the live account replaces the test account

I suspected an issue with the SSL-certificate, but checking the certificate, it bears the correct FQDN and was issued when the new system was installed. It is different from the restored system!

Has anyone a good idea or explanation?

 

[TheodorosG_3CX]

Can you please clarify the exact steps that you are following?

 

[Dominique_CH]

The restore process is quite simple, both systems being hosted at 3CX:
1. Backup live system excl FQDN & license
2. Deploy new test instance with new FQDN & license
3. Restore the backup from step1 onto test instance
4. Open user on test admin console and scan QR-code to add account => replaces rather than adds a new account

To recover the original live acct on my Smartphone-app:
5. Open user on live admin console and scan QR-code => OK