From 3bb1525acd88d7fa6f0926a46964a8e235c1d220 Mon Sep 17 00:00:00 2001 From: Dwight Hodge Date: Fri, 5 Jun 2026 11:17:20 -0400 Subject: [PATCH 1/2] Note clone time travel limitation --- docs/content/stable/manage/backup-restore/instant-db-cloning.md | 1 + docs/content/v2025.1/manage/backup-restore/instant-db-cloning.md | 1 + 2 files changed, 2 insertions(+) diff --git a/docs/content/stable/manage/backup-restore/instant-db-cloning.md b/docs/content/stable/manage/backup-restore/instant-db-cloning.md index 52e70917888d..567d895858c0 100644 --- a/docs/content/stable/manage/backup-restore/instant-db-cloning.md +++ b/docs/content/stable/manage/backup-restore/instant-db-cloning.md @@ -314,4 +314,5 @@ If you have [tablet limits](../../../architecture/docdb-sharding/tablet-splittin - Cloning as of a time close to the limit of the history retention period may fail. For example, if you have a history retention period of 10 minutes and you create a clone as of 9 minutes ago, the clone operation may fail. Use a slightly larger history retention period than you think you need. - Cloning to a point in time during which a DDL was running may fail. See issue {{}}. +- You cannot [time travel](../time-travel-query/) to a point in time prior to the creation of the clone. - Databases with many objects in multi-region deployments may take longer to clone. If the operation takes longer than 10 minutes, increase the `ysql_clone_pg_schema_rpc_timeout_ms` YB-TServer runtime flag. diff --git a/docs/content/v2025.1/manage/backup-restore/instant-db-cloning.md b/docs/content/v2025.1/manage/backup-restore/instant-db-cloning.md index ad0b4f587556..b6e3040f1ef2 100644 --- a/docs/content/v2025.1/manage/backup-restore/instant-db-cloning.md +++ b/docs/content/v2025.1/manage/backup-restore/instant-db-cloning.md @@ -297,4 +297,5 @@ If you have [tablet limits](../../../architecture/docdb-sharding/tablet-splittin - Cloning as of a time close to the limit of the history retention period may fail. For example, if you have a history retention period of 10 minutes and you create a clone as of 9 minutes ago, the clone operation may fail. Use a slightly larger history retention period than you think you need. - Cloning to a point in time during which a DDL was running may fail. See issue {{}}. +- You cannot [time travel](../time-travel-query/) to a point in time prior to the creation of the clone. - Databases with many objects in multi-region deployments may take longer to clone. If the operation takes longer than 10 minutes, increase the `ysql_clone_pg_schema_rpc_timeout_ms` YB-TServer runtime flag. From abcf1a2c6245e674f212a8dc71e41ee022cb97b3 Mon Sep 17 00:00:00 2001 From: Dwight Hodge Date: Fri, 5 Jun 2026 11:21:24 -0400 Subject: [PATCH 2/2] resolve comment --- docs/content/stable/manage/backup-restore/instant-db-cloning.md | 2 +- .../content/v2025.1/manage/backup-restore/instant-db-cloning.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/stable/manage/backup-restore/instant-db-cloning.md b/docs/content/stable/manage/backup-restore/instant-db-cloning.md index 567d895858c0..2941ccd5bdb9 100644 --- a/docs/content/stable/manage/backup-restore/instant-db-cloning.md +++ b/docs/content/stable/manage/backup-restore/instant-db-cloning.md @@ -314,5 +314,5 @@ If you have [tablet limits](../../../architecture/docdb-sharding/tablet-splittin - Cloning as of a time close to the limit of the history retention period may fail. For example, if you have a history retention period of 10 minutes and you create a clone as of 9 minutes ago, the clone operation may fail. Use a slightly larger history retention period than you think you need. - Cloning to a point in time during which a DDL was running may fail. See issue {{}}. -- You cannot [time travel](../time-travel-query/) to a point in time prior to the creation of the clone. +- You cannot [time travel](../time-travel-query/) to a point in time prior to the 'as of' time of the clone. - Databases with many objects in multi-region deployments may take longer to clone. If the operation takes longer than 10 minutes, increase the `ysql_clone_pg_schema_rpc_timeout_ms` YB-TServer runtime flag. diff --git a/docs/content/v2025.1/manage/backup-restore/instant-db-cloning.md b/docs/content/v2025.1/manage/backup-restore/instant-db-cloning.md index b6e3040f1ef2..afcbfd36f5db 100644 --- a/docs/content/v2025.1/manage/backup-restore/instant-db-cloning.md +++ b/docs/content/v2025.1/manage/backup-restore/instant-db-cloning.md @@ -297,5 +297,5 @@ If you have [tablet limits](../../../architecture/docdb-sharding/tablet-splittin - Cloning as of a time close to the limit of the history retention period may fail. For example, if you have a history retention period of 10 minutes and you create a clone as of 9 minutes ago, the clone operation may fail. Use a slightly larger history retention period than you think you need. - Cloning to a point in time during which a DDL was running may fail. See issue {{}}. -- You cannot [time travel](../time-travel-query/) to a point in time prior to the creation of the clone. +- You cannot [time travel](../time-travel-query/) to a point in time prior to the 'as of' time of the clone. - Databases with many objects in multi-region deployments may take longer to clone. If the operation takes longer than 10 minutes, increase the `ysql_clone_pg_schema_rpc_timeout_ms` YB-TServer runtime flag.