![symantec backup exec 2014 the recovery set has expired symantec backup exec 2014 the recovery set has expired](https://media.itpro.co.uk/image/private/s--coHxW0LO--/t_content-image-desktop@2/v1572877701/itpro/images/dir_235/it_photo_117664.jpg)
The latest recovery point chain is a chain of backup sets required to restore data to the latest backup point-in-time.Ī. With this rule enabled, the backup sets that belongs to the last copy of these latest recovery point can not be groomed even when they are expired.Ī recovery point chain is a chain of backup sets required to restore data to a point-in-time, for example is a recovery point chain that is needed to recover data to the point-in-time of Inc2.
#SYMANTEC BACKUP EXEC 2014 THE RECOVERY SET HAS EXPIRED FULL#
The solution for this issue is to get a successful full backup set.Ĭause #2: DLM in Backup Exec 2012 has a rule to always keep the last copy of the latest recovery point chain per job definition per resource. This rule is enabled as default to guarantee that there is always a valid data recovery point. This will also prevent the expired backup sets from being groomed by DLM. If a full backup job failed, the incremental backup sets created after it depend on the earlier successful full backup set instead of this failed full backup set, and all the incremental backup sets since the earlier successful backup set. Check the status of the full backup setsĪs stated in the example presented in cause #1, an incremental backup set depends on the last successful full backup set and all earlier incremental backup sets since the last successful full backup set. For example, if a full backup job is scheduled to run once a month, and the incremental backup jobs run hourly, then all of the incrementals that have run within the month will not be groomed until the new full backup job runs and the last incremental backup set created within the month expires.Ĭ.
![symantec backup exec 2014 the recovery set has expired symantec backup exec 2014 the recovery set has expired](https://content.spiceworksstatic.com/service.community/p/post_images/0000111730/55dd2b84/attached_image/2015-08-26_10h55_28.png)
![symantec backup exec 2014 the recovery set has expired symantec backup exec 2014 the recovery set has expired](https://vox.veritas.com/qsuop67736/attachments/qsuop67736/backup-exec/326479/1/backup2012%20(2).jpg)
This is because the newly created incremental backup sets are the dependents of these earlier incrementals, before their dependent backups expires they cannot be groomed. If a full backup job runs infrequently, and the incremental backup job keeps running, the earlier incremental backup sets cannot get groomed even after they are expired. Check if the job frequency for full backup job is appropriate They can only be groomed after all their dependent backup sets have expired.ī. Check if the retention settings for incremental backup sets are appropriateĪccording to Cause #1, if the retention of incremental backup set is set too long, then all the backup sets that the incremental depends on will not get groomed even when they are expired. For example, for NTFS file system backup, an incremental backup set depends on the last successful full backup set and all earlier incremental backup sets since the last successful full backup set.Ī. SolutionĬause #1: The Data Lifecycle Management (DLM) in Backup Exec 2012 is designed to keep an expired backup set until all of its dependent sets are expired before grooming them together.Ī dependent set is determined by Backup Exec based on the data set relationship to guarantee complete data recovery for each backup point-in-time. Under certain conditions these backup sets that are not able to be deleted or groomed may fill up disk space cause low disk conditions or backups to stop if the storage device is out of space.
![symantec backup exec 2014 the recovery set has expired symantec backup exec 2014 the recovery set has expired](http://i.ytimg.com/vi/hDh20cNIyxQ/maxresdefault.jpg)
These latest recovery points sets can be ungroomed expired backup sets and still fall into this rule. This new Data Lifecycle Management ( DLM ) functionality is to ensure a server is protected and the latest backup set exists in case of a disaster recovery or restore. DLM has a rule to always keep the last copy of the latest recovery point chain per job definition per resource. Backup Exec 2012 introduces a new feature that prevents the overwrite or expiring of the last backup sets in a recovery chain. When multiple backup to disk or dedup sets exist for a resource, the last copy or latest recovery chain set can't be deleted or removed.