If you have an on-premise PortaSwitch installation that uses an Oracle database cluster (Oracle RAC), you can migrate it to a MySQL-based installation in Oracle Cloud Infrastructure (OCI), managed by PortaOne. (RAC requires a very specific hardware configuration for a shared disk array, and is not compatible with virtual resources in the cloud.) The MySQL database delivers the same reliability and performance as a single-node Oracle database – and with the PortaOne team using cloud capabilities for disaster recovery, your service will be as resilient as it was with an on-premise Oracle database cluster.
Migrating an Oracle-based on-premise installation to the cloud eliminates the need to purchase or maintain physical servers and significantly reduces administrative workload, as the cloud infrastructure is fully maintained by PortaOne.
For this type of migration, a new MySQL-based installation is deployed in OCI. Since the new installation contains a new database, you must configure key components – vendors, DID/SIM inventories, and product catalogs (via UI or API) there. After the product catalog is set up, PortaOne Support migrates customers, resellers, and representatives from the on-premise PortaSwitch to the cloud-based PortaSwitch.
Owl Telecom currently operates an on-premise, Oracle-based PortaSwitch and plans to migrate to OCI. The PortaOne Support prepares a new cloud-based system and provides access to Owl Telecom.
The migration process then follows these steps:
- Owl Telecom pre-configures mandatory entities such as vendors, DIDs/SIM cards inventories, and product catalogs in the cloud-based system for their customers.
- PortaOne Support migrates customers (with their accounts), and representatives to the cloud. It also migrates empty resellers (without subentities) to recreate the reseller structure in the cloud-based system.
- Owl Telecom configures a default product for use by their resellers. Each reseller then configures product catalogs for their customers and subresellers using the new portal URL.
- PortaOne Support migrates resellers’ subcustomers (with their accounts), subresellers, and reseller individuals to the cloud-based PortaSwitch.
- After all entities have been migrated, the service provider switches traffic from the on-premise system to the cloud system by updating the DNS records for SIP registrations and portal access.
Specifics
- Only customer, reseller, and representative entities (together with their billing data, like xDRs of the current billing period) can be migrated from the on-premise system to the cloud-based one. All other required entities must be pre-configured manually by the admin via the web interface or API.
Please note that the larger the gap between releases, the more challenging the pre- and post-migration activities become.
- All customers, resellers, and representatives must be migrated in a single run because entities in the on-premises system remain active, continue using services, and generate billing data until the traffic switchover.
Limitations
- Only the billing data for the current billing period is migrated. Historical data, such as xDRs from previous billing periods, are not migrated.
- Transferring the migrated entities back to the on-premise system is not supported.
