Incremental backup job doesn't run and is set to 'Superseded' status if full backup job with no recurring schedule is suspended

Article:TECH199662  |  Created: 2012-11-13  |  Updated: 2014-03-24  |  Article URL http://www.symantec.com/docs/TECH199662
Article Type
Technical Solution


Subject

Issue



If a full backup job with no recurring schedule is suspended after it is performed, the subsequent incremental/differential backup job does not run and the job status is set to 'Superseded' when the scheduled time comes.

This problem occurs only when suspending the full backup job via BEMCLI with the following commands:

BEMCLI> Get-BEJob "Job-Name-Full" | Suspend-BEJob


Solution



A hotfix is now available for this issue in the current version(s) of the product(s) mentioned in this article. Refer to the Hotfix link under Related Documents at the end of this article to obtain the hotfix needed to resolve the issue.

 

Backup Exec 2012 Rev 1798 Service Pack 3 (TECH205351).

 

Note that with Backup Exec 2012 Service Pack 3, Suspend-BEJob fails with 'Completed jobs cannot be placed on hold' error when suspending One-Time backup jobs or Full backup jobs with no recurring schedule which have already been completed. Please refer to TECH212652 for details.


Supplemental Materials

SourceETrack
Value2994973
Description

CORE: Incremental/Differential backup job does not run and is set to 'Superseded' status if full backup job with no recurring schedule is suspended after it is performed




Article URL http://www.symantec.com/docs/TECH199662


Terms of use for this information are found in Legal Notices