Veritas backup exec 16 will not delete expired backup set

#Veritas backup exec 16 will not delete expired backup set full#

This, and the fact that these backup modes allow to keep only one backup file on disk no matter of how long your retention policy is, make them a few times more space efficient than traditional incremental backup. On the other hand, reversed incremental backup mode (or incremental mode with transform enabled, once transformation happened) removes older restore points immediately, as soon as they fall out of retention policy. This option can speed the recovery of a crashed server because you only need to restore the working set backup to get. OR set the date on which the user account will be disabled (syntax is usermod -expiredate YYYY-MM-DD userNameHere ): usermod -expiredate 1 vivek. First, lock user account, enter: passwd -l vivek.

#Veritas backup exec 16 will not delete expired backup set full#

After last incremental backup file in backup chain falls out of your data retention policy (which happens only when retention policy reaches next full backup file), whole previous full backup chain is removed at once. The following is recommend procedure to delete a user from the Linux server. So, as long as last incremental backup file in backup chain must be restorable according to set retention policy, whole respective full + incremental backup chain will have to stay on disk (resulting in more backup files on disk then you may have expected). Take a look at this Connect item, which complains about exactly the same problem, seven years ago to the. Keep in mind that incremental backup mode by definition requires all previous backup files (full and incremental) to be available to make restore from incremental backup possible. EXEC xpdeletefile 0,NF:pathcms,Nbak,NT21:08:04 - this slash may be important - That said, you should simply not be using this stored procedure to clean up your backup folders.