Skip to content

Clarify TTL document restore behavior in backup documentation #343

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
HansWieser-MS wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Clarify TTL document restore behavior in backup documentation #343

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
14 changes: 9 additions & 5 deletions articles/cosmos-db/continuous-backup-restore-introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,11 +56,15 @@ You can choose to restore any combination of provisioned throughput containers,

The following configurations aren't restored after the point-in-time recovery:

* A subset of containers under a shared throughput database can't be restored. The entire database can be restored as a whole.
* Firewall, [virtual network](how-to-configure-vnet-service-endpoint.md), data plane role-based access control, or private endpoint settings.
* All the regions from the source account.
* Stored procedures, triggers, UDFs.
* Role-based access control assignments.
- A subset of containers under a shared throughput database can't be restored. The entire database can be restored as a whole.
- Database account keys. The restored account is generated with new database account keys.
- Firewall, [virtual network](how-to-configure-vnet-service-endpoint.md), data plane RBAC, or private endpoint settings.
- All the regions from the source account.
- Stored procedures, triggers, UDFs.
- Role-based access control assignments. These need to be reassigned.
- Documents that were deleted because of expired TTL are not restored by default, however the behavior can be enforced explicitly.
- Analytical data when synapse link is enabled.
- Materialized views.

You can add these configurations to the restored account after the restore is completed.

Expand Down
2 changes: 1 addition & 1 deletion articles/cosmos-db/periodic-backup-restore-introduction.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ The following configurations aren't restored after the point-in-time recovery:
- Regions. The restored account is only a single-region account, which is the write region of the source account.
- Stored procedures, triggers, user-defined functions (UDF).
- Role-based access control assignments. These need to be reassigned.
- Documents that were deleted because of expired TTL.
- Documents that were deleted because of expired TTL are not restored by default, however the behavior can be enforced explicitly.
Copy link

Copilot AI Jan 14, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The statement claims 'the behavior can be enforced explicitly' but there is no documentation in the codebase explaining how to explicitly enforce TTL-expired document restoration. This could confuse users who want to restore TTL-expired documents. Either add documentation explaining how to enforce this behavior, link to relevant documentation, or remove the claim if this feature doesn't exist or isn't documented.

Copilot uses AI. Check for mistakes.
- Analytical data when synapse link is enabled.
- Materialized views.

Expand Down