cancel
Showing results for 
Search instead for 
Did you mean: 

SQL backup status 46

Will_Restore
Level 6

Reviewed prior threads on Status 46 but did no see solution to this particular issue. 

SQL backups running finie for months until this past weekend.  Of course "nothing has changed". 

Noted in dbclient log for the failed jobs the image names preceded by slash '/' as in /NODENAME.MSSQL7.CLUSTERNAME.db.DBNAME...

Can't figure out where that slash is coming from. 

 

13 REPLIES 13

sdo
Moderator
Moderator
Partner    VIP    Certified

Recent Windows update?

> wmic qfe list brief

...and filter / sort by dates?  What was installed between the dates of last good working, and first now broken, backup?

Will_Restore
Level 6

Thanks for that command.  So there were some KB updates on 5/17.  But the backups failed 5/16. 

 

sdo
Moderator
Moderator
Partner    VIP    Certified

Did the backups finish before the date-time of the installs?

(can you tell whether I'm clutching at straws... :p)

...and I googled 'netbackup sql slash' and it would seem that extra '/' or '\' is bit of a theme?  Red herring though?

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Sounds like a glitch or a change in DNS....
Where exactly is the status 46 coming from? SQL client?

All I can suggest is to troubleshoot as normal status 46:

C:\>bperror -S 46 -r
server not allowed access
The server tries to access a client, but access is blocked.
Possible causes are as follows:
* The server is not listed on the client as a valid server. 

Do you have bpcd on the client?

Will_Restore
Level 6

Name resolution looks fine, forward and back, Master <> Client <> Media

---------------

bpcd log snippet from yesterday (the one from 5/16 looks fine):

CLIENT is not a master server

CLIENT is not a media server either

...

exit status 46

---------------

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Is there a connection request from itself in bpcd?

Is CLIENT also a (SAN) media server?

Will_Restore
Level 6

Noticed in the client bpcd log for the successful job (prior week), it was the media server and client connecting at same point in the log, which was successful.

That snippet above the client was trying to connect to itself.  It is not a SAN media server.

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
No way we can offer advice without seeing what you see. That will include job details and full bpcd and dbclient logs. Maybe bprd on the master as well.

sdo
Moderator
Moderator
Partner    VIP    Certified

Will - could you be out of ports on client side:

> netstat -an | find /i /c "tcp"

...how many ports open?

.

Some example steps to query, and change, and reset:

reg query "HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" | find /i "MaxUserPort"

(FYI - the default is that it does not exist)

netsh int ipv4 show dynamicportrange udp

netsh int ipv4 show dynamicportrange tcp

netsh int ipv6 show dynamicportrange udp

netsh int ipv6 show dynamicportrange tcp

(FYI - the default for all four above is start: 49152 number: 16384)

(FYI - The following extended the range from 16384 ports to 20000 ports)

netsh int ipv4 set  dynamicportrange udp start=20000 number=45500

netsh int ipv4 set  dynamicportrange tcp start=20000 number=45500

netsh int ipv6 set  dynamicportrange udp start=20000 number=45500

netsh int ipv6 set  dynamicportrange tcp start=20000 number=45500

netsh int ipv4 show dynamicportrange udp

netsh int ipv4 show dynamicportrange tcp

netsh int ipv6 show dynamicportrange udp

netsh int ipv6 show dynamicportrange tcp

reg query "HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" /v "MaxUserPort"


FYI - THESE ARE NOTES ON HOW TO RESET TO DEFAULT:

netsh int ipv4 set  dynamicportrange udp start=49152 number=16384

netsh int ipv4 set  dynamicportrange tcp start=49152 number=16384

netsh int ipv6 set  dynamicportrange udp start=49152 number=16384

netsh int ipv6 set  dynamicportrange tcp start=49152 number=16384

reg delete "HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters" /v "MaxUserPort"

Will_Restore
Level 6

dbclient log now shows Status 18 CONNECT FAILED and Status 25 cannot connect on socket. 

"The license for the requested feature is not available"  :( 

Don't know what the server admins did but I'm going to try to remove/reinstall NetBackup Client. 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified
Connectivity problem with master server. Test connectivity as if this is a new installation. Verify forward and reverse name lookup as well as port connectivity on 1556 in both directions.

Will_Restore
Level 6

It had been working for months without issue per OP.   Works fine again after client reinstall.   

Very odd.  I've never seen so many weird errors from one client. 

Will_Restore
Level 6

Solved - removed & reinstalled NetBackup Client software (7.6.0.4).