5 0 0:Changing Retention (EOL)

From SEPsesam
Other languages:

Copyright © SEP AG 1999-2022. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3 Beefalo V2/5.0.0 Jaglion. For previous documentation version(s), check Managing EOL in earlier versions.


Overview

When configuring the SEP sesam environment, you set up media pools and define the retention time. The retention time is set up on a media pool level. It is specified in days and defines how long the backed up data remains protected after it is written to the media. The retention period starts from the date a saveset is written to the media (at the end time of the first backup) and thus defines the expiry date of the saveset (saveset EOL). When the protection (EOL) expires, SEP sesam can use the media for backups again.

To ensure the recoverability of the complete backup chain and protect against data loss, SEP sesam provides a dependency-based retention strategy through automatic EOL adjustment. This strategy is used to manage and preserve the recoverability of the backup chain.

If the default retention does not meet the requirements, you can manually adjust the retention period, or more precisely the expiration date – EOL (End of Lifetime) – of your data.

There are three different EOL types, which are linked to object types and also depend on the storage media used.

saveset EOL
You can change the expiry date of any individual saveset that is stored in the data store, see Changing Saveset EOL.
backup EOL
You can change the expiry date for all backup-related savesets. Unlike the saveset EOL, which is applied individually to each selected saveset, changing the backup EOL always affects all dependent backup versions that are part of the same backup, see Changing Backup EOL.
(tape) media EOL
Some special rules apply to tape media, as the expiry date of the tape corresponds to the maximum retention time (the longest EOL) identified on the tape, see Changing Media EOL.
SEP Tip.png Tip
In the Components -> Media view, you can check the column Media EOL changed by, which shows the EOL-changes made via automatic EOL adjustment by Backup ID/Saveset ID and EOL changed manually by the UI user. This information can also be generated for audit trail purposes, see Audit Logging.

EOL changed by.png

For a detailed description of all EOL types, see EOL (retention) types.

Modifying retention (EOL)

Manually extending EOL can be used for special cases, e.g. to extend the retention period for certain backup data that has also been migrated and is stored on other media pools.
Manually reducing EOL can be used to allow premature retirement of an individual saveset. Manually reducing EOL can lead to potential data loss due to the inability to restore from a backup.
You can also delete your backups before their EOL is reached by using the Delete Backup function, as described in the section Deleting savesets, backups or data on tape media.

Information sign.png Note
It is not recommended to manually adjust EOL. This will override the EOL set by the retention time (in days) in the media pool configuration and started on the date a saveset is written to the media. Changing EOL should only be used in special cases and exceptions.

How SEP sesam manages extending EOL depends on its version; the following sections describe the behavior for versions 5.0.0 Jaglion and higher. If you are using one of the previous SEP sesam versions, refer to the relevant documentation: for Beefalo, see Managing EOL; for Grolar: Manually extending EOL in versions 4.4.3-4.4.3 Grolar.

Changing Backup EOL

The Backup EOL parameter is the expiry date for all data belonging to the same backup, including migrated and replicated savesets. You can check and modify the Backup EOL parameter by setting an exact date for it. You can also delete a backup before it expires, as described in the section Expiring savesets, backups or tape media. The deletion of a backup affects all data belonging to the same backup (entire backup chain), including migrated and replicated savesets.

Backup EOL can be changed under several views in the GUI.

  • From Main Selection -> Job State-> Backups, double-click the backup task (tab Info 1) and click the Backup EOL drop-down calendar to choose a new date.
  • BCK EOL task-change.jpg
  • From Main Selection -> Data stores-> double-click the selected data store to open the properties and click the tab Savesets, look for the Backup EOL column and click the date to open the drop-down calendar and choose a new date.
  • From Main Selection -> Media Pools, expand the target media pool -> double-click the selected item and in the properties click the tab Savesets, then click the date under the Backup EOL column to open the drop-down calendar and choose a new date.
  • From Main Selection -> Media-> filter the media, e.g., by using the column Media EOL to get the list of target media, or select the target media from the list, then double-click the target item to open its properties and click the tab Savesets, look for the Backup EOL column and click the date to open the drop-down calendar and choose a new date.
SEP Tip.png Tip
You can configure global retention settings to customize the default retention behavior for backups and migrated savesets, see the section Customize the default retention behavior for backups and migration.
Increasing Backup EOL

If you extend the Backup EOL, the EOL is adjusted only for the saveset that already has the longest EOL, while EOL of other backups is not affected.

Information sign.png Note
Extending the Backup EOL of savesets stored on tape media can extend the EOL of the tape media (Media EOL) as the actual expiry date of the tape is defined by the longest EOL of all savesets stored on the same tape.
Decreasing Backup EOL

Decreasing the Backup EOL can affect all data belonging to the same backup (entire backup chain), including migrated and replicated savesets. You cannot set the expiry date to a time in the past (the minimum date allowed is the current date). However, you can delete a backup that you no longer need using the right-click Delete Backup function, as described in the section Deleting savesets, backups or data on tape media.

Changing Saveset EOL

The Saveset EOL parameter is the expiry date for an individual saveset that is stored in a data store or on tape media.

Saveset EOL can be changed under several views in the GUI.

  • From Main Selection -> Job State-> Backups, double-click the backup task (tab Info 1) and in the table Storage location click the date under the Saveset EOL column to open the drop-down calendar and choose a new date.
  • SAVESET EOL task-change.jpg
  • From Main Selection -> Data stores-> double-click the selected data store to open the properties and click the tab Savesets, look for the Saveset EOL column and click the date to open the drop-down calendar and choose a new date.
  • From Main Selection -> Media-> filter the media, eg., by using the column Media EOL to get the list of target media, or select the target media from the list, then double-click the target medium to open it properties, click the tab Savesets, look for the Saveset EOL column and click the date to open the drop-down calendar and choose a new date.
  • From Main Selection -> Media Pools, expand the target media pool -> double-click the medium and in the properties click the tab Savesets, then click the date under the Saveset EOL column to open the drop-down calendar and choose a new date.
Increasing Saveset EOL

If you extend the Saveset EOL and one of the savesets is part of an FDI backup chain, then the EOL of the previous savesets in the chain will also be extended.

Decreasing SavesetEOL

If you shorten the saveset EOL, the new expiry date is set immediately for the selected individual saveset. You cannot set the expiry date to a time in the past (the minimum date allowed is the current date). However, you can delete the saveset(s) that you no longer need using the right-click Delete Saveset function, as described in the section Deleting savesets, backups or data on tape media.

Changing Media EOL

To increase or decrease the EOL of tape media, shown as Media EOL in the Media view or as Locked until in tape properties, you can adjust the Media EOL. The manually set EOL applies to all savesets on the tape.

Media EOL is displayed in the Media view list. The lock icon displayed next to the EOL date indicates:

  • Gray open lock: EOL has expired and the medium can be overwritten.
  • Blue lock: The medium is protected until the displayed date (Media EOL) and the current data cannot be overwritten, but there is still free space on the tape for new savesets.
  • Red lock: The tape is full and protected until the displayed date.

Media view lock.jpg

Increasing Media EOL

If you are manually extend the Media EOL, the new EOL applies to all savesets on the tape.

Decreasing Media EOL

If you decrease the Media EOL, the new expiry date is set immediately for the whole tape.

Information sign.png Note
The EOL of tape media may also depend on savesets that are not stored on the same tape – savesets that refer to FULL/DIFF/INCR savesets stored on other media or even data stores. Have in mind that you need all the backups in the backup chain for restore and set your EOL date so that it will not break the chain.

You cannot set the expiry date to a time in the past. However, you can expire the tape(s) that you no longer need using the right-click Expire function, as described in the section Expire savesets, backups or tape media.

SEP Tip.png Tip
If the EOL date of the tape media has been reached, but you do not want to reuse the tape, you can also lock the tape (by using write protection). This option overrides the Media EOL.

Customize the default retention behavior for backups and migration

You can configure global retention settings to customize the default retention behavior for backups and migrated savesets, such as to allow longer retention time of different media pools for migrated savesets, decrease retention time for failed backups, and change the automatic retention of the last successful backup and/or migration.

To change the global retention policy, you can add or modify the keys associated with retention: SEP sesam menu bar, click Configuration -> Defaults -> Settings. See Customizing Global Retention Policy for details.

The screenshot shows the Defaults -> Settings table with the EOL-related parameters.

EOL keys.jpg

Deleting savesets, backups or data on tape media

Once the EOL of a saveset (Saveset EOL) is reached, its protection expires.
However, the EOL of the tape media (Media EOL) follows a different logic than the individual savesets stored in a data store and it will not be re-used until all savesets on it have expired. Therefore, the EOL of the tape media (Media EOL) expires when the saveset with the longest EOL on the tape expires. The EOL of the tape may also depend on savesets that are not stored on the same tape. For details on tape-specific management and protection, see Tape Management.
How SEP sesam uses the storage space of an expired saveset is described in Automatic Retention (EOL) Management.

You can manually delete a saveset or backup, or expire tape media containing data you no longer need.

SEP Warning.png Warning
  • Deleting the DIFF or INCR saveset(s) results in purging and overwriting the complete backup chain!
  • Deleting a backup affects all data belonging to the same backup (entire backup chain), including migrated and replicated savesets.
  • Expiring the tape means that the data is no longer protected and SEP sesam can use the tape for backups again. Note that when deleting a tape medium, the medium is deleted from the SEP sesam DB.

Deleting a backup

Deleting a backup affects all data belonging to the same backup (the entire backup chain), including migrated and replicated savesets.

You can delete the selected backup only or the complete backup chain of the selected backup. When deleting a backup, the deletion is started immediately and can take some time to complete. To avoid the wait, you have the option to postpone deletion until next purge.

You can delete the backup directly by using the Delete function in one of the views that show the Savesets tab/properties or directly in the backup result properties:

  • Media -> double-click to select the media -> switch to the Savesets tab -> select the task and right-click -> Backup -> Delete.
  • Job State -> Backups -> double-click to select the backup -> click the button Delete Backup.

Deleting the backup deletes the selected backup and all related savesets based on the same backup. This means that all dependent saveset versions that are part of the backup are deleted immediately or during the next purge.

Information sign.png Note
  • Be careful with the delete function, as all data belonging to the same backup is irrevocably lost!
  • Deleting the DIFF or INCR backup results in purging and overwriting of all subsequent backups in the chain!

Deleting a saveset

You can delete the saveset directly by using the Delete function in one of the views showing the Savesets tab/properties or directly in the backup result properties:

  • Media -> double-click to select the media -> switch to the Savesets tab -> select the task and right-click -> Saveset -> Delete.
  • Job State -> Backups -> double-click to select the backup -> in the Storage Location table, select the saveset and click the button Delete Saveset.

When deleting a saveset, the deletion is started immediately and can take some time to complete. To avoid the wait, you have the option to postpone deletion until next purge.

In contrast to the Backup approach, deleting the Saveset only deletes the selected saveset(s). If the saveset is part of a backup chain, the entire backup chain is affected.

Information sign.png Note
Deleting the last remaining copy of a DIFF or INCR saveset might break the entire backup chain of existing younger backups, which are then no longer restorable!

Expiring tape media

The media EOL specifies the time until which the backed up data on tape remains protected and thus defines the expiry date of all savesets on tape. It is displayed in the Media view in the Media EOL column or by double-clicking the tape to open its properties in the Locked until field. Locked until and Media EOL are the same parameter that shows for how long the data on the tape cannot be overwritten. When EOL expires, SEP sesam can use the tape for backups again.

If the tape is loaded in the drive or library, you can delete the tape. Deleting a tape removes the tape from the SEP sesam database in contrast to expiring.

Information sign.png Note
You can delete tape media that you no longer need when the EOL of all savesets stored on the tape has expired and the tape is not write-protected.

You can delete the data on tape media directly by using the Expire function:

  • Media view -> select one or more tape(s) from the list by holding the CTRL key and clicking the selected media -> right-click -> Expire Media.
  • Media view -> double-click the tape in the list to open its properties -> click the button Expire Media.

Expiring the tape only removes the metadata of the tape; it does not remove the tape media from the SEP sesam database (use the Delete function for the latter). Clicking the button Expire Media opens a dialog with the following options:

  • Delay deletion until next purge marks the data on the tape for deletion according to the selected deletion option. The deletion is not started immediately but is postponed until the next purge.
  • Delete all metadata removes the tape's metadata but leaves the tape media listed in the database.
  • Delete all metadata and re-initialize tape deletes all metadata of the tape media and initializes the tape (if the tape is loaded into a drive), removing access to all existing data on the tape.

Expire media.jpg