-
-
Option 1
CloudHound moves each server to AWS in one of two ways. It can rehost the whole server on Amazon EC2, with its disks copied block by block. It can also move the server's databases directly to Amazon RDS for SQL Server, PostgreSQL, MySQL or MariaDB. The path is chosen per server when replication starts, and both are costed before anything moves.
-
Option 2
CloudHound moves each server to AWS in one of two ways. It can rehost the whole server on Amazon EC2, with its disks copied block by block. It can also move the server's databases directly to Amazon RDS for SQL Server, PostgreSQL, MySQL or MariaDB. The path is chosen per server when replication starts, and both are costed before anything moves.
Option 3
CloudHound moves each server to AWS in one of two ways. It can rehost the whole server on Amazon EC2, with its disks copied block by block. It can also move the server's databases directly to Amazon RDS for SQL Server, PostgreSQL, MySQL or MariaDB. The path is chosen per server when replication starts, and both are costed before anything moves. The estate below is an example.
Instance sizes come from each server's measured usage. RDS is offered for servers running SQL Server, PostgreSQL, MySQL or MariaDB.
Option 4
CloudHound moves each server to AWS in one of two ways. It can rehost the whole server on Amazon EC2, with its disks copied block by block. It can also move the server's databases directly to Amazon RDS for SQL Server, PostgreSQL, MySQL or MariaDB. Both paths copy the server while it keeps running and stay in sync until cutover. The path is chosen per server, and both are costed before anything moves.
Option 5
CloudHound moves each server to AWS in one of two ways. It can rehost the whole server on Amazon EC2, with its disks copied block by block. It can also move the server's databases directly to Amazon RDS for SQL Server, PostgreSQL, MySQL or MariaDB. The path is chosen per server when replication starts, and both are costed before anything moves.