设计环境架构以确保可靠性。在设计Google Cloud 环境时，您可以从多种架构中进行选择，包括如何在 Google Cloud区域和可用区之间分配资源。如需详细了解如何设计Google Cloud 环境，以及如何设计可靠的单区域环境，请参阅在 Google Cloud上设计弹性单区域环境。
为跨 Google Cloud 区域迁移做好准备。为跨 Google Cloud 区域迁移做好准备可帮助您避免在此类迁移期间出现潜在问题，并减少完成迁移所需的时间和工作量。例如，您可能希望为将来迁移到另一个区域做准备，因为您尚不知道特定区域是否最适合您的环境。或者，您可能会因为您预计将来对首选区域的要求可能会发生变化而为迁移做准备。您甚至可能会因为正考虑迁移到即将开放的区域而为迁移做准备。
设置边界以及安全和合规性控制措施，以确保工作负载和数据保留在特定 Google Cloud区域中。您可能必须遵守安全和监管要求，以便工作负载和数据只能保留在特定Google Cloud 区域中。如果您有此合规性要求，则可能需要实现边界、控制和审核，以在 Google Cloud 提供的保证的基础上确保位置、主权、隐私权和机密性。例如，您可能需要让您的环境符合强制要求某些工作负载和数据绝不离开位于特定政治、行政或州实体的特定区域的法规和安全要求。
最大限度地降低单区域和多区域环境以及跨 Google Cloud 区域迁移的费用。随着您的环境和 Google Cloud 占用空间的增加，您可能会考虑实现相应机制和流程，以控制和降低与环境以及跨区域迁移相关的费用。例如，您可以在特定区域中预配资源，优化网络流量模式，简化和自动执行流程，以及根据需要自动扩缩资源。如需详细了解如何降低费用，请参阅迁移到 Google Cloud：最大限度地降低费用。
[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2024-12-08。"],[[["\u003cp\u003eThis document series guides you through preparing for and executing the migration of workloads and data across Google Cloud regions.\u003c/p\u003e\n"],["\u003cp\u003eThe series covers how to design reliable, single-region environments and set up security and compliance controls to keep data within specific Google Cloud regions.\u003c/p\u003e\n"],["\u003cp\u003eYou will learn how to prepare for future migrations and how to manage migrations even if not planned in advance.\u003c/p\u003e\n"],["\u003cp\u003eThis content will guide you on how to minimize costs associated with single and multi-region environments, as well as migrations across regions.\u003c/p\u003e\n"],["\u003cp\u003eThe document series helps you with architectural decisions, such as distributing resources across Google Cloud regions and zones.\u003c/p\u003e\n"]]],[],null,["# Migrate across Google Cloud regions: Get started\n\nThis document series helps you prepare for migrating your workloads and data\nacross Google Cloud [regions](/docs/geography-and-regions#regions_and_zones). In this series, you learn how to design\nreliable, single-region environments, and how to set up security and compliance\ncontrols to help ensure that your workloads and data stay inside specific\nGoogle Cloud regions. This series also provides guidance on how to expand\nyour environment to multiple regions. This series is useful if you're planning\nto do any of these actions, or if you're evaluating the opportunity to do so in\nthe future and want to explore what it might look like.\n\nThis document is part of the following series:\n\n- Get started (this document)\n- [Design resilient single-region environments on Google Cloud](/architecture/migrate-across-regions/design-resilient-single-region-environments)\n- [Architect your workloads](/architecture/migrate-across-regions/architect-workloads)\n- [Prepare data and batch workloads for the migration](/architecture/migrate-across-regions/prepare-data-and-batch-workloads)\n\nThis series assumes that you have read and are familiar with\n[Migrate to Google Cloud: Get started](/architecture/migration-to-gcp-getting-started),\nwhich describes the general migration framework used in this series. This series\nis also part of a larger set of migration content. For an overview of all\nrelated migration content, see\n[Migration resources](/architecture/migrations).\n\nUse the following list to help you get started with the documents in this\nseries and with related migration content:\n\n- **Architecting your environments for reliability.** When designing your Google Cloud environments, there are several architectural choices to make, including how to distribute resources across Google Cloud regions and zones. For more information about how to design your Google Cloud environments, and about how to design reliable single-region environments, refer to [Design resilient single-region environments on Google Cloud](/architecture/migrate-across-regions/design-resilient-single-region-environments).\n- **Preparing for and migrating across Google Cloud regions**.\n Preparing for a migration across Google Cloud regions helps you avoid\n potential issues during such a migration, and also reduces the\n time and effort required to complete the migration. For example, you might\n want to prepare for a future migration to another region because you don't\n yet know if a particular region would be the best fit for your environment.\n Or you might prepare for a migration because you anticipate that your\n requirements about the preferred region might change in the future. You\n might even prepare for a migration because you're considering a migration\n to a soon-to-be-opened region.\n\n The guidance in this series is also useful if you didn't plan in advance for\n a migration across regions or for an expansion to multiple regions. In this\n case, you might need to spend additional effort to prepare your\n infrastructure, workloads, and data for the migration across regions and for\n the expansion to multiple regions.\n\n For more information about preparing for a migration across\n Google Cloud regions, see the following documents:\n - [Design resilient single-region environments](/architecture/migrate-across-regions/design-resilient-single-region-environments)\n - [Prepare data and batch workloads for migration across regions](/architecture/migrate-across-regions/prepare-data-and-batch-workloads)\n- **Setting up boundaries, and security and compliance controls to ensure\n that your workloads and data stay inside certain Google Cloud\n regions** . You might have to comply with security and regulatory\n requirements so that your workloads and data can only reside in specific\n Google Cloud regions. If you have this compliance requirement, you\n might need to implement boundaries, controls, and auditing to ensure\n locality, sovereignty, privacy, and confidentiality on top of the\n [guarantees that Google Cloud offers](/security).\n For example, you might need to make your environment compliant with\n regulations and security requirements that mandate certain workloads and\n data never leave a specific region residing in a particular political,\n administrative, or state entity.\n\n- **Minimizing the costs of your single- and multi-region environments,\n and of migrations across Google Cloud regions** . As your environments\n and your Google Cloud footprint grow, you might consider implementing\n mechanisms and processes to control and reduce the costs that are\n associated with your environments and your migrations across regions. For\n example, you can provision resources in specific regions, optimize network\n traffic patterns, streamline and automate processes, and automatically\n scale resources with demand. For more information about reducing costs,\n refer to\n [Migrate to Google Cloud: Minimize costs](/architecture/migration-to-google-cloud-minimize-costs).\n\nWhat's next\n-----------\n\n- Learn how to [design resilient single-region environments on Google Cloud](/architecture/migrate-across-regions/design-resilient-single-region-environments).\n- Learn how to [prepare data and batch workloads for the migration](/architecture/migrate-across-regions/prepare-data-and-batch-workloads).\n- Learn how to [minimize costs](/architecture/migration-to-google-cloud-minimize-costs) of your Google Cloud environment and your migration across regions.\n- Read [an in-depth analysis of deployment archetypes for cloud applications](/architecture/deployment-archetypes).\n- Learn about the migration framework by reading [Migrate to Google Cloud: Get started](/architecture/migration-to-gcp-getting-started).\n- Learn when to [find help for your migrations](/architecture/migration-to-gcp-getting-started#finding_help).\n- For more reference architectures, diagrams, and best practices, explore the [Cloud Architecture Center](/architecture).\n\nContributors\n------------\n\nAuthor: [Marco Ferrari](https://www.linkedin.com/in/ferrarimark) \\| Cloud Solutions Architect\n\nOther contributor: [Lee Gates](https://www.linkedin.com/in/gatesl) \\| Group Product Manager"]]
