Video Screencast Help

Fix Netbackup so that cancelling a job really cancels a job (No Matter what!)

Created: 15 Oct 2009 • Updated: 20 Oct 2010 | 6 comments
Fred2010's picture
35 Agree
0 Disagree
+35 35 Votes
Login to vote
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?

Comments 6 CommentsJump to latest comment

TimBurlowski's picture

 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

Login to vote
Fred2010's picture

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!

Login to vote
alazanowski's picture

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.

Login to vote
Genericus's picture

I have the windows admin available, since there are times that the JAva GUI leaves orphan jobs with nothing in them, and I can only clear them with the windows admin.

NetBackup on Solaris 10
EMC Data Domain 990 & 7200 VTL via FC
acsls 8.3.0
SL500 & SL8500 LTO5

Login to vote