Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

Automatic cleanup of recovery points not working consistently which causes backup destination to run out of disk space.

Created: 15 Oct 2012 • Updated: 04 Nov 2013 | 1 comment
Chris Riley's picture
0
Votes
Login to vote
Me Too!I have the same issue
Product(s): Symantec System Recovery (formerly Backup Exec System Recovery) - BESR 2010, Symantec System Recovery (formerly Backup Exec System Recovery)
Severity: Non-data threatening / major functionality
Status: Investigating/gathering information
Tech Note: More Information

Problem

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).

Error

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)

Solution

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.

Comments 1 CommentJump to latest comment

fiasko's picture

I believe I have a similar problem as described or a mix.

has this been fixed(hotfix or otherwise?). I have a daily incremental job for 2  500 GB disks to a 2 TB  USB EXTERNAL DRIVE. Automatic optimizing of storage is specified with threshold of 1453,2MB. 

the job parameter are this:     

Drives and backup destinations:
 System Reserved (*:\) to [Seagate Backup Plus Drive]\Symantec Backups\System Reserved0-1_Drive.v2i
 (C:\) to [Seagate Backup Plus Drive]\Symantec Backups\C_Drive.v2i
 (D:\) to [Seagate Backup Plus Drive]\Symantec Backups\D_Drive.v2i

Start a new recovery point set (base):
 The first time the backup is run in a new month

Scheduled backup time:
 At 03:00 every day, starting 8.4.2013
 Next run time: 2.7.2013 03:00

Event triggers:
 [  ] Any user logs on to the computer
 [  ] Any user logs off from the computer (Not at Shutdown or Restart)
 [  ] Application is installed or uninstalled
 [  ] Application is launched
 [  ] Data added to the drive exceeds:

Options:
 Backup name: Drive Backup of System Reserved (*:\), (C:\), (D:\)
 Compression level: Standard
 [X] Verify recovery points after creation
 Recovery point set limit: 3
 Consolidate incrementals: Never
 [X] Prepend computer name to backup data file names
 [  ] Save backup files to a unique subfolder
 Description: None

 

Last night on 1.7 the  backup does not perform normal although there is no error.

The backup job is supposed to create a new   new recovery base for all the disks on 1. In new month. In this occasion would be the  fourth  by name if the first recovery set base  had not been deleted by  SSR 2013 a month ago.  All the same the backup job creates a recovery point set base for disc D but not for * or C, just ends happily with  no error whatsoever.  

I have 2 events for the 1 of July:

first: 03:00 Am

 

Info 6C8F1F65: The drive-based backup job, Drive Backup of System Reserved (*:\), (C:\), (D:\), has been started automatically.
Details:
Source: Symantec System Recovery

 

second: 05:25 Am

Info 6C8F0427: Symantec System Recovery service started successfully.
Details:
Source: Symantec System Recovery

Last time the ending event were:

Info 6C8F1F7D: A scheduled base recovery point of drive D:\ was created successfully.
Details:
Source: Symantec System Recovery

Info 6C8F1F7D: A scheduled base recovery point of drive *:\ was created successfully.
Details:
Source: Symantec System Recovery

Info 6C8F1F7D: A scheduled base recovery point of drive C:\ was created successfully.
Details:
Source: Symantec System Recovery

 

in that order

and  then 3 times

Info 6C8F0427: Symantec System Recovery service started successfully.
Details:
Source: Symantec System Recovery

Now I don’t get the ending event for the D drive

 

 

SSR 2013 version:11.0.1.47662 on W8

 

 

       

0
Login to vote