04-05-2012 07:30 PM
Hi
Reference: https://www-secure.symantec.com/connect/forums/mailbox-restore-fails-invalid-error-number2826
I am getting same error 2826 while restoring on Linux client .It is dispalying the error
4/5/2012 12:24:37 PM - Error bptm(pid=13460) cannot write data to socket, Broken pipe
4/5/2012 12:24:37 PM - Error bptm(pid=13460) The following files/folders were not restored:
4/5/2012 12:24:37 PM - Error bptm(pid=13460) UTF - /dcs/arch01/ARC/ERI/Mar_2012/MSEMR03201203130957551503.dat.gz
4/5/2012 12:24:38 PM - Info bpbrm(pid=13451) media manager for backup id gnnmed25_1333259894 exited with status 24: socket write failed
4/5/2012 12:24:38 PM - Info bpbrm(pid=13451) terminating bpbrm child 13463 jobid=2014589
4/5/2012 12:24:38 PM - restored image gnnmed25_1333259894 - (socket write failed(24)); restore time 01:18:28
4/5/2012 12:24:39 PM - end Restore; elapsed time: 01:19:12
invalid error number(2826).
please help on the same
Rajkumar Baniwal
backup support
***** Moved to new discussion by MvdB ******
Solved! Go to Solution.
04-25-2012 08:27 PM
It is resolved after changing the same client as SAN media server and restoring through the same media server
04-05-2012 08:01 PM
You have probably noticed in the discussion where you originally posted that we have asked for additional info but never received anything.
The 'real' error in your instance seems to be status 24.
Please share all relevant info for your environment:
OS on Master server and media server
OS on Client (Which Linux 'flavour' and version)
NBU version (and patch level) on master, media server and client
Any firewall between master and media server or between media server and client?
We can see that the restore failed after 1 hour. We sometimes see that firewall timeouts will terminate connection. Was any data actually written to client?
Please share all text in Activity Monitor details as well as the info in 'View Status' tab of the restore GUI.
Also post following logs as attachments (if they do not exist, please create them and retry the restore):
On master: bprd (restart NBU after creating this log)
On media server: bpbrm and bptm
On client : bpcd and tar
Please rename logs to match process name and post them as attachments.
04-06-2012 02:46 PM
PFB
OS on Master server and media server SUN Solaris OS 5.10
OS on Client (Which Linux 'flavour' and version) Linux 2.6.18-164.el5
NBU version (and patch level) on master, media server and client 7.1.0.3
Any firewall between master and media server or between media server and client? No
Was any data actually written to client? No
Alttached all logs fo reference.
Thanks and regards
Rajkumar Baniwal
04-06-2012 04:14 PM
I'm a bit confused,
The restore starts at around 11:06 (from job details we can match the PID)
From media server bpbrm log
11:06:10.726 [13451] <2> logparams: -restore -mpx_restore -S gnnbkp01 -mt 2 -to 32767 -mud 180 -mediasvr gnnbkp01 -masterversion 710000
04-07-2012 07:17 AM
Have you check if the iptables (firewall) service is on? most of the socket errors I see in linux are because iptables are filtering big blocks by default, the rest of your applications can work perfectly but because netbackup needs big blocks is the one that most of the time fails.
try: service iptables status (if is on)
try: service iptables stop (run a backup)
Regards.
04-11-2012 10:28 PM
Firewall is blocked. but we are getting same error
04-12-2012 12:21 AM
6 April:
Any firewall between master and media server or between media server and client? No
12 April:
Firewall is blocked.
Nothing is going to work with blocked firewall.
04-12-2012 01:36 AM
04-25-2012 08:27 PM
It is resolved after changing the same client as SAN media server and restoring through the same media server