Document ID: 329612
http://support.veritas.com/docs/329612
E-Mail this document to a colleague
http://support.veritas.com/docs/329612
E-Mail this document to a colleague
Backup Exec System Recovery Manager (BESRM) does not create new base backups when using default weekly schedule.
Details:
This is because the default custom setting is always set to Sunday (Figure 1).
Figure 1:
Workaround:
Manually edit the schedule and change the custom setting to a day that is included in the schedule (Mon-Fri).
Note: You should also change the start time for the custom weekly job so that it does not overlap with the scheduled incremental job. If the custom weekly job attempts to start when the scheduled incremental is still in progress, it may fail with the following error:
Description: Info 6C8F17E7: An automatic recovery point was not created because an earlier recovery point from the same job was still in progress. Error EBAB03F1: Operation aborted.
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.
Backup Exec System Recovery Manager (BESRM) does not create
new base backups (other than the initial backup) when the following are
true:
- Schedule is configured for Monday - Friday
- 'Start a new recovery point set (base)' is configured for Weekly
This is because the default custom setting is always set to Sunday (Figure 1).
Figure 1:
Workaround:
Manually edit the schedule and change the custom setting to a day that is included in the schedule (Mon-Fri).
Note: You should also change the start time for the custom weekly job so that it does not overlap with the scheduled incremental job. If the custom weekly job attempts to start when the scheduled incremental is still in progress, it may fail with the following error:
Description: Info 6C8F17E7: An automatic recovery point was not created because an earlier recovery point from the same job was still in progress. Error EBAB03F1: Operation aborted.
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.
Supplemental Material:
| System: Ref.# | Description |
| ETrack: 1796682 | BESRM: Weekly schedule set to Mon-Fri does not create new base backups. |
Products Applied:
Backup Exec System Recovery Manager Option 8.5, 8.5 .1 SP1, 8.5 .2 SP2, 8.5 .3 SP3, 8.5 .4 SP4, 8.5 .5 SP5
Backup Exec System Recovery Manager Option 8.5, 8.5 .1 SP1, 8.5 .2 SP2, 8.5 .3 SP3, 8.5 .4 SP4, 8.5 .5 SP5
Last Updated: August 14 2009 08:25 AM GMT
Expires on: 365 days from publish date
Subscribe to receive critical updates about this document
Expires on: 365 days from publish date
Subscribe to receive critical updates about this document
Subjects:
Backup Exec System Recovery Manager Option
Backup: Backup
Backup Exec System Recovery Manager Option
Backup: Backup
Languages:
English (US), French, German, Spanish
English (US), French, German, Spanish
Operating Systems:
Windows Server 2003
Windows Server 2003
Enterprise SP2, Enterprise Server
Symantec World Headquarters:
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com
20330 Stevens Creek Blvd. Cupertino, CA 95014
World Wide Web: http://www.symantec.com,
Tech Support Web: http://entsupport.symantec.com,
E-Mail Support: http://seer.entsupport.symantec.com/email_forms,
FTP: ftp://ftp.entsupport.symantec.com or http://ftp.entsupport.symantec.com
THE INFORMATION PROVIDED IN THE SYMANTEC SOFTWARE KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. SYMANTEC SOFTWARE DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL SYMANTEC SOFTWARE OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES,EVEN IF SYMANTEC SOFTWARE OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.