View source for 5 0 0:Automatic Retention (EOL) Management

<noinclude>
<div class="noprint"><languages />

<translate><!--T:66--> {{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|5.0.0 ''Jaglion'']]|link=[[Special:MyLanguage/4_4_3_Beefalo:Managing_EOL|Managing EOL in earlier versions]]}}</translate></div><br /></noinclude>


==<translate> <!--T:67--> Overview</translate>== 
 <noinclude><div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>
<translate>
<!--T:68-->
Additional resources</translate></b></center>

{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" |<translate><!--T:69--> [[File:SEP_next.png|45px|link=Special:MyLanguage/Changing_Retention_(EOL)|Changing Retention (EOL)]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |

<translate>
<!--T:70-->
See also: [[Special:MyLanguage/Changing_Retention_(EOL)|Changing Retention (EOL)]] – [[Special:MyLanguage/Backup_Chain_Dependencies#check|Backup Chain Dependencies]] – [[Special:MyLanguage/Backup Strategy Best Practices|Backup Strategy Best Practices]] – [[Special:MyLanguage/Tape_Management|Tape Management]] – [[Special:MyLanguage/Backup Strategy Best Practices|Backup Strategy Best Practices]]</translate>
|}

{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:71--> [[File:SEP_Video.png|45px|link=Special:MyLanguage/Video Tutorials & Screencasts#installation|installation videos & screencasts]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |

<translate>
<!--T:72-->
Watch SEP sesam [[Special:MyLanguage/Video Tutorials & Screencasts#installation|installation videos & screencasts]].</translate>
|}

{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | 

<translate>
<!--T:73-->
Check [[Special:MyLanguage/FAQ|FAQ]] to find the answers to most common questions.</translate>
|}

{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" | <translate><!--T:74--> [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]</translate>
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | 

<translate>
<!--T:75-->
Problems? See the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]. </translate>
|}</div></noinclude>


<translate><!--T:76--> Data retention is the amount of time a backup is kept by SEP sesam. When you create a [[Special:MyLanguage/SEP_sesam_Glossary#media_pool|media pool]], you set the retention time for the pool. Running respective backup tasks creates a backup chain on your backup storage consisting of a [[Special:MyLanguage/SEP_sesam_Glossary#FULL|full]] backup, followed by [[Special:MyLanguage/SEP_sesam_Glossary#DIFF|differential]] and [[Special:MyLanguage/SEP_sesam_Glossary#INCR|incremental]] backups, a backup metadata file, and may also include other dependent backups, such as migrated and replicated backups. Some INCR backups use [[Special:MyLanguage/Changed_Block_Tracking_(CBT)|CBT (changed block tracking)]].</translate>


==={{anchor|dependency-based_retention}}<translate><!--T:77--> What is retention time and EOL (End of Lifetime)</translate> === 

<translate>
<!--T:78-->
Retention time specifies the time period for which backup data is protected after it is written to the media, so that the savesets are preserved and available for restore. Data retention is important to ensure that all regulations and retention schedules are met. How long you should retain data depends on the nature of your business, as well as regulatory, legal, and other requirements.</translate>
*<translate><!--T:79--> Retention time is set up at a media pool level and is specified in days.</translate> 
*<translate><!--T:80--> 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 '''expiration date of the saveset''' – '''EOL''' (''End of Lifetime''). For example, the retention time of a media pool is 30 days and the data is backed up to the media on January 1, therefore the ''saveset EOL'' is January 31. There are three different EOL types associated with object types and also depending on the storage media used; for details, see the section [[Special:MyLanguage/5_0_0:Automatic_Retention_(EOL)_Management#EOL|EOL (retention) types]].</translate>
*<translate><!--T:81--> When the protection (EOL) expires, SEP sesam can use the media for backups again. For more details, see the section [[Special:MyLanguage/5_0_0:Automatic_Retention_(EOL)_Management#expired_EOL|What happens when retention expires]]. </translate>

<translate>
<!--T:82-->
SEP sesam provides automatic EOL (retention) management to ensure recoverability of the entire backup chain and protect against data loss, based on backup chain dependencies. You can also manually adjust the EOL of your data, as described in [[Special:MyLanguage/Changing_Retention_(EOL)|Changing Retention (EOL)]].</translate>

{{<translate> <!--T:83--> note</translate>|<translate> <!--T:84--> EOL (retention time) refers only to backups and related migrated and replicated savesets. SEP sesam logs, readability check logs, calendar sheet entries, and restore tasks have separate retention parameters. For details, see [[Special:MyLanguage/SEP_sesam_Glossary#retention_periods|retention periods]].</translate>}}


==={{anchor|bck_chain}}<translate><!--T:85--> What are backup chain dependencies </translate>=== 

<translate>
<!--T:86-->
A backup chain consists of [[Special:MyLanguage/SEP_sesam_Glossary#FULL|full]], [[Special:MyLanguage/SEP_sesam_Glossary#DIFF|differential]] and [[Special:MyLanguage/SEP_sesam_Glossary#INCR|incremental]] backups. Running respective backup tasks creates a backup chain on your backup storage consisting of a full backup, followed by differential and incremental backups, and, additionally, a backup metadata file. Some INCR backups use Changed Block Tracking (CBT), an incremental backup technology for virtual machines that creates faster and smaller backups.

<!--T:87-->
An FDI backup chain can contain any number of backups that each depend on other backups in the chain and can also depend on another backup in the number of backups. A backup chain can contain the first (primary) backup and one or more dependent backups, such as ''migrated'' and ''replicated'' backups.</translate> 
*<translate><!--T:88--> A primary backup can be a backup that does not require any other backups for a successful data restore. Thus, a primary backup can be a complete backup, but a dependent backup may require additional backups for a successful data restore as it may depend on the additional backups.</translate>
*<translate><!--T:89--> For example, for INCR backups all previous savesets (FULL, DIFF and INCR) must be present for a successful restore.</translate> 
*<translate><!--T:90--> If retention time is considered only from the perspective of an individual backup, it can ensure restorability of data only for that particular backup.</translate> 
*<translate><!--T:91--> To enable full recovery of the data backed up in the backup chain, all dependent backup savesets are tracked and their retention time is managed according to their dependencies.</translate>

<translate>
<!--T:92-->
Dependent backups are also classified by the respective depth of the dependent backups in the backup chain. The respective depth can be a measure of how many backups are required to complete the restore of a system, e.g. a VM, to a predetermined state.</translate><br />
<translate>
<!--T:93-->
SEP sesam provides the '''''saveset tree view''''' to determine dependencies and EOL of an FDI backup chain. This view shows a data structure that relates savesets to their dependencies. You should use it before manually changing the EOL parameter to avoid breaking the backup chain. For details, see [[Special:MyLanguage/Backup_Chain_Dependencies#check|Backup Chain Dependencies]].</translate>

<translate>
<!--T:94-->
'''Example of a 14-day retention scenario'''</translate><br />
<translate>
<!--T:95-->
In a typical 14-day retention scenario, the first execution of the backup job creates a full backup. This is followed by differential and incremental backups. Once the 14-day retention (EOL) is reached, the savesets are marked as EOL-free and can be [[Special:MyLanguage/SEP_sesam_Glossary#purge|purged]]. If the backup data is stored on tape, its protection expires when the [[Special:MyLanguage/Tape_Management#tape_EOL|tape media EOL]] expires. For example, the backup chain has the following retention: FULL on pool MONTH (retention time:32), DIFF on pool WEEK (retention time:15), and INCR on pool DAY (retention time:7). The EOL of such an FDI chain is sufficient and no retention adjustment is required.</translate>

<translate>
<!--T:96-->
'''Automatic EOL adjustment'''</translate><br />
<translate>
<!--T:97-->
However, in some cases SEP sesam automatically adjusts the EOL to retain consistency of the backed up data and keep the backup chain readily available for restore. For example, it may happen that the expiry time of some savesets has already expired, but they have not been deleted due to one or more rules of the backup chain dependencies. 

<!--T:98-->
There are six main rules that lead to an adjusted EOL.</translate>

=={{anchor|rules}}<translate><!--T:99--> Rules for the automatically adjusted retention time </translate>== 

<translate>
<!--T:100-->
If the retention time is considered only from the perspective of an individual backup, it can ensure restorability of data only for that particular backup. To enable complete restore of data backed up in the backup chain, SEP sesam tracks all dependent backup savesets and manages their retention time according to their dependencies. 

<!--T:101-->
For example, INCR backups require all previous savesets (FULL, DIFF and INCR) to be available for a successful restore: INCR backup taken as the third INCR after the FULL requires the FULL, the first, the second, and the third INCR to provide complete restore capability. If a saveset is missing from the backup chain, data recovery to a specific point in time is not possible. For this reason, SEP sesam maintains control over the dependencies among the individual backup savesets and provides six rules for dependency-based automatic retention.</translate>

==={{anchor|rule_1}}<translate><!--T:102--> Rule #1: Full backups do not expire as long as dependent DIFF/INCR exist </translate>=== 

<translate>
<!--T:103-->
For example, you set a media pool retention parameter to 30 days and run a FULL backup. This FULL saveset is initially kept for 30 days, e.g., until January 31. If a subsequent INCR or DIFF saveset in the chain has a longer EOL, e.g. an expiration date of February 3, the EOL of all previous savesets, including the FULL, is adjusted to the longer expiration date. </translate>

==={{anchor|rule_2}}<translate><!--T:104--> Rule #2: An increased EOL of a DIFF/INCR saveset results in an increased EOL of all dependent savesets</translate>=== 

<translate>
<!--T:105-->
If the EOL parameter of a DIFF or INCR saveset is increased, SEP sesam also increases the EOL of all dependent savesets (FULL and other DIFF and INCR). In this way, SEP sesam ensures that the EOL of the FULL saveset and other dependent DIFF and INCR is not shorter than the potentially modified EOL of the DIFF or INCR saveset. </translate> 

==={{anchor|rule_3}}<translate><!--T:106--> Rule #3: A decreased EOL of a DIFF/INCR saveset leads to reduced EOL of all dependent savesets</translate>=== 

<translate>
<!--T:107-->
If the EOL of a DIFF or INCR saveset is decreased, SEP sesam decreases the EOL of all dependent savesets (FULL and other DIFF and INCR).</translate>  


{{<translate><!--T:108--> warning</translate>|<translate><!--T:109--> If you use the ''Expire'' function to delete unneeded saveset(s) or backup set(s), SEP sesam issues a warning message, asking you to confirm your decision to expire the entire backup chain. If you allow the DIFF or INCR saveset(s) to expire, the entire backup chain will be deleted and overwritten.</translate>}}

==={{anchor|rule_4}}<translate><!--T:110--> Rule #4: ''A too short EOL of DIFF/INC savesets leads to an increased EOL''</translate>=== 

<translate>
<!--T:111-->
If the DIFF/INCR backup detects that a saveset belonging to an FDI chain has an EOL that is too short, then any subsequent DIFF/INCR backup that runs on a pool with a longer retention time will increase the EOL of the saveset from that particular pool.</translate>
 
{{<translate><!--T:112--> note</translate>|<translate><!--T:113--> If the EOL of a saveset belonging to an FDI chain has already expired, it will not be extended. In this case, the next DIFF/INCR backup will be executed as FULL backup.</translate>}}

==={{anchor|rule_5}}<translate><!--T:114--> Rule #5: ''A new or migrated DIFF/INC backup results in an adjusted EOL for dependent savesets''</translate>===

<translate>
<!--T:115-->
When a ''new INCR or DIFF backup is run'' or an ''INCR or DIFF backup is migrated'', SEP sesam automatically adjusts the EOL of all related savesets to preserve the backup data.</translate>

==={{anchor|rule_6}}<translate><!--T:116--> Rule #6: The last successful backup or migration is automatically retained </translate>=== 

<translate>
<!--T:117-->
SEP sesam automatically retains the last successful backup or migration saveset if the next backup/migration fails. By extending the EOL of the last successful backup/migration, SEP sesam ensures that at least one successful backup is retained. This behavior is enabled by default and can be changed by setting the values of the corresponding keys, as described in [[Special:MyLanguage/Customizing_Global_Retention_Policy|Customizing Global Retention Policy]].</translate>

{{<translate><!--T:118--> note</translate>|<translate><!--T:119--> SEP sesam also allows you to [[Special:MyLanguage/Changing_Retention_(EOL)|manually adjust EOL]] if the default retention does not meet the requirements, but you should be careful with this option. Manually adjusted EOL overrides the EOL defined by the retention time in the media pool configuration and should only be used for special cases and exceptions. Some special rules apply to the tape media EOL, see section [[Special:MyLanguage/5_0_0:Automatic_Retention_(EOL)_Management#EOL|EOL (retention) types]].</translate>}}


=={{anchor|expired_EOL}}<translate><!--T:120--> What happens when the saveset expires</translate>== 

<translate>
<!--T:121-->
The protection of a saveset expires when its EOL is reached. The storage space of an expired saveset is not used immediately; SEP sesam uses the ''GET_OLDEST'' policy to preserve the data on the media for as long as possible. The expired saveset can be used again if the following conditions are met:</translate>

*<translate><!--T:122--> As a rule, there must not be any other savesets that depend on this saveset. An expired saveset is not deleted until all sets in the backup chain that depend on it have expired and been deleted. You can override this condition by explicitly allowing the expiry date (EOL) of the entire backup chain to expire, which deletes the backup data of all related savesets.</translate>

*<translate><!--T:123--> If a saveset is stored on tape, the EOL of all stored savesets must have expired.</translate>

*<translate><!--T:124--> The media must not be ''[[Special:MyLanguage/SEP_sesam_Glossary#write-protected|write-protected]]'' (locked).</translate>

*<translate><!--T:125--> SEP sesam Server automatically allocates the media with the oldest EOL for re-use. The oldest medium is the medium with the oldest ''locked until'' (is [[Special:MyLanguage/SEP_sesam_Glossary#backup_day|backup day]]+ retention time) date in the media pool.</translate>

==={{anchor|track}}<translate><!--T:126--> Tracking the adjusted EOL </translate>=== 

<translate>
<!--T:127-->
In the ''Media'' view in the GUI, you can check the column ''Media EOL changed by'' that shows EOL-changes made via the automatic EOL adjustment by ''Backup ID/Saveset ID'', as well as the EOL that the user changed manually. The modified EOL is also recorded in the main log and can be generated for audit trail purposes, see [[Special:MyLanguage/Audit_Logging|Audit Logging]].</translate>

{{anchor|EOL}}
{{Source:EOL_Types}}
<noinclude>
<div class="noprint"><translate>

<!--T:129-->
==See also==
[[Special:MyLanguage/Changing_Retention_(EOL)|Changing Retention (EOL)]] – [[Special:MyLanguage/Backup_Chain_Dependencies#check|Backup Chain Dependencies]] – [[Special:MyLanguage/Backup Strategy Best Practices|Backup Strategy Best Practices]] – [[Special:MyLanguage/Tape_Management|Tape Management]] </translate></div>

{{Copyright}}</noinclude>