Skip to content

Commit 1daf70f

Browse files
DOCSP-43480 moved groom job intervals table (#363)
1 parent 08404ce commit 1daf70f

File tree

1 file changed

+15
-14
lines changed

1 file changed

+15
-14
lines changed

source/admin/backup/grooms-page.txt

Lines changed: 15 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -22,19 +22,7 @@ space.
2222
If no existing :manual:`snapshots </reference/glossary/#std-term-snapshot>` reference a given
2323
block, |onprem| considers the block *unused* or *dead*. |onprem| grooms
2424
blockstores after the snapshot drops below the threshold of living
25-
bytes. |onprem| runs groom jobs at the following minimum intervals:
26-
27-
.. list-table::
28-
:widths: 20 80
29-
:header-rows: 1
30-
:stub-columns: 1
31-
32-
* - Blockstore Location
33-
- Minimum Groom Interval
34-
* - MongoDB
35-
- One time per year
36-
* - |s3|
37-
- One time every two weeks
25+
bytes.
3826

3927
.. _how-groom-jobs-work:
4028

@@ -114,8 +102,21 @@ What Triggers a Groom Job
114102
- the percentage of living bytes drops below a given threshold and
115103
- the number of dead bytes reaches a minimum value.
116104

117-
When grooming, Ops Manager removes all the dead bytes.
105+
|onprem| also runs groom jobs at the following minimum intervals:
118106

107+
.. list-table::
108+
:widths: 20 80
109+
:header-rows: 1
110+
:stub-columns: 1
111+
112+
* - Blockstore Location
113+
- Minimum Groom Interval
114+
* - S3
115+
- One time every two weeks
116+
* - MongoDB
117+
- One time per year
118+
119+
When grooming, Ops Manager removes all the dead bytes.
119120

120121
.. list-table::
121122
:widths: 30 35 35

0 commit comments

Comments
 (0)