ytclone

Copy static tables, files, YSON documents, and directories between YTsaurus and S3, preserving schemas and portable attributes. Repeat a command to skip completed, unchanged nodes and retry unfinished copies.

Restoring from S3 requires an archive created by ytclone.

Installation

Install from PyPI in your Python virtual environment:

pip install ytclone

Requires CPython 3.10+ on Linux x86_64 with glibc or macOS ARM64 (Apple Silicon). Other platforms are currently unsupported because the required ytsaurus-yson dependency has no wheels for them.

Standalone archives include both commands and need no installed Python or Docker. See standalone downloads for Linux x86_64 and macOS ARM64.

Docker images include both commands and use the same version numbers as PyPI. See running with Docker for commands (linux/amd64 only).

Quick start

Configure access to YTsaurus and S3:

export YT_PROXY="https://yt.example.com"
export YT_TOKEN="..."
export AWS_ACCESS_KEY_ID="..."
export AWS_SECRET_ACCESS_KEY="..."
export AWS_DEFAULT_REGION="us-east-1"

The S3 bucket must already exist. For an S3-compatible service, also set S3_ENDPOINT to its URL. Use AWS_SESSION_TOKEN for temporary credentials.

Copy to S3:

ytclone //home/analytics/events s3://my-bucket/export --log-file export.log

The full YT path is appended to the S3 prefix: this command stores events at s3://my-bucket/export/home/analytics/events/.

Restore to YTsaurus:

ytclone s3://my-bucket/export/home/analytics/events \
  //home/analytics/events_copy --log-file restore.log

The restore destination is used exactly as given: the children of events go directly under //home/analytics/events_copy. The same commands work for a single table, file, or document. With --log-file, progress appears on the console and detailed logs are appended to the file.

Repeated runs

Run the same command again after an interruption or a source update. Completed, unchanged nodes are skipped. New, changed, or incomplete nodes are copied again; an interrupted table, file, or document starts from the beginning, not from its last part.

Source data is never deleted. Destination nodes absent from the source are kept. Use a separate S3 prefix for each source cluster.

Parallel export

For trees with many tables or files, use multiple copy processes:

ytclone-parallel //home/analytics/events s3://my-bucket/export \
  --processes 2 --concurrency 2 --log-file export.log

This runs two processes with two transfers each, prioritizing directories and small nodes. One table still occupies one transfer slot. Parallel mode supports YT → S3; restore its archives with ytclone as above.

Before you copy

• Supported node types: static tables, files, YSON documents, and directories. Dynamic tables are skipped and reported; links are unsupported.
• One current S3 copy. There is no archive version history. Replacing a node makes its archive unavailable until completion; a failed replacement can lose the previous complete copy.
• Permissions are not copied. ACLs, ownership, and account settings are excluded. Replacing an existing YT table, file, or document recreates the node, so its previous settings are not preserved either.
• Consistency is per node. A directory tree is not a single point-in-time snapshot.
• Avoid overlapping writers. Do not run commands that write to the same destination nodes concurrently, or restore an archive while it is being replaced.

Documentation

Run ytclone --help or ytclone-parallel --help for all command-line options.

• User guide: paths, configuration, progress, retries, and parallel export.
• Architecture: archive format, change detection, and execution diagrams.
• Contributing: installation from source, development, and tests.

License

MIT.