- Joined
- Mar 11, 2019
- Messages
- 288
- Reaction score
- 37
Hi,
We are planning to migrate our 3CX v20 installation from a windows server to a debian server, keeping the deployment at the same physical location.
The new debian server will use the same IP address and FQDN as the existing windows-based 3CX server.
To carry out the migration, we intend to shut down the windows server and then install 3CX on the debian server, configured with the same IP and FQDN.
However, our 3CX environment is integrated with multiple systems such as our CRM, which must function correctly after the migration.
Given this dependency, we want to ensure we have a fallback plan in case the debian server or related integrations do not work as expectd.
Our proposed fallback is to simply power down the Debian server and bring the Windows server back online with the original 3CX installation.
The question is, Is this fallback plan viable?
Specifically, can we revert to the windows-based 3CX server without requiring a fresh installation?
or would there be any issues related to licensing or FQDN/SSL that would prevent a seamless rollback?
Kindly, please provide your insights.
Thank you in advance.
We are planning to migrate our 3CX v20 installation from a windows server to a debian server, keeping the deployment at the same physical location.
The new debian server will use the same IP address and FQDN as the existing windows-based 3CX server.
To carry out the migration, we intend to shut down the windows server and then install 3CX on the debian server, configured with the same IP and FQDN.
However, our 3CX environment is integrated with multiple systems such as our CRM, which must function correctly after the migration.
Given this dependency, we want to ensure we have a fallback plan in case the debian server or related integrations do not work as expectd.
Our proposed fallback is to simply power down the Debian server and bring the Windows server back online with the original 3CX installation.
The question is, Is this fallback plan viable?
Specifically, can we revert to the windows-based 3CX server without requiring a fresh installation?
or would there be any issues related to licensing or FQDN/SSL that would prevent a seamless rollback?
Kindly, please provide your insights.
Thank you in advance.