Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Managed Service for Greenplum®
  • Getting started
    • All guides
      • Information about existing clusters
      • Creating a cluster
      • Updating cluster settings
      • Stopping and starting a cluster
        • Information about hosts
        • Expanding a cluster
        • Migrating hosts to a different availability zone
      • Managing backups
      • Deleting a cluster
    • Connecting to a database
    • Connecting to an external file server (gpfdist)
    • Auxiliary utilities
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  1. Step-by-step guides
  2. Clusters
  3. Managing cluster hosts
  4. Migrating hosts to a different availability zone

Migrating Greenplum® cluster hosts to a different availability zone

Written by
Yandex Cloud
Updated at October 29, 2024

All Managed Service for Greenplum® cluster hosts are located in the same Yandex Cloud availability zone. To move hosts from one availability zone to another, restore your cluster from a backup. During cluster recovery from a backup, specify a new availability zone.

Note

For clusters with hosts residing in the ru-central1-d availability zone, local SSD storage is not available if using the Intel Cascade Lake platform.

Specifics of migration in Yandex Data TransferSpecifics of migration in Yandex Data Transfer

If your cluster acts as an endpoint at data transfer using Data Transfer:

  1. Make sure the cluster hosts are located in the ru-central1-a or ru-central1-b availability zone; otherwise, the transfer will not operate correctly.

  2. If the transfer type is Replication or Snapshot and increment, restart the transfer after recovery from a backup. This way, it will get data about the cluster's new topology. You do not need to restart Snapshot transfers, as information about the new topology is provided automatically while activating them.

    To restart a transfer, choose one of the two methods:

    • Deactivate the transfer and wait for its status to change to Stopped. Next, reactivate the transfer and wait for its status to change to Replicating.
    • Update any setting for the transfer or endpoint.

For more information, see Migrating a Data Transfer transfer and endpoints to a different availability zone.

Was the article helpful?

Previous
Expanding a cluster
Next
Managing backups
© 2025 Direct Cursus Technology L.L.C.