From 83b5076dcebb3c40c33410338349c4aafdcdab41 Mon Sep 17 00:00:00 2001 From: Dominik Csapak Date: Mon, 28 Feb 2022 12:20:07 +0100 Subject: [PATCH] docs: explain retention time for event allocation policy in more detail 'when the calendar event' triggers was too vague, it could mean for the current media-set or the next time. Apart from that, it was not technically correct all the time, since we take the start time of the next media set if that exists first. The idea here is that we begin the retention when the media set is finished. Signed-off-by: Dominik Csapak --- docs/tape-backup.rst | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/tape-backup.rst b/docs/tape-backup.rst index a8d6b7fd..ae597d3d 100644 --- a/docs/tape-backup.rst +++ b/docs/tape-backup.rst @@ -519,8 +519,9 @@ a single media pool, so a job only uses tapes from that pool. This balances between space efficiency and media count. - .. NOTE:: Retention period starts when the calendar event - triggers. + .. NOTE:: Retention period starts on the creation time of the next + media-set or, if that does not exist, when the calendar event + triggers the next time after the current media-set start time. Additionally, the following events may allocate a new media set: