Skip to content
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.

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

Replaced tech preview label with GA #199

Merged
merged 2 commits into from
Sep 2, 2024
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
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
2 changes: 1 addition & 1 deletion docs/features/backup-types.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,6 @@ The following table provides an overview of each type:
| [Selective](selective-backup.md) <br><small>GA</small> | 2.5.0 | Restore of the desired subset of data without disrupting the operations of your whole cluster| Sharded clusters starting with version 2.0.3. Sharded collections starting with version 2.1.0. | Yes | Yes |
| [Incremental](incremental-backup.md) <br><small>GA</small> | 2.1.0 (For PSMDB versions 4.2.24-24, 4.4.18-18, 5.0.2-1, 6.0.2-1 and higher) | Save on disk space for large backups where the data needs to be frequently backed up | Sharded clusters and non-sharded replica sets | Yes | No |
| [Point-in-time recovery](point-in-time-recovery.md) <br><small>GA</small> | 1.3.0 (logical) <br> 2.0.0 (physical manually) <br> 2.2.0 (physical automated) | Full restore of a database to a specific point in time with guaranteed data consistency | Sharded clusters and non-sharded replica sets | Yes | Yes |
| [Snapshot-based](snapshots.md) <br><small>[Tech preview](../reference/glossary.md#technical-preview-feature)</small> | 2.2.0 | Restore of a very large data set (e.g. Terabytes of data) with almost immediate access to data. A drawback is no guarantee for data consistency in your cluster | Sharded clusters and non-sharded replica sets | Yes | No |
| [Snapshot-based](snapshots.md) <br><small>GA</small> | 2.6.0 | Restore of a very large data set (e.g. Terabytes of data) with almost immediate access to data. A drawback is no guarantee for data consistency in your cluster | Sharded clusters and non-sharded replica sets | Yes | No |


5 changes: 2 additions & 3 deletions docs/features/snapshots.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,8 @@

## Considerations

1. This is a [technical preview feature](../reference/glossary.md#technical-preview-feature).
2. Supported only for full physical backups
3. Available only if you run Percona Server for MongoDB in your environment as PBM uses the [`$backupCursor and $backupCursorExtended aggregation stages` :octicons-link-external-16:](https://docs.percona.com/percona-server-for-mongodb/latest/backup-cursor.html).
1. Supported only for full physical backups
2. Available only if you run Percona Server for MongoDB in your environment as PBM uses the [`$backupCursor and $backupCursorExtended aggregation stages` :octicons-link-external-16:](https://docs.percona.com/percona-server-for-mongodb/latest/backup-cursor.html).
nastena1606 marked this conversation as resolved.
Show resolved Hide resolved

While a physical backup is a physical copy of your data directory, a snapshot is a point in time copy of your disk or a volume where the data files are stored. Restoring from snapshots is much faster and allows almost immediate access to data, while the database is unavailable during physical restore. Snapshot-based backups are especially useful for owners of large data sets with terabytes of data. Yet the snapshots don’t guarantee data consistency in sharded clusters.

Expand Down
Loading