cancel
Showing results for 
Search instead for 
Did you mean: 

SQL Dabase backup fails while filesystem is fine

bal2
Level 3

Friends, 

I could use your help here, I have SQL server with Filesystem and Database backup (through script) configured. Filesystem backup is sucessful while dabase backup fails. Please advise @Marianne 

Mar 8, 2021 12:14:13 PM - Error bprd (pid=15236) Unable to write progress log </C/ProgramÀ Files/Veritas/NetBackup/Logs/user_ops/dbext/logs/48388.0.1615191072> on client XXXX. Policy=EVSQLDB-Backup Sched=NONE
Mar 8, 2021 12:14:15 PM - Error bprd (pid=15236) CLIENT XXXX  POLICY EVSQLDB-Backup  SCHED NONE  EXIT STATUS 25 (cannot connect on socket)

 

8 REPLIES 8

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

Database backup needs comms between master and client in addition to media server and client comms.

Ensure forward and reverse name lookup between master and client as well as port connectivity on pbx (port 1556) .

Test comms between master server and client with bptestbpcd on master:
bptestbpcd -client <clent-name> -verbose -debug

Run bpclntcmd command on client that initiates connection to the master:
bpclntcmd -pn

pats_729
Level 6
Employee

Hi @bal2 

Can you provide following details

MSSQL Version

NBU Version ?

How is SQL Policy Configured ? Script or Intelligent.

If its a script then provide a copy of it here.

 

 

L_BR
Level 5

Can you connect to the DB from the master server?

Open the Admin console

Select Applications on the left pane

Select Microsoft SQL Server

You can try to discover new instances or add the instance yourself. If SQL can be queried, you have permissions in SQL, if not, use an account that has the correct permissions in SQL to query and connect to the database.

If you don't have the user info, you can get the DB Admins to change the following services to use a MSSQL SA account:

Netbackup Client Service

Netbackup Legacy Client Service

Netbackup Legacy Network Service

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@bal2 

I just noticed this:  Policy=EVSQLDB-Backup 

Does this mean that you are backing up the Enterprise Vault SQL database with MS-SQL policy type?

Are you aware that the EV database should be backed up with EV policy that backs up EV data and database?

Documentation:
https://www.veritas.com/support/en_US/article.100006827
https://www.veritas.com/support/en_US/article.100007570

 

Thank you @Marianne  as always.

I have tested communication is ok , filesystem backup is also working well. 

Here is output for command , please let me know if this helps. 

bptestbpcd -client <clent-name> -verbose -debug

D:\Program Files\Veritas\NetBackup\bin\admincmd>bptestbpcd -client -
verbose -debug

13:46:47.970 [11032.24580] <2> bptestbpcd: VERBOSE = 0
13:46:47.970 [11032.24580] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1889: pseudo PN for : XXXX
13:46:47.970 [11032.24580] <2> read_client: dname=., offline=0, online_at=0 offl
ine_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
13:46:47.970 [11032.24580] <2> read_client: dname=.., offline=0, online_at=0 off
line_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
13:46:47.970 [11032.24580] <2> read_client: dname=CO_0, offline=0, online_at=0 o
ffline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
13:46:47.970 [11032.24580] <2> read_client: dname=host_info, offline=0, online_a
t=0 offline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
13:46:47.970 [11032.24580] <2> read_client: dname=OA_0, offline=0, online_at=0 o
ffline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0
13:46:47.985 [11032.24580] <2> check_vnetd_process_dup_permission: OpenProcessTo
ken() failed: 5
13:46:47.985 [11032.24580] <2> vnet_check_windows_privileges: enabled SeDebugPri
vilege privilege
13:46:48.001 [11032.24580] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1889: pseudo PN for : XXXX
13:46:48.001 [11032.24580] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1889: pseudo PN for : XXXX
13:46:48.001 [11032.24580] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1889: pseudo PN for : XXXX
13:46:48.001 [11032.24580] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1889: pseudo PN for : XXXX
13:46:48.017 [11032.24580] <2> vnet_pbxConnect_ex: pbxConnectExEx Succeeded
13:46:48.017 [11032.24580] <4> create_user_group_id_marker_WIN: connecting to na
med pipe:\\.\pipe\{68D81602-BE2A-4148-A7B6-111D3F1B0C3A}:OUTBOUND
13:46:48.017 [11032.24580] <4> create_user_group_id_marker_WIN: successfully con
nected to server named pipe
13:46:48.048 [11032.24580] <2> logconnections: BPCD CONNECT FROM BACKUPSERVERIP.5209
6 TO 10.4.3.134.1556 fd = 568
13:46:48.048 [11032.24580] <2> vnet_connect_to_vnetd_bpcd: js_bpcd_info: 0000000
0028C31E0
13:46:48.063 [11032.24580] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1889: pseudo PN for : XXXX
13:46:48.110 [11032.24580] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1889: pseudo PN for : XXXX
13:46:48.110 [11032.24580] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1889: pseudo PN for : XXXX
13:46:48.110 [11032.24580] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1889: pseudo PN for : XXXX
13:46:48.142 [11032.24580] <2> vnet_pbxConnect_ex: pbxConnectExEx Succeeded
13:46:48.235 [11032.24580] <4> create_user_group_id_marker_WIN: connecting to na
med pipe:\\.\pipe\{A1C12646-7A48-4903-974C-9FE7B88CF96C}:OUTBOUND
13:46:48.251 [11032.24580] <4> create_user_group_id_marker_WIN: successfully con
nected to server named pipe
13:46:48.267 [11032.24580] <8> do_pbx_service: [vnet_connect.c:2600] via PBX VNE
TD CONNECT FROM BACKUPSERVERIP.52108 TO SQLSERVERIP.1556 fd = 576
13:46:48.267 [11032.24580] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vn
etd.c:458] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
13:46:48.282 [11032.24580] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vn
etd.c:483] ipc_string 50507
13:46:52.782 [11032.24580] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1889: pseudo PN for : XXXX
13:46:52.798 [11032.24580] <2> bpcr_get_version_rqst: bpcd version: 08000000
1 1 1
BACKUPSERVERIP:52096 -> SQLSERVERIP:1556
BACKUPSERVERIP:52108 -> SQLSERVERIP:1556
13:46:52.813 [11032.24580] <2> bpcr_get_version_rqst: bpcd version: 08000000
13:46:52.813 [11032.24580] <16> bpcr_get_domain_ctx_rqst: connected bpcd version
0x08000000 is less than required version 0x08100000
13:46:52.829 [11032.24580] <2> bpcr_get_peername_rqst: Server peername length =
27
13:46:52.860 [11032.24580] <2> bpcr_get_hostname_rqst: Server hostname length =
26
13:46:52.876 [11032.24580] <2> bpcr_get_clientname_rqst: Server clientname lengt
h = 26
13:46:52.892 [11032.24580] <2> bpcr_get_version_rqst: bpcd version: 08000000
13:46:52.907 [11032.24580] <2> bpcr_get_platform_rqst: Server platform length =
7
13:46:52.923 [11032.24580] <2> bpcr_get_version_rqst: bpcd version: 08000000
13:46:52.954 [11032.24580] <2> bpcr_patch_version_rqst: theRest == > <
13:46:52.954 [11032.24580] <2> bpcr_get_version_rqst: bpcd version: 08000000
13:46:52.985 [11032.24580] <2> bpcr_patch_version_rqst: theRest == > <
13:46:52.985 [11032.24580] <2> bpcr_get_version_rqst: bpcd version: 08000000
PEER_NAME = masterserver
HOST_NAME = mediaserver
CLIENT_NAME = sqlclient
VERSION = 0x08000000
PLATFORM = win_x64
PATCH_VERSION = 8.0.0.0
SERVER_PATCH_VERSION = 8.0.0.0
MASTER_SERVER = v-cs0-dc-nbs
EMM_SERVER = v-cs0-dc-nbs
NB_MACHINE_TYPE = CLIENT
SERVICE_TYPE = UNKNOWN
PROCESS_HINT =
13:46:53.048 [11032.24580] <2> vnet_connect_to_vnetd_bpcd: js_bpcd_info: 0000000
0028C2EE0
13:46:53.048 [11032.24580] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1889: pseudo PN for : XXXX
13:46:53.048 [11032.24580] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1889: pseudo PN for : XXXX
13:46:53.048 [11032.24580] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1889: pseudo PN for : XXXX
13:46:53.048 [11032.24580] <2> copy_preferred_network_list: ../../libvlibs/nbcon
f.c.1889: pseudo PN for : XXXX
13:46:53.079 [11032.24580] <2> vnet_pbxConnect_ex: pbxConnectExEx Succeeded
13:46:53.204 [11032.24580] <4> create_user_group_id_marker_WIN: connecting to na
med pipe:\\.\pipe\{CB16F68C-46EA-40AE-A103-02035F36B9D1}:OUTBOUND
13:46:53.204 [11032.24580] <4> create_user_group_id_marker_WIN: successfully con
nected to server named pipe
13:46:53.220 [11032.24580] <8> do_pbx_service: [vnet_connect.c:2600] via PBX VNE
TD CONNECT FROM BACKUPSERVERIP.52132 TO SQLSERVERIP.1556 fd = 580
13:46:53.235 [11032.24580] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vn
etd.c:458] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa
13:46:53.235 [11032.24580] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vn
etd.c:483] ipc_string 50509
BACKUPSERVERIP:52132 -> SQLSERVERIP:1556
<2>bptestbpcd: EXIT status = 0
13:46:53.298 [11032.24580] <2> bptestbpcd: EXIT status = 0

@Marianne 

I am afraid we have had this setup from sometime, however thank you for documents, I will try to change this. 

@L_BR 

Thank you for helping, I will get these all check and report. 

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@bal2 

What about 'bpclntcmd -pn' on the client?

If this has been running fine for some time, then basic comms are probably fine.

This means that you need to check logs -
bprd on the master (if bprd log folder does not exist, you need to create it and restart NBU)
dbclient log on SQL server - level 3 should be fine.