Server Migration Completion Report
Date: 2026-09-27
Service Status: Migration completed; all business systems are operating normally
I. Overview
Because the provider of the original server (156.238.224.104) ceased operations and the machine was nearing expiration, we fully migrated all business systems to the new server (186.241.68.236).
Service was not interrupted at any point during the migration. User access, data reads and writes, and email sending and receiving remained normal throughout the migration.
II. Migration Results
| Item | Result |
|---|---|
| Migrated data | 49 GB, totaling 1,089,478 files |
| Data integrity | No missing data (confirmed by item-by-item comparison with the original server) |
| Business systems | All 31 services started successfully |
| DNS resolution | All 62 DNS records switched |
| Service interruption | 0 |
| Data loss | None |
III. Migrated and Verified Systems
Databases (all with complete historical data)
| System | Purpose |
|---|---|
| MySQL | Primary business database and email system data |
| PostgreSQL ×3 | Application database, user center database, and unified authentication database |
| MariaDB | Website management system database |
| Redis ×3 | Cache and session data |
All databases were checked individually: their table structures and record counts were exactly identical to those on the original server.
Websites and Web Services
- Configuration for 59 websites was migrated in full, and all passed configuration validation
- Web servers and the PHP runtime environment are ready
- Some sites have been tested and confirmed accessible
Application Services (31 total)
These include the API gateway, authentication system, email service, file service, search service, bot service, subscription service, monitoring system, and management panel, all of which are operating normally.
Management Panels
| Panel | Status |
|---|---|
| BT Panel | Operating normally |
| 1Panel | Operating normally |
Security Certificates
- 48 SSL certificates were migrated; all were verified as valid and correctly matched with their private keys
- The Let’s Encrypt automatic renewal account did not need to be re-registered and has been verified as functional
Internal Network Connectivity
The new and original servers have established a direct encrypted internal network connection, with latency of approximately 2 milliseconds. Even after the original server is taken offline, operations staff can securely access the new server through the internal network without exposing public ports.
IV. DNS Changes
All 62 DNS records now point to the new server, covering four domains:
| Domain | Number of records |
|---|---|
568131.xyz |
34 |
lezi.chat |
22 |
lezi-ai.bond |
3 |
lezi-chat.bond |
3 |
Email authentication (SPF) uses a gradual transition strategy: the IP addresses of both the new and original servers remain in the authentication record to ensure normal email delivery during the migration. The old record will be removed after the original server is officially taken offline.
A complete backup from before the changes has been archived and can be restored at any time if a rollback is needed.
V. Data Security
| Measure | Description |
|---|---|
| Pre-change backup | All DNS records (258 total) were fully backed up |
| Data verification | All migrated data was compared item by item, confirming no missing data |
| Original server retained | All data on the original server was preserved; nothing was deleted |
| No service interruption | The new and original servers operated in parallel throughout the migration |
VI. Outstanding Items
The following items are unrelated to this migration and concern expired authorizations or reconfiguration requirements in the original system:
| Item | Description | Required action |
|---|---|---|
| Some third-party API authorizations | Refresh tokens for upstream services have expired | Log in and authorize again |
| Website administration programs | Some backend services must be started manually | Awaiting startup |
| VPN service | Configuration is bound to the public IP address | Reconfigure |
| Email domain records | DNS targets have changed | Update records |
| Internal network tunneling | Credentials are bound to the original machine | Reauthorize |
VII. Improvements After Migration
- Improved performance: The new server has 8 cores / 7.6 GB of memory (the original had 4 cores / 3.8 GB)
- Disk space: 100 GB (the original had two disks totaling 29 GB + 69 GB)
- Simplified architecture: The original server had a legacy issue involving the same disk being mounted repeatedly. The new server has been standardized, eliminating potential path ambiguity
- Access channel: A new encrypted direct internal network connection makes operations and administration more secure
- Improved security awareness: The original server was found to have suffered long-term SSH brute-force attacks (410,000 failed attempts within one week). The IP addresses of 279 attack sources have been submitted to the international security threat intelligence database AbuseIPDB, most of which were marked as the highest risk level
VIII. Conclusion
The migration is complete. All business data, configurations, certificates, and container definitions were fully migrated to the new server and verified.
The systems are operating normally with no impact visible to users. The original server will be retained until its expiration as a fallback safeguard.
