cancel
Showing results for 
Search instead for 
Did you mean: 

The status of hot catalog job (parent job) is running (all the time) and did not stop

brant
Level 3
Employee
When I upgrade AIX5.3(5300-06-01) to a new level (now is 5300-07-08-0918), then occured this problem:
  If I start a hot catalog backup job, the parent still running all the time after its child jobs finished.

So could someone tell me how to fix the AIX problem?
Thank you all.

1 ACCEPTED SOLUTION

Accepted Solutions

brant
Level 3
Employee
Thank you all.
I resolve this issue from http://seer.entsupport.symantec.com/docs/292450.htm.
Thanks.

View solution in original post

4 REPLIES 4

Sriram
Level 6
I dont think AIX upgrade would be an issue but

Dont go for any conclusion before you are 100% sure. 

Try this first:

Go back to the old version of AIX and check if the catalog job completes fine.  Isolate if the AIX upgrade caused the issue with netbackup catalog backup.

Then:

If the first did'nt works out.  Restart the netbackup services and recreate the catalog policy and check

Hope this helps

Abesama
Level 6
Partner
Symantec's compate guide only mentions ML4 showing some issues...

ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/325328.pdf

If working on AIX version change is not easy/possible, try looking at debug log.

Enable nbjm/nbpem/bpbrm logs and increase verbose level, run the job, review it using vxlogview command and check out /usr/openv/netbackup/logs/bpbrm directory.

Interesting - are other multiple-stream jobs running ok?

Hot catalog backup job (especially the part where the job wraps up) is not any more than a simple multiple stream backup job...

Abe

brant
Level 3
Employee
Thank you all.
I resolve this issue from http://seer.entsupport.symantec.com/docs/292450.htm.
Thanks.

Raghuraam
Level 4
Raghuraam