Video Screencast Help

Jobs "On Hold" still run, BE 2014 14.1 Rev.1786

Created: 21 Aug 2014 | 1 comment

We moved to BE 2014, mainly to have the option to include all of our servers in a single backup job. I created the new job, submitted it, and placed all of our other scheduled jobs on hold. Now the new job is running, however all of our other jobs, though on hold, still run as well. I am seeing in the job history that these jobs have run since being placed on hold, and I go into the "jobs" tab and verify their status is "On Hold", and if I right-click on them, "Hold" is checked. What gives? The only thing I can think of is that our new job had possibly started before all of the other jobs were placed on hold. Do I actually have to wait until this new job is complete before the others will actually go "On Hold?"


Operating Systems:

Comments 1 CommentJump to latest comment

CraigV's picture

That shouldn't BE 2014 fully patched?

If so, I would suggest logging a call with Symantec to get this investigated as previous versions used to keep jobs on hold.


Alternative ways to access Backup Exec Technical Support: