A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://cloud.google.com/compute/docs/disks/async-pd/configure below:

Configure Persistent Disk Asynchronous Replication | Compute Engine Documentation

Skip to main content Configure Persistent Disk Asynchronous Replication

Stay organized with collections Save and categorize content based on your preferences.

This document describes how to configure Asynchronous Replication. Asynchronous Replication is useful for low-RPO, low-RTO disaster recovery.

To to enable asynchronous disk replication, complete the following steps:

  1. Set up a disk replication pair to configure Asynchronous Replication.
  2. Manually start replication to begin replicating data between the primary and secondary disk.
Limitations Before you begin Set up a disk replication pair

Before you can replicate data between disks, you need to configure replication by completing the following tasks:

  1. Choose a region pair and your primary and secondary regions.
  2. Optional: If you need to coordinate replication across a group of disks, create a consistency group in the primary region. You must add primary disks to a consistency group before you start replication.
  3. Create or select the primary disks. You can optionally add these disks to the consistency group.
  4. Create new, blank secondary disks.
Disk requirements

Disks must meet the following requirements to be used as primary or secondary disks for Asynchronous Replication:

Create or select a primary disk

The primary disk is the boot or data disk that is attached to the VM where the workload runs. You can use any pre-existing disk that meets the disk requirements as a primary disk, or you can create a new disk. If you want to use an existing disk as a primary disk, you don't need to perform any additional configuration on the disk. Proceed to create a secondary disk to complete Asynchronous Replication configuration.

Create a primary disk

Create a primary disk using the methods described in one of the following documents.

Create a secondary disk

The secondary disk is a data disk in a separate region from the primary disk, that receives and writes replicated data from the primary disk. When configuring Asynchronous Replication, you must create a new, blank secondary disk that references the primary disk.

To create a secondary disk with the same properties as the primary disk, follow the steps in Create a secondary disk identical to the primary disk.

Note: Compute Engine copies the properties from the primary disk to the secondary disk only once, when the secondary disk is created. If you modify the primary disk's label, guest OS features, or other properties after the secondary disk is created, then Compute Engine doesn't replicate those changes to the secondary disk.

To create a secondary disk that differs from the primary disk, see Create a custom secondary disk.

Create a secondary disk identical to the primary disk

This section describes how to create a secondary disk identical to the primary disk.

Console Note: When you create a secondary disk using the Google Cloud console, replication starts immediately. If you want to add the secondary disk's corresponding primary disk to a consistency group, you must do so before you create the secondary disk.

Create a secondary disk and start replication by doing the following:

  1. In the Google Cloud console, go to the Disks page.

    Go to Disks

  2. Click the name of the primary disk. The Manage disk page opens.

  3. Click Create secondary disk.

  4. In the Name field, enter a name for the disk.

  5. In the Location section, do one of the following:

  6. Click Create. Compute Engine creates the disk and starts replication.

gcloud

Create a secondary disk using the gcloud compute disks create command:

gcloud compute disks create SECONDARY_DISK_NAME \
    --SECONDARY_LOCATION_FLAG=SECONDARY_LOCATION \
    --size=SIZE \
    --primary-disk=PRIMARY_DISK_NAME \
    --PRIMARY_DISK_LOCATION_FLAG=PRIMARY_LOCATION \
    --primary-disk-project=PRIMARY_DISK_PROJECT

To create a regional secondary disk, additionally specify the --replica-zones flag:

--replica-zones=ZONE_1,ZONE_2

Replace the following:

Go

Create a zonal or regional secondary disk using one of the following code samples:

Create a zonal secondary disk Create a regional secondary disk Java

Create a zonal or regional secondary disk using one of the following code samples:

Create a zonal secondary disk Create a regional secondary disk Node.js

Create a zonal or regional secondary disk using one of the following code samples:

Create a zonal secondary disk Create a regional secondary disk Python

Create a zonal or regional secondary disk using one of the following code samples:

Create a zonal secondary disk Create a regional secondary disk REST

Create a zonal or regional secondary disk using one of the following methods:

Replace the following:

Note: You can't create a secondary disk from a snapshot, image or disk. Don't add the sourceSnapshot, sourceImage, or sourceDisk fields to your request. Terraform

To create a secondary disk identical to the primary disk, use the compute_disk resource.

To learn how to apply or remove a Terraform configuration, see Basic Terraform commands.

Create a custom secondary disk

This section discusses how to create a custom secondary disk, that is, a secondary disk whose properties differ from the primary disk.

If the primary disk is a boot disk, you can't change or remove any of the primary disk's guest OS features. You can only add more guest OS features. For more information, see Secondary disk customization.

You can create a custom secondary disk with the gcloud CLI, REST, or Terraform. You can't customize the secondary disk from the Google Cloud console.

gcloud

To create a custom secondary disk, use the gcloud compute disks create command as described in Create a secondary disk identical to the primary disk. Use additional flags to customize the secondary disk's properties.

The following are examples of how to customize the secondary disk:

Go Java Node.js Python REST

To create a custom secondary disk, use the same method described in Create a secondary disk identical to the primary disk. Specify additional fields to customize the secondary disk's properties.

The following are examples of how to customize the secondary disk:

Terraform

To create a custom secondary disk, use the same method described in Create a secondary disk identical to the primary disk. You can specify additional fields to customize the secondary disk's properties.

The following are examples of how to customize the secondary disk:

Start replication

After you create a primary and secondary disk, you must start replication to begin replicating data from the primary disk to the secondary disk.

What's next

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-08-07 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["PD Async Replication enables low-RPO, low-RTO disaster recovery by asynchronously replicating data between a primary and a secondary disk."],["To configure PD Async Replication, you must set up a disk replication pair and choose a supported region pair for the primary and secondary disks."],["Secondary disks must be created blank, as they cannot be derived from images, snapshots, or existing disks, and are subject to specific disk requirements."],["Once primary and secondary disks are created, you must manually start replication to initiate data transfer from the primary to the secondary disk."],["Disks can be organized into consistency groups for coordinated replication, and there are options to customize secondary disks with additional features and labels beyond what the primary disk has."]]],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4