[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2022-06-20 (世界標準時間)。"],[],[],null,["*** ** * ** ***\n\nWhen you create a Cloud Storage bucket, you choose its permanent\ngeographic location. As your business needs change, where you store your data\nmight need to change too. For example, your data might be better situated in a\nhighly available dual-region bucket, a lower cost regional bucket, or simply a\ndifferent region of the world.\n\nThis tutorial helps you to select a [location](/storage/docs/locations)\nthat best fits your needs.\n\nObjectives\n\n- Choose a new location for the Cloud Storage data.\n\nCosts\n\n\nIn this document, you use the following billable components of Google Cloud:\n\n\n- [Cloud Storage](/storage/pricing)\n\n\u003cbr /\u003e\n\n\nTo generate a cost estimate based on your projected usage,\nuse the [pricing calculator](/products/calculator). \nNew Google Cloud users might be eligible for a [free trial](/free). \n\n\u003cbr /\u003e\n\nBefore you begin\n\nThere are no prerequisites to this tutorial. \n\nChoose a new location\n\nWhen you choose the location for a Cloud Storage bucket, consider the\ndifferences in availability, and price, as shown in the following\ntable.\n\n| | Region | Dual-region | Multi-region |\n| [Availability](/storage/docs/availability-durability) | - Data redundancy across availability zones (synchronous) - RTO(recovery time objective)=0: automated failover and failback on zonal failure (no need to change storage paths) | - Higher availability than regions for a given storage class - Data redundancy across regions (asynchronous) - [Turbo replication](/storage/docs/availability-durability#turbo-replication) option for replication within 15 minutes - RTO(recovery time objective)=0: automated failover and failback on regional failure (no need to change storage paths) | - Higher availability than regions for a given storage class - Data redundancy across regions (asynchronous) - RTO(recovery time objective)=0: automated failover and failback on regional failure (no need to change storage paths) |\n| [Pricing](/storage/pricing#storage-pricing) | - Lowest storage price - No replication charges - No outbound data transfer charges when reading data inside the same region | - Highest storage price - Replication charges apply on write - No outbound data transfer charges when reading data within either region | - Higher storage price than regions, but lower than dual-regions - Replication charges apply on write - Outbound data transfer charges always apply when reading data |\n|-------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n\nLocation recommendations\n\n| Requirements | Recommended bucket location | Workload examples |\n|------------------------------------------------------------------------------------------------------------------------------------|-----------------------------|------------------------------------------------------|\n| - Optimized latency and bandwidth - Lowest data storage cost - Cross-zone redundancy | Region^[1](#fn1)^ | - Analytics - Backup and archive |\n| - Optimized latency and bandwidth - Cross-region redundancy, with precise control of the locations where copies of data are stored | Dual-region^[2](#fn2)^ | - Analytics - Backup and archive - Disaster recovery |\n| - Cross-geography data access - Cross-region redundancy | Multi-region | - Content serving |\n\n1. For more information about region-specific considerations, see [Geography and regions](/docs/geography-and-regions#regions_and_zones).\n2. If you need a short and predictable [recovery point objective (RPO)](/architecture/dr-scenarios-planning-guide#basics_of_dr_planning), enable the premium [turbo replication](/storage/docs/availability-durability#turbo-replication) feature.\n\n- To maximize performance and lower your total cost of ownership, colocate your data and compute in the same region(s). Regions and dual-regions are both suitable for this purpose.\n- To avoid data replication charges, store short-lived datasets in regions.\n- For moderate performance and ad hoc analytics workloads, multi-region storage\n can be a cost-effective choice.\n\n Note that the performance of workloads that use data in a multi-region bucket\n might vary over time because storage and compute aren't colocated. When a\n multi-region workload has strict performance requirements, consider enabling\n [Anywhere Cache](/storage/docs/anywhere-cache).\n- When transferring to a new bucket, consider if the current\n [storage class](/storage/docs/storage-classes) still\n suits your needs.\n\nPlan and start the transfer\n\nAfter you've decided on a new location, see\n[Transfer between Cloud Storage buckets](/storage-transfer/docs/cloud-storage-to-cloud-storage)\nto plan and perform your data move."]]
