After upgrade to 6.5.5 jobs will not go active and complete

After upgrading from 6.5.3 to 6.5.5, jobs are not running.  They will kick off but and a few will run and then after a short time no jobs will go active.  Jobs just sit queued or in an active state but unproductive.  Has anyone ran into issues like this after upgrading to 6.5.5?
1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

I'm wondering if you might be


I'm wondering if you might be experiencing the problem explained in this TechNote:

http://seer.entsupport.symantec.com/docs/345892.htm

BUG REPORT: In NetBackup versions 6.5.4 and 6.5.5 the nbjm log shows PBX attempting to use interfaces that are not defined in the bp.conf with SERVER entries.
....
The above behavior may cause very large delays in processing information from the JM CallbackQueue, which in turn may result in many backup jobs being in a queued state.

View solution in original post

9 Replies
Highlighted

Have you tried restarting the

Have you tried restarting the Netbackup services after upgrade.

If not ,

Please try if windows Veritas\NetBackup\bin>bpdown -v -f

once its get completely down run the command bpup -v -f

Highlighted

We are running on Solaris and

We are running on Solaris and we did restart the master and all media servers after the upgrade. We also tried killing all jobs, running an nbrbutil -dump and it was clean, we did a resetAll anyway and restarted the environment again. Immediately after the upgrade, jobs will kick off and complete for about 1 phase.   After that, jobs just sit in the monitor and do nothing. We are seeing a lot of issues with anything connecting to emm.  commands are reporting 800 error resource unavailable, some of the jobs that do complete writing the backup report a 71 at the end of the backup and report Error bptm (pid=2302132) cannot add fragment to image database, error = network connection timed out.
Highlighted

Hi there


that kick off mean that the policy is deactivated?


try
nbpemreq -updatepolicies
that will show U the furure jobs

I had a GREAT problem w/ the daylight saving here, look for the date.

my nb server has outomatically updated time .. but 1 month and 1 hour... all jobs has gone ok for 1 day..
when I set the rign date .. all jobs was waiting to next run 1 1 month.




Highlighted

Error reporting 800 is due to

Error reporting 800 is due to drive unable , it may happen if the drives are not configured properly or any mismatch.  After upgrades sometimes it may need to reconfigure drives .

Please try to reconfigure drives for one of the media server and try backup on that and verify ...
Highlighted

we had the same kinda problem


we had the same kinda problem but on windows boxes

restart of the services and installing the driver again fixed the problem
Highlighted

Have you confirmed in the


Have you confirmed in the patch installation logs that the installation was 100% successful? We have quite a number of customers on 6.5.5 (mostly Solaris) and have not seen any problems after the patch install.
Highlighted

Has your upgrade resulted in "space issues"?

If space becomes a premium in the install directory it can start to cause anomalous failures etc.

If so, have a look in the 'pack' directory per this rather old T/N:
http://seer.entsupport.symantec.com/docs/280824.htm
Highlighted

Have you checked your Storage

Have you checked your Storage Units after the upgrade? Check that they haven't reset to Media Server = ANY. This has happened to me a fair few times in the past.
Highlighted
Accepted Solution!

I'm wondering if you might be


I'm wondering if you might be experiencing the problem explained in this TechNote:

http://seer.entsupport.symantec.com/docs/345892.htm

BUG REPORT: In NetBackup versions 6.5.4 and 6.5.5 the nbjm log shows PBX attempting to use interfaces that are not defined in the bp.conf with SERVER entries.
....
The above behavior may cause very large delays in processing information from the JM CallbackQueue, which in turn may result in many backup jobs being in a queued state.

View solution in original post