Trying to backup sql db's. Small clip from dbclient. Remote registry is running.
09:24:45.360 [1256.6648] <16> writeToServer: ERR - send() to server on socket failed: 09:24:45.360 [1256.6648] <16> dbc_RemoteWriteFile: ERR - could not write progress status message to the NAME socket 09:24:45.360 [1256.6648] <4> getServerName: Read server name from nb_master_config: netbmngr.xxxx.xxx.xx 09:24:45.375 [1256.6648] <2> vnet_pbxConnect: pbxConnectEx Succeeded 09:24:45.375 [1256.6648] <2> logconnections: BPRD CONNECT FROM 192.168.101.212.54658 TO 192.168.1.212.1556 fd = 1300 09:24:49.306 [1256.6648] <16> writeToServer: ERR - send() to server on socket failed: 09:24:49.306 [1256.6648] <16> dbc_RemoteWriteFile: ERR - could not write progress status message to the NAME socket 09:24:49.306 [1256.6648] <16> CDBbackrec::InitDeviceSet_Part2(): ERR - Error in GetConfiguration: 0x80770003.
Please find log files.
NBU master: 188.8.131.52 Windows 2008 r2
Solved! Go to Solution.
It reports a connection timeout so two possibilities
1. The SQL client and Master Server are having difficulties communication with each other
2. You need to increase the Client Read Timeout setting on your Master and Media Servers in their host propeties section - default is 5 minutes and that is where you get your timeout - try 1800 to start with and see how it goes (this is the most likely issue)
Hope this helps
Thanks for the reply.
I did increase the time out to 900 from 300 but it doesn't seem to have taken affect, any advice on this?
I'll look into the possibity of communication problems.
The timeout must be the Client Read Timeout and should be set on your Media Servers Host properties and not the clients host properties
This will need a service re-start on the media servers to take effect
The log will confirm it as it will say:
00:10:59.474 [5284.3172] <4> CDBbackrec::InitDeviceSet(): INF - Created VDI object for SQL Server instance <Assurasql1>. Connection timeout is <300> seconds.
That should be 900 of the settings have taken
SQL backups are one of the very few where the client talks directly to the Master server as well as the Media severs which is why communication is important there
I've changed the value, trying both doing from master server and from the media server, ran bpdown/bpup, restarted the client service on the sql host and it still won't change! I've ran into this before and I don't think I sorted it then either!
Any ideas what I may be doing wrong?
Ok - try changing it on the clients host properties too and re-start its client service again
Having said that it wouldn't hurt to upgrade to 184.108.40.206 all round to eliminate any potential bugs
There were some hardcoded timeouts increased for bpcd and bpdbm in one of the last releases so it that may help