cancel
Showing results for 
Search instead for 
Did you mean: 

Online Catalog Backups failing with status 2 and 25

dami
Level 5

My online catalog backups now fail with this message

 

12/08/2008 17:00:42 - requesting resource tedc-xn-nbm01.NBU_CATALOG.MAXJOBS
12/08/2008 17:00:42 - granted resource tedc-xn-nbm01.NBU_CATALOG.MAXJOBS
12/08/2008 17:00:42 - begin Parent Job
12/08/2008 17:00:42 - begin Catalog Backup , DBM Query
Status 2
12/08/2008 17:14:20 - end Catalog Backup , DBM Query; elapsed time: 00:13:38
Status 2
12/08/2008 17:14:20 - end Parent Job; elapsed time: 00:13:38
none of the requested files were backed up(2)

 

And

 

 

Child job:

12/08/2008 11:42:04 - requesting resource tedc-xn-nbm01-hcart2-robot-tld-0

12/08/2008 11:42:04 - requesting resource tedc-xn-nbm01.NBU_CLIENT.MAXJOBS.tedc-xn-nbm01

12/08/2008 11:42:04 - requesting resource tedc-xn-nbm01.NBU_POLICY.MAXJOBS.Online-NBU-Catalogs

12/08/2008 11:42:05 - granted resource tedc-xn-nbm01.NBU_CLIENT.MAXJOBS.tedc-xn-nbm01

12/08/2008 11:42:05 - granted resource tedc-xn-nbm01.NBU_POLICY.MAXJOBS.Online-NBU-Catalogs

12/08/2008 11:42:05 - granted resource 0059JB

12/08/2008 11:42:05 - granted resource IBM.03592E05.003

12/08/2008 11:42:05 - granted resource tedc-xn-nbm01-hcart2-robot-tld-0

12/08/2008 11:42:05 - started process bpbrm (4176)

12/08/2008 11:42:05 - connecting

12/08/2008 11:48:05 - Error bpbrm(pid=4176) listen for client protocol error - couldn't accept from data socket, The operation completed successfully. (0)

12/08/2008 11:48:06 - end writing

cannot connect on socket(25)

 

This is a 6.0MP5/W2K3 system which was rebuilt last week after a corrupted upgrade attempt to 6.5.x ... Offline catalog backups work fine, backups work fine .... I've opened a call with Symantec and await their input. Wandering if anyone has seen this b4.

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

dami
Level 5

solved ... After much much scrapping around with Symantec ... saw that bpclntcmd -pn was not working on the master server. After another 24 hrs realised that the hosts file was causing it. Lesson sometimes good to temporarily rename the hosts file and try again to see if there is a problem with it.

 

 

View solution in original post

2 REPLIES 2

dami
Level 5

solved ... After much much scrapping around with Symantec ... saw that bpclntcmd -pn was not working on the master server. After another 24 hrs realised that the hosts file was causing it. Lesson sometimes good to temporarily rename the hosts file and try again to see if there is a problem with it.

 

 

Rakesh_Khandelw
Level 6
Thanks for posting the solution.