Après la migration

Vérifié avant la mise en production

Quand un serveur démarre sur AWS, il est comparé à la source. Quand une base de données passe sur Amazon RDS, elle est comparée à la source avant la bascule.

Automated QA after launch

When the server boots on Amazon EC2, the CloudHound agent on it checks it against the source: every service, port, database, volume and network path the source used.

Waiting for the server to bootExample: a Windows Server 2019 application server with IIS and SQL Server

0/26

Collecting information from the server

How to fix it

Neither issue is on the server. The route table of its subnet in AWS has no route to two networks on premises. In the VPC console, open that route table and add:

10.20.8.0/24 through the transit gateway, for the 3 app servers
10.20.9.0/24 through the transit gateway, for the mail relay

Database handover

When a server's databases are replatformed, CloudHound restores them into Amazon RDS and compares RDS with the source before handing over. Any mismatch stops the handover and the database stays on the EC2 copy. This replay is a 300 GiB SQL Server 2022 database moved to Amazon RDS for SQL Server on a db.m8i.8xlarge.

RDS instance-Created while the server syncs
Preflight-Database fenced and checked
Restore-Backup, upload, restore
Verify-RDS against the source
Handover-Online on RDS

Check

Source

RDS

Result

RDS instance ready

Checked before it goes live

Every move ends with the target compared against the source. A rehosted server is checked by the CloudHound agent on its EC2 copy once it boots. A replatformed database is compared table by table with Amazon RDS, and any mismatch stops the handover.

Check

Source

Copy

Result