Automatic cleanup of recovery points not working consistently which causes backup destination to run out of disk space.
Automatic cleanup of recovery points, to remain with the threshold ('Recovery Point Limit') specified, is not working consistently. This causes the backup destination to run out of disk space and subsequent backups to fail.
Consider the following scenario:
5 independent backup jobs targeted to their own specific USB drive. Recovery point limit is set to 2.
Monday backup is targeted to 'Monday' USB drive. Tuesday backup is targeted to 'Tuesday' USB drive and so on.
The issue is seen when 3 recovery point files are stored on the USB drive (i.e. the oldest recovery point should have been automatically removed when the most recent backup was completed).
High Priority Info: Error EBAB03F1: The operation was canceled by the user.
Info 6C8F1C2F: A recovery point operation on drive Tuesday was cancelled by the user.
Error E7D1001F: Unable to write to file.
Error E7D1003C: There is not enough space.
Error EBAB03F1: There is not enough space on the disk. 0x800704C7 (Backup Exec System Recovery)
The only workaround currently available is to manually delete the oldest recovery point to remain within the limit specified.
Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec Corporation is committed to product quality and satisfied customers.
This issue is currently under investigation by Symantec Corporation. Pending the outcome of the investigation, this issue may be resolved by way of a patch or hotfix in current or future revisions of the software. However, this particular issue is not currently scheduled for any release. If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Symantec Sales representative or the Symantec Sales group to discuss these concerns. For information on how to contact Symantec Sales, please see http://www.symantec.com
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.