Duplicate jobs are skipped intermittently.

book

Article ID: 100040726

calendar_today

Updated On:

Description

Error Message

e000e054 - The job was skipped because the source backup job is not present

Cause

 

Resolution

WORKAROUND:
The skipped duplicate job can be run manually.


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.

This issue is currently under investigation by Veritas Technologies LLC. 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 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.


Product version

Backup Exec 15

Regarding Backup Exec 15, a supported hotfix has been made available for this issue. Please contact Veritas Technical Support to obtain this fix.
This hotfix has not yet gone through any extensive Q&A testing. Consequently, if you are not adversely affected by this problem and have a satisfactory temporary workaround in place, we recommend that you wait for the public release of this hotfix.

Issue/Introduction

Duplicate jobs are skipped intermittently.

When the duplicate job is skipped, the following errors appear in <Computername>-SGMon.log on Backup Exec server.

[<Computername>-SGMon.log]
BESERVER: [MM/DD/YY HH:MM:SS] [<TID>] -1 Dispatcher::loadBalanceTask(JOBNAME) Skipping Job, SourceImageID==GUID_NULL
BESERVER: [MM/DD/YY HH:MM:SS] [<TID>] -1 LoadBalanceTask(JOBNAME)=1
BESERVER: [MM/DD/YY HH:MM:SS] [<TID>] -1 CWorkItem::handleSkippedJob(JOBNAME)

If "Debug detail level" is set as "Normal" and "Job Logs" is set as "High" in "Backup Exec Server" section, and "Catalog debugging detail level" is set as "High (not recommended) -5 in "Catalog debug settings" section, the following errors appear in <Computername>-SGMon.log on Backup Exec server.

<Computername>-SGMon.log>
BESERVER: [MM/DD/YY HH:MM:SS] [<TID>] -1 GetSourceImageID() ERROR: script.Get() failed!
BESERVER: [MM/DD/YY HH:MM:SS] [<TID>] -1 GetSourceImageID() returning idSourceImage={00000000-0000-0000-0000-000000000000}
BESERVER: [MM/DD/YY HH:MM:SS] [<TID>] -1 taskBalancerInfo() TASK_SETCOPY: bIsLinkedB2VJob=0
BESERVER: [[MM/DD/YY HH:MM:SS] [<TID>] -1 CWorkItem::taskBalancerInfo(JOBNAME) IsDJMManager()=0, PolicyID==GUID_NULL=0, *GetLinkedJobID()==GUID_NULL=0