Fix Netbackup so that cancelling a job really cancels a job (No Matter what!)
Updated: 20 Oct 2010 | 4 comments
Status:
In Review
We regularly notice that jobs can't be cancelled, unless we stop all services on Master and Media servers (BPDOWN)
Why can't jobs be cancelled no matter what, when an administrator cancels the job in the Netbackup GUI?
idea Filed Under:
Comments
Follow-up questions
I was reviewing this today with the NetBackup product management group. We were looking for more detail. Is there a kind of job where it seems slow? What version are you experiencing this with? Any more detail would help us work through this.
Technical Product Manger Symantec
Hi Tim, Sorry for the late
Hi Tim,
Sorry for the late answer: I've been out of the office a while...
What I mean is the following (We are running 6.0 and 6.5.5 in 2 separate environments btw):
When a job hangs (For whatever reason) it is sometimes impossible to cancel the job and clean it away after it has been canceled.
No matter what I try (And I hear this from others as well), some jobs can't be canceled, except when I boot the server (Or BPDOWN / BPUP).
I have no specific example when this happens, but I guess you must have encountered situations like that as well sometimes...
To test I sometimes have canceled a job that was seemingly hung, and waited until the next day, only to see it hadn't canceled!
I can confirm that this
I can confirm that this occurs in 6.5.5 and even in netbackup 7.0
-Austin Lazanowski Backups cost way too much until you needed them.
Looks like 7.1 as well
Looks like 7.1 as well
Would you like to reply?
Login or Register to post your comment.