Migration to Azure from an on-premise CloudBlue Commerce installation using Azure Site Recovery (ASR) is one of the two possible migration scenarios.
This migration procedure is applicable for platform-related hosts:
- Operations Management node
- Operations DB node
- Billing Application node
- Billing DB node
- CloudBlue Commerce Online Store node
- The PrivacyProxy service node
- APS application endpoint nodes
This migration procedure is not applicable for:
- UI nodes or UI cluster
- DNS nodes
- On-premise-only nodes
Migration Procedure
To migrate virtual machines using Azure Site Recovery, please follow official Microsoft documentation.
As the migration result:
- Source on-premise machines will be replicated to Azure.
- For infrastructure-dependent services, such as networking, new Azure-specific configuration will be created.
- The file system content will be replicated to new Azure virtual machines, except for infrastructure-related configuration files (such as network configurations).
Recommendations
When following the migration procedure from official Microsoft documentation to migrate on-premise CloudBlue Commerce virtual machines to Azure using the Azure Site Recovery service, please take into consideration the following recommendations:
Pre-Migration
- When setting the Protection goal field:
- For virtual machines for which there are special Protection goal options, use those options. This will automate the IP address assignment and simplify the Configuration server deployment.
- For virtual machines for which there are no special options to complete the Protection goal field, choose the Physical machine option.
- Remember that container migration (including Virtuozzo containers) is not supported.
- When preparing a set of resources in Azure, to ensure data integrity and security, create and assign security groups.
- When deploying the Configuration server:
- Associate the on-premise Configuration server, which orchestrates the replication and failover processes, with the Recovery Service vault.
- Make sure that the Configuration server has access to the Internet.
- When configuring the replication process for target hosts, make sure that the Configuration server can connect to the target hosts (which may not have access to the Internet).
Migration
Before the actual migration (or "failover"), perform a test migration. If the test migration fails, it is easy to roll back.
Post-Migration
After your installation is migrated, manually adjust the infrastructure-dependent service configurations in Azure.