Quantcast
Channel: Symantec Connect - Backup and Recovery - Discussions
Viewing all articles
Browse latest Browse all 6307

error 130 after updating linux client to v7.6.0.4

$
0
0
I need a solution

hi,

I updated both server and client nbu versions from v7.6.0.1/2 to v7.6.0.4 ... 

most clients did their job good but there are three linux clients which end up in an "error 130" when backing up.

"

1424955661 1 1 4 hellboy 0 0 0 *NULL* nbjm backup job submission request (jobid=614558) for client peppone, policy fit_unix, schedule Full
1424955662 1 4 4 hellboy 614558 614558 0 peppone nbjm started backup job for client peppone, policy fit_unix, schedule Full on storage unit jbod2008
1424955665 1 4 16 hellboy 614558 614558 0 peppone bpbrm BMRERR: Received BMR error: Failed to discover System. (12)
1424955665 1 4 16 hellboy 614558 614558 0 peppone bpbrm BMRERR: Received BMR error: BMR information discovery failed. (35)
1424955665 1 4 16 hellboy 614558 614558 0 peppone bpbrm BMRERR: Did not receive bmr client request from peppone, status = 0
1424955665 1 1 4 hellboy 0 0 0 *NULL* nbjm backup job submission request (jobid=614559) for client peppone, policy fit_unix, schedule Full
1424955665 1 1 4 hellboy 0 0 0 *NULL* nbjm backup job submission request (jobid=614560) for client peppone, policy fit_unix, schedule Full
1424955665 1 1 4 hellboy 0 0 0 *NULL* nbjm backup job submission request (jobid=614561) for client peppone, policy fit_unix, schedule Full
1424955665 1 4 4 hellboy 614559 614558 0 peppone nbjm started backup job for client peppone, policy fit_unix, schedule Full on storage unit jbod2008
1424955666 1 4 4 hellboy 614560 614558 0 peppone nbjm started backup job for client peppone, policy fit_unix, schedule Full on storage unit jbod2009
1424955668 1 4 32 hellboy 614559 614558 0 peppone bpbrm from client peppone: FTL - terminated by signal 11
1424955669 1 4 32 hellboy 614560 614558 0 peppone bpbrm from client peppone: FTL - terminated by signal 11
1424955673 1 65536 4 hellboy 614559 614558 0 peppone bptm VBRC 2 17328 1 peppone_1424955665 0 fit_unix 0 Full 0 1 1
1424955673 1 65536 4 hellboy 614560 614558 0 peppone bptm VBRC 2 17329 1 peppone_1424955666 0 fit_unix 0 Full 0 1 1
1424955674 1 1668 4 hellboy 614559 614558 0 peppone bptm begin writing backup id peppone_1424955665, copy 1, fragment 1, destination path /jbod2008/dssu
1424955674 1 4 4 hellboy 614559 614558 0 peppone bptm no data received from client peppone, image not written
1424955674 1 1668 4 hellboy 614560 614558 0 peppone bptm begin writing backup id peppone_1424955666, copy 1, fragment 1, destination path /jbod2009/dssu
1424955674 1 4 4 hellboy 614560 614558 0 peppone bptm no data received from client peppone, image not written
1424955675 1 4 16 hellboy 614559 614558 0 peppone bpbrm cannot send mail to root on client peppone
1424955675 1 68 4 hellboy 614559 614558 0 peppone nbpem CLIENT peppone  POLICY fit_unix  SCHED Full  EXIT STATUS 130 (system error occurred)
1424955675 1 4 16 hellboy 614559 614558 0 peppone nbpem backup of client peppone exited with status 130 (system error occurred)
1424955675 1 4 16 hellboy 614560 614558 0 peppone bpbrm cannot send mail to root on client peppone
1424955675 1 68 4 hellboy 614560 614558 0 peppone nbpem CLIENT peppone  POLICY fit_unix  SCHED Full  EXIT STATUS 130 (system error occurred)
1424955675 1 4 16 hellboy 614560 614558 0 peppone nbpem backup of client peppone exited with status 130 (system error occurred)

"

this is a debian 7.8 client, another SuSE linux client also produces this error... after downgrading to v7.6.0.1 the backup runs fine. I also tried a clean client software installation by deleting /usr/openv/ completely or moving away. 

can anyone tell me whether this is a known error? many other debian linux clients (also debian 7.8) didn't fail and run fine with version v7.6.0.4 ... so I am a little bit confused what is wrong... 

thanks in advance... 


Viewing all articles
Browse latest Browse all 6307

Trending Articles