Incremental backup job doesn't run and is set to 'Superseded' status if full backup job with no recurring schedule is suspended after it is performed
Created: 13 Nov 2012 | Updated: 13 Nov 2012 | 1 comment
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.
The job can be suspended via BEMCLI with the following commands:
BEMCLI> Get-BEJob "Job-Name-Full" | Start-BEJob -Confirm:$False | Wait-BEJob ; Get-BEJob "Job-Name-Full" | Suspend-BEJob
Please be noted that this issue reproduces only when a full backup job does not have recurring schedule.
This issue is currently under investigation by Symantec Corporation. For more information please check the following article.
http://www.symantec.com/docs/TECH199662
Known Issue Filed Under:
Comments 1 Comment • Jump to latest comment
Is this occurring continuous for next schedule also?...
If No!!! My suggestions to check Master server Global Properties (number of occurred jobs in 12 hours)
Would you like to reply?
Login or Register to post your comment.