|
| 1 | +.. _rm-deployment-considerations: |
| 2 | + |
| 3 | +========================= |
| 4 | +Deployment Considerations |
| 5 | +========================= |
| 6 | + |
| 7 | +.. contents:: On this page |
| 8 | + :local: |
| 9 | + :backlinks: none |
| 10 | + :depth: 1 |
| 11 | + :class: singlecol |
| 12 | + |
| 13 | +In the context of Relational Migrator, deployment considerations refers |
| 14 | +to where the servers, networking equipment, and databases are located. |
| 15 | +This page outlines location specific details to consider when using |
| 16 | +Relational Migrator. |
| 17 | + |
| 18 | +How to Run Relational Migrator |
| 19 | +------------------------------ |
| 20 | + |
| 21 | +The following table outlines high-level recommendations for how to |
| 22 | +run Relational Migrator. Also note that the |
| 23 | +:ref:`Kafka deployment model <kafka-intro>` provides greater |
| 24 | +resilience and scalability and can be used with any of the |
| 25 | +deployment options. |
| 26 | + |
| 27 | +.. list-table:: |
| 28 | + :header-rows: 1 |
| 29 | + :widths: 40 60 |
| 30 | + |
| 31 | + * - Use case |
| 32 | + - Recommended environment |
| 33 | + |
| 34 | + * - Smaller scale or debugging and testing jobs that run for |
| 35 | + less than four hours. |
| 36 | + - Laptop / Desktop / Docker |
| 37 | + |
| 38 | + * - Larger scale production jobs that run for more than four |
| 39 | + hours. |
| 40 | + - Remote server / EC2 / Azure VM |
| 41 | + |
| 42 | +Where to Run Relational Migrator |
| 43 | +-------------------------------- |
| 44 | + |
| 45 | +For best performance, locate the machine or server running Relational |
| 46 | +Migrator as geographically close to the source and target databases as |
| 47 | +possible. Proximity to the target database influences performance |
| 48 | +the most: |
| 49 | + |
| 50 | +- If you're using Relational Migrator for an on-premises migration, |
| 51 | + run Relational Migrator in the same data center as the source |
| 52 | + database. |
| 53 | + |
| 54 | +- If you're using a cloud hosted database, run Relational |
| 55 | + Migrator on an EC2 instance or VM in the same |
| 56 | + :abbr:`VPC (Virtual Private Cloud)` as the source database. |
| 57 | + |
| 58 | +.. tip:: |
| 59 | + |
| 60 | + Check the sleep timeout setting for your operating system. If your |
| 61 | + machine goes to sleep during a migration, the sync job fails. |
| 62 | + |
| 63 | +Network Considerations |
| 64 | +---------------------- |
| 65 | + |
| 66 | +When using Relational Migrator, the system firewall on the machine or |
| 67 | +server must allow outbound TCP traffic to both the source and |
| 68 | +destination databases. |
| 69 | + |
| 70 | +Cloud Networking |
| 71 | +~~~~~~~~~~~~~~~~ |
| 72 | + |
| 73 | +When running Relational Migrator in a cloud environment, check the |
| 74 | +cloud specific firewall (security group), router table, and |
| 75 | +the server firewall configurations. For details on specific cloud |
| 76 | +provider network configurations, see these pages: |
| 77 | + |
| 78 | +- `AWS Networking <https://docs.aws.amazon.com/vpc/>`__ |
| 79 | +- `Azure Networking <https://azure.microsoft.com/en-us/products/category/networking>`__ |
| 80 | +- `GCP Networking <https://cloud.google.com/vpc/docs>`__ |
| 81 | + |
| 82 | +System Hardware |
| 83 | +--------------- |
| 84 | + |
| 85 | +For specific hardware recommendations, see :ref:`rm-system-requirements`. |
| 86 | + |
| 87 | +.. note:: |
| 88 | + |
| 89 | + Scaling up the Atlas cluster size can significantly improve migration |
| 90 | + speeds. For details, see :ref:`scale-cluster-instance`. |
| 91 | + |
| 92 | +Get Started |
| 93 | +----------- |
| 94 | + |
| 95 | +For detailed installation instructions, see :ref:`installation`. |
0 commit comments