Skip to content

[DOC-1349] Note clone time travel limitation #32056

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ddhodge wants to merge 2 commits into
base: master
Choose a base branch
from
+2 −0
Open

[DOC-1349] Note clone time travel limitation #32056

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3bb1525
Note clone time travel limitation
ddhodge Jun 5, 2026
abcf1a2
resolve comment
ddhodge Jun 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/content/stable/manage/backup-restore/instant-db-cloning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<issue 28814>}}.
- 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.
1 change: 1 addition & 0 deletions docs/content/v2025.1/manage/backup-restore/instant-db-cloning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 {{<issue 28814>}}.
- 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.