Yandex Cloud
Documentation
PresentationContact UsTry it for free
© 2026 Direct Cursus Technology L.L.C.
Yandex Data Transfer
  • Available transfers
  • Getting started
    • Resource relationships
    • Transfer types and lifecycles
    • What objects can be transferred
    • Regular incremental copy
    • Parallel copy
    • Data transformation
    • Serialization
    • Yandex Data Transfer workflow for sources and targets
    • Delivery guarantees
    • Operations on transfers
    • Networking in Yandex Data Transfer
    • Speed for copying data in Yandex Data Transfer
    • Change data capture
    • Use cases
    • Quotas and limits
  • Troubleshooting
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials

In this article:

  • Operations initiated by users
  • Operations initiated by a transfer
  • Operations initiated by administrators
  1. Concepts
  2. Operations on transfers

Operations on transfers

Written by
Yandex Cloud
Updated at October 16, 2026
View in Markdown
  • Operations initiated by users
  • Operations initiated by a transfer
  • Operations initiated by administrators

An operation is an action performed on a transfer that can be initiated by:

  • Users, e.g., when activating or deactivating a transfer.
  • Transfer itself, e.g., in the event of an error in the transfer.
  • Yandex Cloud administrators, e.g., when upgrading the transfer version.

The history of transfer operations is available on the operations page.

Operations initiated by usersOperations initiated by users

  • Activate: Activates the transfer. Activation is required for each new transfer, except for an INCREMENT_ONLY or SNAPSHOT_AND_INCREMENT transfer created using Terraform.

    Upon activation, the system provisions resources for the transfer. The actions depend on the transfer type:

    • Snapshot: Initiates a full data copy.
    • Replication: Starts replication of changes without prior copying.
    • Snapshot and increment: Creates a replication slot, makes a full data copy, and runs replication of changes.

    For transfers with periodic copying, each run triggers either full data copy or incremental copy, if this mode is configured for tables.

  • Deactivate: Deactivates the transfer.

    During transfer deactivation, the system cleans up run artifacts. For example:

    • For Snapshot and increment transfers, disables the replication slot on the source.

    • Deletes temporary data transfer logs.

    • Synchronizes the target:

      • Transfers the source data schema objects for the final deactivation stage.
      • Creates indexes.
  • UpdateTransfer when editing the settings of the transfer in the Replicating status.

Operations initiated by a transferOperations initiated by a transfer

  • Termination if a fatal error occurs during the transfer that terminates it (for example, when deleting a replication slot if data is delivered from PostgreSQL).
  • CleanupResource to delete external resources created by the transfer. Takes place if the transfer shuts down due to an error or deactivation.

Operations initiated by administratorsOperations initiated by administrators

  • Update version when a new Data Transfer version is released or the transfer version is updated.

Was the article helpful?

Previous
Delivery guarantees
Next
Networking in Yandex Data Transfer
© 2026 Direct Cursus Technology L.L.C.