Synthetic full backup job does not concurrently run with a duplicate job
book
Article ID: 100034130
calendar_today
Updated On:
Resolution
WorkaroundAdjust the schedule not to run the jobs concurrently.
- or -
Start duplicate jobs before starting a synthetic full backup job.
Veritas Technologies LLC has acknowledged that the above-mentioned issue is present in the current version(s) listed under the Product(s) Section of this article. Veritas Technologies LLC is committed to product quality and satisfied customers.
There are currently no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time. 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 Veritas Sales representative or the Veritas Sales group to discuss these concerns. For information on how to contact Veritas Sales, please see http://www.veritas.com
Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.
Issue/Introduction
A duplicate job does not start when a synthetic full backup job is running.
The duplicate job will be running status, but the byte count keeps 0 (zero) until the synthetic full backup is completed.
Additional Information
ETrack: 3920536
Was this article helpful?
thumb_up
Yes
thumb_down
No