How data transfers handle destination objects

By the time an iteration of a data transfer starts, the destination bucket may already contain objects. You can configure what Object Storage does with them:

Overwrite objects that have a newer pair in the source.

Apply the overwrite setting to unmanaged objects (objects in the destination that weren’t transferred at previous iterations).

Overwriting destination objects

The setting to overwrite destination objects, also known as the overwrite strategy in the developer tools, determines what happens when the source and destination both contain an object with the same key. Depending on the setting’s value, Object Storage overwrites the destination object with the source version or leaves it unchanged:

Overwrite if source is newer: Object Storage overwrites a destination object only if the source object has a newer timestamp (based on the Last-Modified header). This value is recommended for incremental synchronization.
Do not overwrite: Object Storage doesn’t overwrite existing destination objects. If an object with the same key already exists in the destination, this source object is skipped. This is the safest option to avoid accidental data loss.

You can configure overwriting objects when you create a data transfer (but not for existing transfers):

Web console
CLI
Terraform

In the web console, the setting appears under Overwriting destination objects.

Set .spec.overwrite_strategy to one of the following values:

IF_NEWER: Overwrite if source is newer
NEVER: Do not overwrite

For example:

{
  "spec": {
    "overwrite_strategy": "IF_NEWER"
  }
}

Set the overwrite_strategy argument to one of the following values in your resource block:

"IF_NEWER": Overwrite if source is newer
"NEVER": Do not overwrite

For example:

resource "nebius_storage_v1_transfer" "example" {
  overwrite_strategy = "IF_NEWER"
  # Other parameters
}

Unmanaged destination objects

Unmanaged objects are objects in the destination bucket that never had a matching object in the source (they were created in the destination only, or their keys never matched the source prefix). You can configure whether they are overwritten by source objects with the same keys:

Allow overwriting: Object Storage overwrites unmanaged destination objects. Use only when you are sure that the destination doesn’t contain any important data.
Do not overwrite (default): Object Storage doesn’t overwrite unmanaged destination objects. Only destination objects that previously had a pair in the source are affected. Protects objects that only exist in the destination.

For example, you use Overwrite if source is newer with Do not overwrite for unmanaged objects. The transfer updates only destination objects that correspond to source keys; any object in the destination that never had a source pair is left unchanged. You can configure overwriting objects when you create a data transfer (but not for existing transfers):

Web console
CLI
Terraform

In the web console, the setting for unmanaged objects appears under Destination → Unmanaged objects.

Set the .spec.touch_unmanaged field:

true: Allow overwriting unmanaged destination objects
false (default): Do not overwrite unmanaged destination objects

Example:

{
  "spec": {
    "touch_unmanaged": false
  }
}

Set the touch_unmanaged argument to one of the following values in your resource block:

true: Allow overwriting unmanaged destination objects
false (default): Do not overwrite unmanaged destination objects

Example:

resource "nebius_storage_v1_transfer" "example" {
  touch_unmanaged = false
  # Other parameters
}

Object Storage

Managed Service for PostgreSQL®

Container Registry

How data transfers handle destination objects

Overwriting destination objects

Unmanaged destination objects

Object Storage

Managed Service for PostgreSQL®

Container Registry

Documentation Index

​Overwriting destination objects

​Unmanaged destination objects

Overwriting destination objects

Unmanaged destination objects