Point-in-time recovery options¶
pitr: enabled: <boolean> oplogSpanMin: <float64> compression: <string> compressionLevel: <int>
Enables point-in-time recovery
The duration of an oplog span in minutes. If set when the
pbm-agent is making an oplog slice, the slice’s span is updated right away.
If the new duration is smaller than the previous one, the
pbm-agent is triggered to save a new slice with the updated span. If the duration is larger, then the next slice is saved with the updated span in scheduled time.
The compression method for Point-in-Time Recovery oplog slices. Available in Percona Backup for MongoDB as of version 1.7.0.
The compression level is from
10. The default value depends on the compression method used.
The following table shows available compression levels per compression method:
|Compression method||Compression levels||Default|
||1 - fastest speed, 2 - default, 3 - better compression, 4 - best compression||2|
||From 1 (fastest) to 16||1|
||-1 - default compression, 0 - no compression, 1 - best speed, 9 - best compression||-1|
Note that the higher value you specify, the more time and computing resources it will take to compress the data.
Controls whether the base backup is required to start Point-in-Time Recovery recovery oplog slicing. When set to true, Percona Backup for MongoDB saves oplog chunks without the base backup snapshot. Available in Percona Backup for MongoDB starting with version 1.8.0. To learn more about the usage, see Point-in-Time Recovery oplog replay.
For free technical help, visit the Percona Community Forum.
To report bugs or submit feature requests, open a JIRA ticket.
For paid support and managed or consulting services , contact Percona Sales.
Created: March 23, 2023