02-25-2014 11:39 AM
Win 2008 r2 x64
NBU 7.1
Accessing the UNC path from the NBU Master/Media server " netbackup-01ny"
Large Shares:
\\file-03ny\redirect-adm$\Dead-My-Docs
\\file-03ny\redirect-adm$\RedirectFolders
Attached is bpbrm log
I am trying to backup, over the network via UNC path a couple of large file systems. We're eventually moving away from this method of backup but I need it for a little while.
I did the following to get basic UNC path backups working (changing the account that the services run as):
http://www.symantec.com/connect/blogs/netbackup-error-when-using-unc-path-storage-unit-absolute-pathname
At this point I can backup small shares or single files via UNC path but I get the following error when I am doing larger files.
I increased the timeout periods:
Host Properties>Master Servers>Timeouts
Client connect timeouts: 1000 seconds
Backup star notify timeout: 500 seconds
File browse timeout: 10,000 seconds
Client read timeout: 1000 seconds
Backup end notify timeouts: 500 seconds
Media server connect timeout: 60 seconds
Clients>Master Servers>Timeouts
Client read timeout: 10,000 seconds
File browse timeout: 10,000 seconds
Host Properties>Master Servers>Client Attributes>netbackup-01ny.hq.hview.com
Windows Open File Backup: off
Solved! Go to Solution.
02-25-2014 12:17 PM
02-25-2014 12:17 PM
02-25-2014 12:18 PM
(bpbrm readline: socket read failed, An existing connection was forcibly closed by the remote host. (10054)
10053 and 10054 are related to network timeout issues
Please make Client Read out time as 3600 and try running the backup again
02-25-2014 01:08 PM
It fails almost instantly so timeouts do not look to be the issue
I am assuming that the account you have set the client service (and maybe the netbackup legacy client network service) to use has full rights to those locations?
Do the smaller shares you backup point to "real" shares?
I am wondering if admin shares will not get passed to NetBackup correctly
If possible back up the share rather than the admin share... so something like the below (no $):
\\file-03ny\folders\RedirectFolders
rather than
\\file-03ny\redirect-adm$\Dead-My-Docs
\\file-03ny\redirect-adm$\RedirectFolders
02-25-2014 01:11 PM
The error occurs to quickly to be a read timeout.
Have you tried running bpbkar -nocont on the UNC path?
http://www.symantec.com/business/support/index?page=content&id=TECH17541
02-25-2014 01:15 PM
I tried both the admin share and regular shares. When I didn't see a difference I put it back to the admin shares.
I've done this type of backup months ago on a different NBU master server. So I am pretty sure that admin shares are ok.
The account used for the services has full access to the volume. That part has been confirmed by a couple people over here.
02-25-2014 01:16 PM
I increased all the time outs to 10,000 but it did not make a difference.
02-25-2014 01:17 PM
I will attempt option 4 tonight and report back.
02-25-2014 01:19 PM
Ok - setup bpbrm, bpcd and bpbkar logs and run it again - then post thise logs as attachments so that we can try and spot something
Could we also see the policy output: bppllist policyname -U
Thanks
02-25-2014 02:51 PM
I agree with revaroo - try a bpbkar -nocont on the UNC path - to isolate whether the issue is with reading the file system.
02-25-2014 09:39 PM
Also set the client_read and client_connect time outs to 900 seconds each. Enable the bpbkar log on the client and run the bpbkar to null. I would say over 80% of the time the problem is the client with UNC backups.
02-26-2014 12:00 AM
I agree with Mark - it fails within a few seconds. So, the issue is not with timeout:
2/25/2014 10:57:35 AM - begin writing2/25/2014 10:57:37 AM - Error bpbrm(pid=5528) socket read failed, An existing connection was forcibly closed by the remote host. (10054)
02-26-2014 06:43 AM
This looks like it is working. I went with option 4. the backups are still running and it's been a couple of hours. I am waiting to see if the backups complete.
I will keep you updated.
02-26-2014 02:21 PM
So option 4 seems to be working. The backups have completed.
Should I set all the time-outs back to the default 300 seconds? Or should I leave them very high ?
02-26-2014 09:40 PM
Please mark sdo's post as solution.
Yes, drop down Timeouts.
As we have pointed out above - the issue was never with timeouts.