Shared Hosting Migration with IP Change and Decreased Downtime
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Migration of shared hosting environments with IP changes often results in significant downtime due to the need to move multiple web sites and mailboxes simultaneously, which can be lengthy, and IP switching is complicated by network configurations and DNS propagation times.
Innovation Solution
A method utilizing a migrator module that decreases TTL values on the source DNS server, sets up database replication, creates configurations and copies files to the target server, performs DNS switching, and synchronizes content, minimizing downtime by allowing gradual transition to the new IP address.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If IP switch is performed when moving all sites and mailboxes at once, then migration is completed in a single operation, but downtime is greater than the entire transfer time and network configuration may prevent the switch
Solution Approach 1:
The patent segments the migration process by maintaining separate DNS zones for source and target servers, allowing gradual transition of individual domains rather than forcing a complete simultaneous migration. Each domain can be migrated independently by updating its DNS zone to point to the target server, eliminating the requirement to migrate all sites and mailboxes at once.
Solution Approach 2:
The patent performs preliminary actions by pre-configuring the target DNS server with slave zones before migration, and pre-setting up database replication between source and target. This allows the target server to be ready to receive traffic immediately when DNS records are updated, minimizing downtime without requiring a complete IP switch of all services at once.
2Reliability
If DNS records are updated to point to target IP address after migration, then service moves to another IP address, but DNS propagation and cache update take a long time resulting in long downtime
Solution Approach 1:
The patent performs preliminary DNS configuration by setting up the target DNS server with slave zones and pre-configuring DNS records before the actual migration. This allows DNS propagation to begin in advance, so when the DNS switch occurs, the target server is already configured and ready to receive traffic immediately, eliminating the propagation delay that would otherwise occur after migration.
Solution Approach 2:
The patent introduces a DNS zone as an intermediary layer between the source and target servers. By using DNS zone transfer mechanisms (master-slave relationship), the system allows gradual propagation of DNS records to point to the target server without requiring a complete simultaneous switch, reducing the impact of DNS cache updates on service availability.
3Loss of time
If content migration is performed before DNS switch, then all files and databases must be transferred completely, but this adds significant time to the overall migration process
Solution Approach 1:
The patent performs preliminary content migration by copying files and setting up database replication before the DNS switch. The replication mechanism allows continuous synchronization during the transition period, ensuring data completeness without requiring the entire migration to be completed before DNS propagation begins.
Solution Approach 2:
The patent maintains continuous data synchronization between source and target servers during the migration process. Database replication and file synchronization continue to operate throughout the DNS transition period, ensuring that the target server always has up-to-date data without requiring a complete stop for data transfer.
Data Source
AI summary
A method, system and computer product for a migration of a shared hosting environment with an IP change is provided. Migration is performed with the help of a special tool—the migrator. For each migrated domain on the source server, the TTL (time to live) values are decreased on the source DNS server. If possible, for a database server, a replication between the source and the target servers is set up for migrated databases. The migrator creates configuration of web sites and mail service on the target server and copies files and mail messages from the source to the target server; the migrator creates databases (if replication is not available) on the target server; and the migrator creates DNS zones with DNS records pointing to the target server. Once administrator checks that site works well on the target server, the migrator performs content sync and sets DNS zone on the source server as slave to DNS zone on the target server.