diff --git a/docs/user-guide/deployments-administration/disaster-recovery/back-up-&-restore-data.md b/docs/user-guide/deployments-administration/disaster-recovery/back-up-&-restore-data.md
index f0fbf7709..6e3ff5659 100644
--- a/docs/user-guide/deployments-administration/disaster-recovery/back-up-&-restore-data.md
+++ b/docs/user-guide/deployments-administration/disaster-recovery/back-up-&-restore-data.md
@@ -7,6 +7,8 @@ description: Describes how to use GreptimeDB's Export and Import tools for datab
 
 This guide describes how to use GreptimeDB's Export and Import tools for database data backup and restoration operations. 
 
+For the resumable snapshot-based Export/Import V2 workflow, see [Export and Import Data with Export/Import V2](./export-import-v2.md).
+
 For detailed command-line options and advanced configurations, please refer to [Data Export & Import](/reference/command-lines/utilities/data.md).
 
 ## Overview
diff --git a/docs/user-guide/deployments-administration/disaster-recovery/export-import-v2.md b/docs/user-guide/deployments-administration/disaster-recovery/export-import-v2.md
new file mode 100644
index 000000000..115f99f46
--- /dev/null
+++ b/docs/user-guide/deployments-administration/disaster-recovery/export-import-v2.md
@@ -0,0 +1,389 @@
+---
+keywords: [GreptimeDB, export-v2, import-v2, backup, restore, snapshot, migration, S3, MinIO]
+description: Describes how to export, verify, manage, and import GreptimeDB snapshots with the export-v2 and import-v2 CLI commands.
+---
+
+# Export and Import Data with Export/Import V2
+
+Export/Import V2 creates portable snapshots of GreptimeDB data. Use it to back up data, restore data, or migrate data between GreptimeDB instances.
+
+A V2 snapshot contains schema metadata, a manifest, and data files. Data files are split into chunks so interrupted export and import jobs can resume from the previous progress.
+
+This guide uses the following commands:
+
+- `greptime cli data export-v2 create` to create a snapshot
+- `greptime cli data export-v2 verify` to verify a snapshot
+- `greptime cli data export-v2 list` to list snapshots under a parent location
+- `greptime cli data export-v2 delete` to delete a snapshot
+- `greptime cli data import-v2` to import from a snapshot
+
+## Prerequisites
+
+Before using Export/Import V2, make sure that:
+
+- The GreptimeDB HTTP endpoint is reachable, for example `127.0.0.1:4000`.
+- You have a `greptime` binary that includes the `cli data export-v2` and `cli data import-v2` commands.
+- The snapshot storage location is readable and writable by both the CLI client and the GreptimeDB server.
+
+For remote object storage, explicitly enable one supported backend and provide the backend options. Export/Import V2 supports S3-compatible storage, Alibaba Cloud OSS, Google Cloud Storage, and Azure Blob Storage. For example, use `--s3` with `--s3-bucket` and `--s3-region` for S3-compatible storage.
+
+For `file://` snapshots, the path must be accessible from the GreptimeDB server as well as the CLI client. This usually means running the CLI on the same host as a standalone server, or mounting the same filesystem path into the GreptimeDB server. For remote, Kubernetes, or distributed deployments, use object storage such as S3 or MinIO instead of a local `file://` path.
+
+:::note
+
+The snapshot URI, such as `s3://my-bucket/snapshots/prod`, identifies the snapshot location. The object store options, such as `--s3-bucket my-bucket`, configure how the CLI connects to the backend. Keep them consistent across create, verify, import, list, and delete commands.
+
+:::
+
+## Quick start with local filesystem
+
+Use a local filesystem snapshot only when the path is shared by the CLI client and the GreptimeDB server. For example, this works for a local standalone server when the CLI runs on the same host.
+
+Create a snapshot:
+
+```bash
+greptime cli data export-v2 create \
+  --addr 127.0.0.1:4000 \
+  --to file:///tmp/greptime-snapshots/demo
+```
+
+Verify the snapshot before restoring it:
+
+```bash
+greptime cli data export-v2 verify \
+  --snapshot file:///tmp/greptime-snapshots/demo
+```
+
+Import from the snapshot:
+
+```bash
+greptime cli data import-v2 \
+  --addr 127.0.0.1:4000 \
+  --from file:///tmp/greptime-snapshots/demo
+```
+
+By default, export and import use the `greptime` catalog. Add `--catalog <catalog>` if you need another catalog.
+
+## Export to remote object storage
+
+Export/Import V2 can store snapshots in AWS S3, S3-compatible services such as MinIO, Alibaba Cloud OSS, Google Cloud Storage, and Azure Blob Storage. The examples below use the S3 backend because S3 and MinIO are common choices. For other object stores, use the corresponding backend flag and options described in [Supported storage backends](#supported-storage-backends).
+
+### S3 or MinIO
+
+Use the S3 backend for AWS S3 and S3-compatible services such as MinIO.
+
+### S3-compatible endpoint
+
+For MinIO, pass `--s3-endpoint`:
+
+```bash
+greptime cli data export-v2 create \
+  --addr 127.0.0.1:4000 \
+  --to s3://greptime/snapshots/local-test \
+  --s3 \
+  --s3-bucket greptime \
+  --s3-region us-west-2 \
+  --s3-access-key-id superpower_ci_user \
+  --s3-secret-access-key superpower_password \
+  --s3-endpoint http://127.0.0.1:9000
+```
+
+Use the same storage options when verifying, importing, listing, or deleting the snapshot:
+
+```bash
+greptime cli data export-v2 verify \
+  --snapshot s3://greptime/snapshots/local-test \
+  --s3 \
+  --s3-bucket greptime \
+  --s3-region us-west-2 \
+  --s3-access-key-id superpower_ci_user \
+  --s3-secret-access-key superpower_password \
+  --s3-endpoint http://127.0.0.1:9000
+```
+
+```bash
+greptime cli data import-v2 \
+  --addr 127.0.0.1:4000 \
+  --from s3://greptime/snapshots/local-test \
+  --s3 \
+  --s3-bucket greptime \
+  --s3-region us-west-2 \
+  --s3-access-key-id superpower_ci_user \
+  --s3-secret-access-key superpower_password \
+  --s3-endpoint http://127.0.0.1:9000
+```
+
+For AWS S3, use the same `--s3` options but omit `--s3-endpoint` unless you use a custom endpoint. If your environment uses instance profiles or another credential provider, explicit access keys may not be required. The S3 backend still requires `--s3`, `--s3-bucket`, and `--s3-region`.
+
+## Export selected schemas
+
+Export only selected schemas with `--schemas`. You can pass a comma-separated list:
+
+```bash
+greptime cli data export-v2 create \
+  --addr 127.0.0.1:4000 \
+  --to file:///tmp/greptime-snapshots/observability \
+  --schemas public,metrics
+```
+
+Or pass the option multiple times:
+
+```bash
+greptime cli data export-v2 create \
+  --addr 127.0.0.1:4000 \
+  --to file:///tmp/greptime-snapshots/observability \
+  --schemas public \
+  --schemas metrics
+```
+
+When importing, `--schemas` selects a subset from the snapshot:
+
+```bash
+greptime cli data import-v2 \
+  --addr 127.0.0.1:4000 \
+  --from file:///tmp/greptime-snapshots/observability \
+  --schemas public
+```
+
+If you request a schema that is not in the snapshot, the import fails.
+
+## Export schema only
+
+Use `--schema-only` to export table definitions without data:
+
+```bash
+greptime cli data export-v2 create \
+  --addr 127.0.0.1:4000 \
+  --to file:///tmp/greptime-snapshots/schema-only \
+  --schema-only
+```
+
+Importing a schema-only snapshot restores the schema but does not import data chunks:
+
+```bash
+greptime cli data import-v2 \
+  --addr 127.0.0.1:4000 \
+  --from file:///tmp/greptime-snapshots/schema-only
+```
+
+## Export by time range and chunk window
+
+Use a bounded time range and a chunk window for large datasets. Export/Import V2 creates one or more data chunks for each schema in the range.
+
+```bash
+greptime cli data export-v2 create \
+  --addr 127.0.0.1:4000 \
+  --to s3://greptime/snapshots/prod-2026-06 \
+  --start-time 2026-06-01T00:00:00Z \
+  --end-time 2026-07-01T00:00:00Z \
+  --chunk-time-window 1d \
+  --s3 \
+  --s3-bucket greptime \
+  --s3-region us-west-2 \
+  --s3-access-key-id superpower_ci_user \
+  --s3-secret-access-key superpower_password \
+  --s3-endpoint http://127.0.0.1:9000
+```
+
+`--chunk-time-window` requires both `--start-time` and `--end-time`.
+
+Chunks are created by time window. For example, a 15-minute range with `--chunk-time-window 5m` creates 3 chunks. During import, data tasks are scheduled per chunk and per schema. If the snapshot contains 3 chunks and 2 schemas with data, import schedules 6 data tasks.
+
+Snapshot data files are also organized by schema and chunk. For example, a multi-chunk snapshot can contain paths such as:
+
+```text
+data/logs/1/app_logs.parquet
+data/logs/2/app_logs.parquet
+data/logs/3/app_logs.parquet
+data/public/1/host_metrics.parquet
+data/public/2/host_metrics.parquet
+data/public/3/host_metrics.parquet
+```
+
+Choose the chunk window based on the data volume and density:
+
+- Use a larger window for small or sparse datasets to avoid too many small chunks.
+- Use a smaller window for large datasets to keep each chunk manageable.
+- Start with `1d` and adjust after checking export duration and chunk sizes.
+
+## Tune parallelism
+
+Export has two parallelism options:
+
+- `--parallelism` controls server-side `COPY DATABASE` parallelism per schema per chunk. The default is `1`.
+- `--chunk-parallelism` controls how many export chunks the client runs concurrently. The default is `1` and the valid range is `1..=64`.
+
+Import uses:
+
+- `--task-parallelism` to control how many import data tasks the client runs concurrently. The default is `1` and the valid range is `1..=64`.
+
+Increase these values gradually and monitor GreptimeDB, object storage, and network resource usage.
+
+## Resume an interrupted export or import
+
+Export/Import V2 is designed to resume interrupted work.
+
+For export:
+
+- If the target snapshot does not exist, `export-v2 create` creates it.
+- If the target snapshot already exists, the same command resumes from existing progress.
+- Completed chunks are skipped. Failed or pending chunks are retried.
+- Use `--force` only when you want to delete the existing snapshot and recreate it.
+
+```bash
+greptime cli data export-v2 create \
+  --addr 127.0.0.1:4000 \
+  --to file:///tmp/greptime-snapshots/demo
+```
+
+Run the same command again to resume after interruption.
+
+For import, progress is stored in a state file while the import is running. By default, the state file is under `~/.greptime/import_state`. Override it with `--state-path` when you want an explicit state location:
+
+```bash
+greptime cli data import-v2 \
+  --addr 127.0.0.1:4000 \
+  --from file:///tmp/greptime-snapshots/demo \
+  --state-path /tmp/greptime-import-demo.state
+```
+
+`--dry-run` does not create an import state file. A real import keeps the state file if it fails or is interrupted, so the next run can resume completed data tasks. After a successful import, import-v2 automatically deletes the state file because there is no remaining work to resume. A `.lock` file with the same prefix can remain; it is a lock file, not the import state content.
+
+If you intentionally want to rerun an import from scratch after a failed or interrupted run, use a different `--state-path` or remove the previous state file after confirming that doing so is safe.
+
+## Dry-run an import
+
+Use `--dry-run` to validate the snapshot and import plan without executing DDL or importing data:
+
+```bash
+greptime cli data import-v2 \
+  --addr 127.0.0.1:4000 \
+  --from file:///tmp/greptime-snapshots/demo \
+  --dry-run
+```
+
+Dry-run is useful before a production migration or restore.
+
+## Verify, list, and delete snapshots
+
+Verify a snapshot:
+
+```bash
+greptime cli data export-v2 verify \
+  --snapshot file:///tmp/greptime-snapshots/demo
+```
+
+List snapshots under a parent location:
+
+```bash
+greptime cli data export-v2 list \
+  --location file:///tmp/greptime-snapshots
+```
+
+Delete a snapshot:
+
+```bash
+greptime cli data export-v2 delete \
+  --snapshot file:///tmp/greptime-snapshots/demo
+```
+
+For non-interactive deletion, pass `--no-confirm`:
+
+```bash
+greptime cli data export-v2 delete \
+  --snapshot s3://greptime/snapshots/local-test \
+  --no-confirm \
+  --s3 \
+  --s3-bucket greptime \
+  --s3-region us-west-2 \
+  --s3-access-key-id superpower_ci_user \
+  --s3-secret-access-key superpower_password \
+  --s3-endpoint http://127.0.0.1:9000
+```
+
+## Authentication, timeout, proxy, and progress
+
+If the GreptimeDB instance has basic authentication enabled, pass credentials with `--auth-basic <username>:<password>`.
+
+Set request timeout with `--timeout`, for example `--timeout 60s` or `--timeout 5m`.
+
+For commands that connect to the GreptimeDB HTTP endpoint, such as `export-v2 create` and `import-v2`, use `--proxy` to set an HTTP proxy, or `--no-proxy` to disable proxy usage:
+
+```bash
+greptime cli data import-v2 \
+  --addr 127.0.0.1:4000 \
+  --from file:///tmp/greptime-snapshots/demo \
+  --no-proxy
+```
+
+Long-running create and import commands support `--progress` to control progress output:
+
+- `auto`: show an interactive bar on a TTY, otherwise log progress. This is the default.
+- `always`: always emit progress; it uses a bar on a TTY and lightweight logs otherwise.
+- `never`: never emit progress.
+
+## Supported storage backends
+
+Export/Import V2 supports local filesystem snapshots and remote object storage snapshots.
+
+For remote object storage, enable exactly one backend:
+
+- `--s3` for AWS S3 or S3-compatible storage such as MinIO
+- `--oss` for Alibaba Cloud OSS
+- `--gcs` for Google Cloud Storage
+- `--azblob` for Azure Blob Storage
+
+Common S3 options are:
+
+| Option | Description |
+| --- | --- |
+| `--s3-bucket` | S3 bucket name. Required for S3. |
+| `--s3-region` | S3 region. Required for S3. |
+| `--s3-access-key-id` | Access key ID. Optional when the environment provides credentials. |
+| `--s3-secret-access-key` | Secret access key. Optional when the environment provides credentials. |
+| `--s3-endpoint` | Custom S3-compatible endpoint, such as a MinIO endpoint. |
+| `--s3-enable-virtual-host-style` | Enable virtual-hosted-style requests. |
+| `--s3-disable-ec2-metadata` | Disable EC2 metadata service credential lookup. |
+
+## Troubleshooting
+
+### Failed to connect to `/v1/sql`
+
+Check that GreptimeDB is running and that `--addr` points to the HTTP endpoint:
+
+```bash
+curl http://127.0.0.1:4000/health
+```
+
+### `--chunk-time-window` fails validation
+
+`--chunk-time-window` requires both `--start-time` and `--end-time`. Add a bounded time range or remove `--chunk-time-window`.
+
+### S3 or MinIO reports `NoSuchBucket` or `NoSuchKey`
+
+Check that:
+
+- The bucket in the snapshot URI matches `--s3-bucket`.
+- `--s3-endpoint` is set for MinIO or other S3-compatible services.
+- The credentials can read and write the snapshot location.
+- You pass the same storage options to create, verify, import, list, and delete commands.
+
+### Import skips data unexpectedly
+
+Import resumes from its state file. If a previous import marked tasks as completed, a later run with the same state identity may skip them. Use an explicit `--state-path` for each restore operation, or remove the old state file after confirming it is safe.
+
+### A requested schema is not found
+
+When using `--schemas` during import, make sure the schema exists in the snapshot. Use `export-v2 verify` first and check the snapshot contents.
+
+### Verification fails
+
+Do not import a snapshot that fails verification. The snapshot may be incomplete or corrupted. Re-run the export with the same command to resume missing chunks, or recreate the snapshot with `--force` if you intentionally want to discard the existing snapshot.
+
+## Limitations
+
+- Export/Import V2 snapshots are not the same format as the legacy export/import output.
+- Schema filtering is schema-level. Table-level filtering is not covered by this command.
+- Time-range chunking is designed for time-series data. Sparse data may need a larger chunk window.
+- Schema-only snapshots do not contain data files.
+- Large migrations require careful tuning of chunk window, parallelism, object storage throughput, and GreptimeDB resources.
diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments-administration/disaster-recovery/export-import-v2.md b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments-administration/disaster-recovery/export-import-v2.md
new file mode 100644
index 000000000..08cf806f8
--- /dev/null
+++ b/i18n/zh/docusaurus-plugin-content-docs/current/user-guide/deployments-administration/disaster-recovery/export-import-v2.md
@@ -0,0 +1,389 @@
+---
+keywords: [GreptimeDB, export-v2, import-v2, 备份, 恢复, 快照, 迁移, S3, MinIO]
+description: 介绍如何使用 export-v2 和 import-v2 CLI 命令导出、验证、管理和导入 GreptimeDB 快照。
+---
+
+# 使用 Export/Import V2 导出和导入数据
+
+Export/Import V2 会创建可移植的 GreptimeDB 数据快照。你可以使用它备份数据、恢复数据，或在 GreptimeDB 实例之间迁移数据。
+
+V2 快照包含 schema 元数据、manifest 和数据文件。数据文件会被拆分为 chunks，因此中断的导出和导入任务可以从之前的进度继续执行。
+
+本指南使用以下命令：
+
+- `greptime cli data export-v2 create`：创建快照
+- `greptime cli data export-v2 verify`：验证快照
+- `greptime cli data export-v2 list`：列出父路径下的快照
+- `greptime cli data export-v2 delete`：删除快照
+- `greptime cli data import-v2`：从快照导入数据
+
+## 前置条件
+
+使用 Export/Import V2 之前，请确认：
+
+- GreptimeDB HTTP endpoint 可访问，例如 `127.0.0.1:4000`。
+- 你的 `greptime` binary 包含 `cli data export-v2` 和 `cli data import-v2` 命令。
+- CLI client 和 GreptimeDB server 都能读写快照存储位置。
+
+对于远程对象存储，仅有快照 URI 还不够。你还需要显式启用一个受支持的存储后端，并传入该后端的连接选项。Export/Import V2 支持 S3-compatible 存储、阿里云 OSS、Google Cloud Storage 和 Azure Blob Storage。例如，对于 S3-compatible 存储，需要同时使用 `--s3`、`--s3-bucket` 和 `--s3-region`。
+
+对于 `file://` 快照，路径必须同时能被 GreptimeDB server 和 CLI client 访问。通常这意味着 CLI 与 standalone server 运行在同一台主机上，或者将同一个文件系统路径挂载到 GreptimeDB server 中。对于远程、Kubernetes 或分布式部署，请使用 S3 或 MinIO 等对象存储，而不是本地 `file://` 路径。
+
+:::note
+
+快照 URI（例如 `s3://my-bucket/snapshots/prod`）标识快照位置。对象存储选项（例如 `--s3-bucket my-bucket`）配置 CLI 如何连接到对应后端。请在 create、verify、import、list 和 delete 命令中保持这些选项一致。
+
+:::
+
+## 使用本地文件系统快速开始
+
+只有在 CLI client 和 GreptimeDB server 共享同一路径时，才应使用本地文件系统快照。例如，对于本地 standalone server，如果 CLI 在同一台主机上运行，这种方式可以工作。
+
+创建快照：
+
+```bash
+greptime cli data export-v2 create \
+  --addr 127.0.0.1:4000 \
+  --to file:///tmp/greptime-snapshots/demo
+```
+
+恢复之前先验证快照：
+
+```bash
+greptime cli data export-v2 verify \
+  --snapshot file:///tmp/greptime-snapshots/demo
+```
+
+从快照导入：
+
+```bash
+greptime cli data import-v2 \
+  --addr 127.0.0.1:4000 \
+  --from file:///tmp/greptime-snapshots/demo
+```
+
+默认情况下，导出和导入使用 `greptime` catalog。如果需要使用其他 catalog，请添加 `--catalog <catalog>`。
+
+## 导出到远程对象存储
+
+Export/Import V2 可以将快照存储到 AWS S3、MinIO 等 S3-compatible 服务、阿里云 OSS、Google Cloud Storage 和 Azure Blob Storage。下面的示例使用 S3 backend，因为 S3 和 MinIO 是常见选择。对于其他对象存储，请使用 [支持的存储后端](#支持的存储后端) 中对应的 backend flag 和选项。
+
+### S3 或 MinIO
+
+对于 AWS S3 以及 MinIO 等 S3-compatible 服务，请使用 S3 backend。
+
+### S3-compatible endpoint
+
+对于 MinIO，请传入 `--s3-endpoint`：
+
+```bash
+greptime cli data export-v2 create \
+  --addr 127.0.0.1:4000 \
+  --to s3://greptime/snapshots/local-test \
+  --s3 \
+  --s3-bucket greptime \
+  --s3-region us-west-2 \
+  --s3-access-key-id superpower_ci_user \
+  --s3-secret-access-key superpower_password \
+  --s3-endpoint http://127.0.0.1:9000
+```
+
+验证、导入、列出或删除快照时，也需要使用相同的存储选项：
+
+```bash
+greptime cli data export-v2 verify \
+  --snapshot s3://greptime/snapshots/local-test \
+  --s3 \
+  --s3-bucket greptime \
+  --s3-region us-west-2 \
+  --s3-access-key-id superpower_ci_user \
+  --s3-secret-access-key superpower_password \
+  --s3-endpoint http://127.0.0.1:9000
+```
+
+```bash
+greptime cli data import-v2 \
+  --addr 127.0.0.1:4000 \
+  --from s3://greptime/snapshots/local-test \
+  --s3 \
+  --s3-bucket greptime \
+  --s3-region us-west-2 \
+  --s3-access-key-id superpower_ci_user \
+  --s3-secret-access-key superpower_password \
+  --s3-endpoint http://127.0.0.1:9000
+```
+
+对于 AWS S3，请使用相同的 `--s3` 选项；除非使用自定义 endpoint，否则不要传 `--s3-endpoint`。如果你的环境使用 instance profile 或其他凭据提供机制，可能不需要显式传入 access key。S3 backend 仍然需要 `--s3`、`--s3-bucket` 和 `--s3-region`。
+
+## 导出指定 schemas
+
+使用 `--schemas` 只导出指定 schemas。可以传入逗号分隔的列表：
+
+```bash
+greptime cli data export-v2 create \
+  --addr 127.0.0.1:4000 \
+  --to file:///tmp/greptime-snapshots/observability \
+  --schemas public,metrics
+```
+
+也可以多次传入该选项：
+
+```bash
+greptime cli data export-v2 create \
+  --addr 127.0.0.1:4000 \
+  --to file:///tmp/greptime-snapshots/observability \
+  --schemas public \
+  --schemas metrics
+```
+
+导入时，`--schemas` 会从快照中选择一个子集：
+
+```bash
+greptime cli data import-v2 \
+  --addr 127.0.0.1:4000 \
+  --from file:///tmp/greptime-snapshots/observability \
+  --schemas public
+```
+
+如果请求的 schema 不存在于快照中，导入会失败。
+
+## 只导出 schema
+
+使用 `--schema-only` 导出表定义，不导出数据：
+
+```bash
+greptime cli data export-v2 create \
+  --addr 127.0.0.1:4000 \
+  --to file:///tmp/greptime-snapshots/schema-only \
+  --schema-only
+```
+
+导入 schema-only 快照会恢复 schema，但不会导入数据 chunks：
+
+```bash
+greptime cli data import-v2 \
+  --addr 127.0.0.1:4000 \
+  --from file:///tmp/greptime-snapshots/schema-only
+```
+
+## 按时间范围和 chunk window 导出
+
+对于大数据集，请使用有界时间范围和 chunk window。Export/Import V2 会为范围内的每个 schema 创建一个或多个数据 chunks。
+
+```bash
+greptime cli data export-v2 create \
+  --addr 127.0.0.1:4000 \
+  --to s3://greptime/snapshots/prod-2026-06 \
+  --start-time 2026-06-01T00:00:00Z \
+  --end-time 2026-07-01T00:00:00Z \
+  --chunk-time-window 1d \
+  --s3 \
+  --s3-bucket greptime \
+  --s3-region us-west-2 \
+  --s3-access-key-id superpower_ci_user \
+  --s3-secret-access-key superpower_password \
+  --s3-endpoint http://127.0.0.1:9000
+```
+
+`--chunk-time-window` 需要同时指定 `--start-time` 和 `--end-time`。
+
+Chunks 会按时间窗口创建。例如，15 分钟的范围配合 `--chunk-time-window 5m` 会创建 3 个 chunks。导入时，数据任务按 chunk 和 schema 调度。如果快照包含 3 个 chunks，且有 2 个 schema 包含数据，则导入会调度 6 个数据任务。
+
+快照数据文件也会按 schema 和 chunk 组织。例如，一个多 chunk 快照可能包含如下路径：
+
+```text
+data/logs/1/app_logs.parquet
+data/logs/2/app_logs.parquet
+data/logs/3/app_logs.parquet
+data/public/1/host_metrics.parquet
+data/public/2/host_metrics.parquet
+data/public/3/host_metrics.parquet
+```
+
+请根据数据量和数据密度选择 chunk window：
+
+- 对于较小或稀疏的数据集，使用更大的 window，避免产生太多小 chunks。
+- 对于较大的数据集，使用更小的 window，让每个 chunk 保持在可管理的大小。
+- 可以先从 `1d` 开始，再根据导出耗时和 chunk 大小调整。
+
+## 调整并行度
+
+导出有两个并行度选项：
+
+- `--parallelism` 控制每个 schema、每个 chunk 上 server-side `COPY DATABASE` 的并行度。默认值为 `1`。
+- `--chunk-parallelism` 控制 client 同时运行多少个 export chunks。默认值为 `1`，有效范围是 `1..=64`。
+
+导入使用：
+
+- `--task-parallelism` 控制 client 同时运行多少个 import data tasks。默认值为 `1`，有效范围是 `1..=64`。
+
+请逐步提高这些值，并监控 GreptimeDB、对象存储和网络资源使用情况。
+
+## 恢复中断的导出或导入
+
+Export/Import V2 设计上支持恢复中断的工作。
+
+对于导出：
+
+- 如果目标快照不存在，`export-v2 create` 会创建它。
+- 如果目标快照已存在，同一条命令会从已有进度继续执行。
+- 已完成的 chunks 会被跳过。失败或 pending 的 chunks 会重试。
+- 只有在你想删除已有快照并重新创建时，才使用 `--force`。
+
+```bash
+greptime cli data export-v2 create \
+  --addr 127.0.0.1:4000 \
+  --to file:///tmp/greptime-snapshots/demo
+```
+
+中断后再次运行同一条命令即可继续。
+
+对于导入，导入运行时进度会保存在 state 文件中。默认情况下，state 文件位于 `~/.greptime/import_state`。如果希望使用显式的 state 文件位置，可以用 `--state-path` 覆盖：
+
+```bash
+greptime cli data import-v2 \
+  --addr 127.0.0.1:4000 \
+  --from file:///tmp/greptime-snapshots/demo \
+  --state-path /tmp/greptime-import-demo.state
+```
+
+`--dry-run` 不会创建 import state 文件。真正的导入如果失败或中断，会保留 state 文件，因此下一次运行可以恢复已完成的数据任务。导入成功后，import-v2 会自动删除 state 文件，因为已经没有需要恢复的剩余工作。相同前缀的 `.lock` 文件可能保留下来；它是锁文件，不是导入状态内容。
+
+如果你确实想在失败或中断后从头重新运行导入，请使用不同的 `--state-path`，或在确认安全后删除之前的 state 文件。
+
+## Dry-run 导入
+
+使用 `--dry-run` 验证快照和导入计划，但不执行 DDL，也不导入数据：
+
+```bash
+greptime cli data import-v2 \
+  --addr 127.0.0.1:4000 \
+  --from file:///tmp/greptime-snapshots/demo \
+  --dry-run
+```
+
+Dry-run 适合在生产迁移或恢复前使用。
+
+## 验证、列出和删除快照
+
+验证快照：
+
+```bash
+greptime cli data export-v2 verify \
+  --snapshot file:///tmp/greptime-snapshots/demo
+```
+
+列出父路径下的快照：
+
+```bash
+greptime cli data export-v2 list \
+  --location file:///tmp/greptime-snapshots
+```
+
+删除快照：
+
+```bash
+greptime cli data export-v2 delete \
+  --snapshot file:///tmp/greptime-snapshots/demo
+```
+
+对于非交互式删除，请传入 `--no-confirm`：
+
+```bash
+greptime cli data export-v2 delete \
+  --snapshot s3://greptime/snapshots/local-test \
+  --no-confirm \
+  --s3 \
+  --s3-bucket greptime \
+  --s3-region us-west-2 \
+  --s3-access-key-id superpower_ci_user \
+  --s3-secret-access-key superpower_password \
+  --s3-endpoint http://127.0.0.1:9000
+```
+
+## 认证、超时、代理和进度
+
+如果 GreptimeDB 实例启用了 basic authentication，请使用 `--auth-basic <username>:<password>` 传入凭据。
+
+使用 `--timeout` 设置请求超时时间，例如 `--timeout 60s` 或 `--timeout 5m`。
+
+对于会连接 GreptimeDB HTTP endpoint 的命令，例如 `export-v2 create` 和 `import-v2`，可以使用 `--proxy` 设置 HTTP 代理，或使用 `--no-proxy` 禁用代理：
+
+```bash
+greptime cli data import-v2 \
+  --addr 127.0.0.1:4000 \
+  --from file:///tmp/greptime-snapshots/demo \
+  --no-proxy
+```
+
+长时间运行的 create 和 import 命令支持使用 `--progress` 控制进度输出：
+
+- `auto`：在 TTY 上显示交互式进度条，否则输出进度日志。这是默认值。
+- `always`：始终输出进度；在 TTY 上使用进度条，否则输出轻量日志。
+- `never`：不输出进度。
+
+## 支持的存储后端
+
+Export/Import V2 支持本地文件系统快照和远程对象存储快照。
+
+对于远程对象存储，请只启用一个 backend：
+
+- `--s3`：用于 AWS S3 或 MinIO 等 S3-compatible 存储
+- `--oss`：用于阿里云 OSS
+- `--gcs`：用于 Google Cloud Storage
+- `--azblob`：用于 Azure Blob Storage
+
+常用 S3 选项如下：
+
+| Option | Description |
+| --- | --- |
+| `--s3-bucket` | S3 bucket 名称。使用 S3 时必填。 |
+| `--s3-region` | S3 region。使用 S3 时必填。 |
+| `--s3-access-key-id` | Access key ID。当环境提供凭据时可选。 |
+| `--s3-secret-access-key` | Secret access key。当环境提供凭据时可选。 |
+| `--s3-endpoint` | 自定义 S3-compatible endpoint，例如 MinIO endpoint。 |
+| `--s3-enable-virtual-host-style` | 启用 virtual-hosted-style 请求。 |
+| `--s3-disable-ec2-metadata` | 禁用 EC2 metadata service 凭据查找。 |
+
+## 故障排除
+
+### 无法连接到 `/v1/sql`
+
+检查 GreptimeDB 是否正在运行，以及 `--addr` 是否指向 HTTP endpoint：
+
+```bash
+curl http://127.0.0.1:4000/health
+```
+
+### `--chunk-time-window` 校验失败
+
+`--chunk-time-window` 需要同时指定 `--start-time` 和 `--end-time`。请添加有界时间范围，或移除 `--chunk-time-window`。
+
+### S3 或 MinIO 返回 `NoSuchBucket` 或 `NoSuchKey`
+
+请检查：
+
+- 快照 URI 中的 bucket 是否与 `--s3-bucket` 一致。
+- 对于 MinIO 或其他 S3-compatible 服务，是否设置了 `--s3-endpoint`。
+- 凭据是否可以读写快照位置。
+- create、verify、import、list 和 delete 命令是否传入了相同的存储选项。
+
+### Import 意外跳过数据
+
+Import 会从 state 文件恢复。如果之前的导入已经将任务标记为 completed，后续使用同一个 state identity 运行时可能会跳过这些任务。请为每次恢复操作使用显式的 `--state-path`，或在确认安全后删除旧 state 文件。
+
+### 请求的 schema 不存在
+
+在导入时使用 `--schemas` 时，请确认该 schema 存在于快照中。请先使用 `export-v2 verify`，并检查快照内容。
+
+### 验证失败
+
+不要导入验证失败的快照。快照可能不完整或已损坏。请使用同一条命令重新运行导出，以恢复缺失的 chunks；如果你确实想丢弃已有快照并重新创建，请使用 `--force`。
+
+## 限制
+
+- Export/Import V2 快照与 legacy export/import 输出不是同一种格式。
+- Schema filter 的粒度是 schema-level。该命令不覆盖 table-level filter。
+- Time-range chunking 面向时间序列数据设计。稀疏数据可能需要更大的 chunk window。
+- Schema-only 快照不包含数据文件。
+- 大规模迁移需要仔细调优 chunk window、并行度、对象存储吞吐和 GreptimeDB 资源。
diff --git a/sidebars.ts b/sidebars.ts
index 5a305b992..60714408d 100644
--- a/sidebars.ts
+++ b/sidebars.ts
@@ -387,6 +387,7 @@ const sidebars: SidebarsConfig = {
                   label: 'Overview',
                 },
                 'user-guide/deployments-administration/disaster-recovery/back-up-&-restore-data',
+                'user-guide/deployments-administration/disaster-recovery/export-import-v2',
                 'user-guide/deployments-administration/disaster-recovery/back-up-&-restore-meta-data',
                 'user-guide/deployments-administration/disaster-recovery/dr-solution-based-on-cross-region-deployment-in-single-cluster',
               ],