Problem

STATUS CODE 21: After upgrading to Veritas NetBackup (tm) 6.0, backup jobs end in a Status 21 (socket open failed).

Error
socket open failed

Solution
Overview: After upgrading to NetBackup 6.0, backup jobs end in a Status 21 (socket open failed).

Troubleshooting: This symptom has been observed in environments where a firewall is configured and vnetd is in use prior to upgrading to NetBackup 6.0. In NetBackup 6.0, vnetd is enabled by default.

Log Files: bpbrm

11:41:09.344 [4360.1340] <2> vnet_async_connect: vnet_vnetd.c.3949: connect in progress: 0 0x00000000 11:41:09.406 [4360.1340] <2> version_connect: vnet_vnetd.c.1816: Function failed: 24 0x00000018 11:41:09.406 [4360.1340] <2> do_vnetd_service: vnet_vnetd.c.4317: version_connect failed: 24 0x00000018 11:41:09.406 [4360.1340] <2> vnet_async_connect: vnet_vnetd.c.4117: do_vnetd_service failed: 24 0x00000018 11:41:09.406 [4360.1340] <2> vnet_bind_to_port_addr_extra: vnet_bind.c.158: Function failed: 10 0x0000000a 11:41:09.406 [4360.1340] <2> vnet_async_connect: vnet_vnetd.c.3835: vnet_bind_to_port_addr failed: 10 0x0000000a 11:41:09.406 [4360.1340] <2> vnet_connect_to_service_or_vnetd: vnet_vnetd.c.3515: vnet_async_connect failed: 10 0x0000000a 11:41:09.406 [4360.1340] <2> nb_connect_to_vnetd_or_legacy: comm.c.2033: vnet_connect_to_vnetd_or_service failed: 10 11:41:09.406 [4360.1340] <2> bpcr_connect: nb_connect_to_vnetd_service(admcorp) failed: 21 11:41:09.406 [4360.1340] <2> bpcr_connect: Can't connect to client admcorp 11:41:09.406 [4360.1340] <2> ConnectToBPCD: bpcd_connect_and_verify(admcorp, admcorp) failed: 21 11:41:09.406 [4360.1340] <16> bpbrm start_bpcd_stat: bpcd on admcorp exited with status 21: socket open failed

Resolution: It has been observed that applying the default "Global Attributes" and "Port Ranges" settings to the master server can resolve this issue. To apply these settings, follow these steps: Open the NetBackup Administration Console, connecting to the master server Expand Host Properties in the left pane and click Master Server Double click the name of the master server in the right pane Click the Global Attributes property Within Global Attributes, click Defaults. Then, click Apply Click the Port Ranges property Within Port Ranges, click Defaults. Then, click Apply and OK Click OK on the message that services may need to be restarted When no jobs are active on the master server, restart services when possible Note: Ensure that any firewalls in place are configured to allow communication within port ranges that are specified in NetBackup. For more information on NetBackup and ports, see the port usage guide referenced below.

Problem
STATUS CODE 21: Oracle backups through a firewall fail with NetBackup Status Code 21 (socket open failed) when using a NetBackup 5.1 Oracle client and a NetBackup 6.0 master server.

Solution
Overview: Oracle backups through a firewall fail with NetBackup Status Code 21 (socket open failed) when using a NetBackup 5.1 Oracle client and a NetBackup 6.0 master server. Troubleshooting: Review the Oracle Recover Manager (RMAN) output log file and the NetBackup progress log, along with the client's attributes on the master server. Log files: The RMAN output from the backup contains the following information:
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on ORA_SBT_TAPE_1 channel at 10/10/2006 04:02:13 ORA-19506: failed to create sequential file, name="OWLLT_1954_603432048_1", parms=""

ORA-27028: skgfqcre: sbtbackup returned error ORA-19511: Error received from media manager layer, error text: VxBSACreateObject: Failed with error: Server Status: socket open failed

The NetBackup progress log on the Oracle server (/usr/openv/netbackup/logs/dbext/logs) contains the following:
Backup started Wed Oct 11 04:01:19 2006 04:01:23 Initiating backup 04:01:32 INF - Starting bpbrm 04:02:34 INF - Server status = 21 04:02:36 INF - Backup by SYSTEM on client nladms0034 using policy CSM_nladms0034_OWLLP_flx, sched oracle_application_daily:socket open failed.

Resolution: The client connection information for the Oracle client needs to be updated as follows: BPCD connect back: Use default connect options Ports: Use default connect options Daemon connection port: Automatic. This can be set either through the NetBackup Administration Console or from the command line.

To set this from the command line, open a command prompt on the master server, and from the /usr/openv/netbackup/bin/admincmd directory, run:
bpclient -client <client_name> -L

This lists the specified client and the connect attributes. To update the connect options, run the following command:
bpclient -client <client_name> -update -connect_options 2 2 0

If the bpclient -client <client_name> -L command returns the message "bpclient: no entity was found (227)", then there is currently no client entry, and one can be created using the command:
bpclient -client <client_name> -add -connect_options 2 2 0

To set the connection options from the NetBackup Administration Console, open the console, and from the Host Properties section, open the host properties of the master server, and select the Client Attributes section (see Figure 1 below). Figure 1

Review the "Clients" section (circled in Figure 1 above), and see if the Oracle client which is failing is listed. If the client is not shown (as in Figure 1), add the client by clicking on the "Add" button, and entering the Oracle client's name (Figure 2). Figure 2

After adding the client, go to the Connect Options tab, and confirm the connections are set as shown in Figure 3.

Figure 3

Once set as shown, click on Apply and OK, and close the master server host properties. When there are no backups or restores running, cycling all NetBackup services.

Problem
STATUS CODE 21: SQL backups fail with a Status Code 21 (socket open failed) in the dbclient log file when the master server is Veritas NetBackup (tm) 6.x and the SQL client is NetBackup 5.x.

Solution

Overview: SQL backups fail with a NetBackup Status Code 21 (socket open failed) in the dbclient log file when the master server is NetBackup 6.x and the SQL client is NetBackup 5.x. Troubleshooting: Enable and review the NetBackup dbclient log file on the SQL server. Log files: In the dbclient log file, the following error message is observed:
11:18:07.671 [232.397] <16> serverResponse: ERR - server exited with status 21: socket open failed 11:18:07.671 [232.397] <16> CreateNewImage: ERR - serverResponse() failed

Resolution: The problem observed is the result of changes to the default communication method between NetBackup 5.x and NetBackup 6.x. In NetBackup 5.x, communications between the master and client server are via standard ports (13782 for bpcd and 13720 for bprd). In NetBackup 6.x, the default communication port is the VNETD port (13724). Since SQL backups require a connection back to the master server, by default, the NetBackup 5.x client will attempt to connect via port 13720. The master server is listening on port 13724, so no connection is made and the socket open fails. To correct this, open the NetBackup Administration Console on the master server, and open the Host Properties section. Click on Master Server, and then open the properties for the master server. Under "Client Attributes", click on "Add" (see Figure 1). Figure 1

Enter the name of the SQL client server, and click on "Add", and then "Close" (see Figure 2). Figure 2

Then, go to the "Connect Options" tab for the SQL client and for the "Daemon connection port", select either Automatic or VNETD only (see Figure 3). Figure 3

Then click on OK to close the master server properties and restart the NetBackup services, as requested.

Problem

Error: Status code 21 when trying to backup a Client. Changing the backup destination to another Media Server sometimes works, and the original Media Server that has problems backing up the Client doesn't have any issues while doing backups for another Clients.

Error

Status Code 21.

Running a bptestbpcd from the master server to the client works fine.

Running a bptestbpcd from the media server to the client does not work, even though the media server is able to access the vnetd port on the client via telnet. Log Files: The following logs might be seen during this error: From the vnetd log:

15:55:18.349 [6696.7488] <2> ProcessRequests: .\vnetd.c.284: msg: VNETD ACCEPT FROM 192.168.20.51.3559 TO 10.211.5.106.13724 fd = 728 15:55:18.349 [6696.7488] <2> vnet_version_accept: .\vnetd.c.1141: *actual_version: 4 0x00000004 15:55:18.520 [6696.7488] <2> ProcessRequests: .\vnetd.c.344: msg: Request VN_REQUEST_SERVICE_SOCKET(6) 15:55:18.520 [6696.7488] <2> process_service_socket: .\vnetd.c.1523: service_name: bpcd 15:55:18.520 [6696.7488] <2> vtext_failure: ..\libvlibs\vtext.c.98: Function vtext_open failed: 7 15:55:18.520 [6696.7488] <2> vnet_read_service: ..\libvlibs\vnet_text.c.415: Function failed: 19 0x00000013 15:55:18.520 [6696.7488] <2> vnet_read_service_file: ..\libvlibs\vnet_text.c.356: Function failed: 19 0x00000013 15:55:18.552 [6696.7488] <2> ProcessRequests: .\vnetd.c.346: status: 0 0x00000000 15:55:18.552 [6696.7488] <4> main: Terminating with status 0 16:04:10.546 [7104.7628] <2> ProcessRequests: .\vnetd.c.284: msg: VNETD ACCEPT FROM 192.168.20.53.56080 TO 10.211.5.106.13724 fd = 712 16:04:10.546 [7104.7628] <2> vnet_version_accept: .\vnetd.c.1141: *actual_version: 4 0x00000004 16:04:10.718 [7104.7628] <2> ProcessRequests: .\vnetd.c.344: msg: Request VN_REQUEST_SERVICE_SOCKET(6) 16:04:10.718 [7104.7628] <2> process_service_socket: .\vnetd.c.1523: service_name: bpcd 16:04:10.718 [7104.7628] <2> vtext_failure: ..\libvlibs\vtext.c.98: Function vtext_open failed: 7 16:04:10.718 [7104.7628] <2> vnet_read_service: ..\libvlibs\vnet_text.c.415: Function failed: 19 0x00000013 16:04:10.718 [7104.7628] <2> vnet_read_service_file: ..\libvlibs\vnet_text.c.356: Function failed: 19 0x00000013 16:04:10.781 [7104.7628] <2> ProcessRequests: .\vnetd.c.346: status: 0 0x00000000 16:04:10.781 [7104.7628] <4> main: Terminating with status 0

From the bpcd log:

13:02:35.415 [6892.2968] <2> vnet_bind_and_connect_extra: ..\libvlibs\vnet_bind.c.280: Function failed: 10 0x0000000a

13:02:35.415 [6892.2968] <2> vnet_bind_and_connect: ..\libvlibs\vnet_bind.c.181: Function failed: 10 0x0000000a 13:02:35.415 [6892.2968] <2> vnet_connect_by_vnetd: ..\libvlibs\vnet_vnetd.c.1410: status: 10 0x0000000a 13:02:35.415 [6892.2968] <2> get_vnetd_forward_socket: vnet_connect_by_vnetd failed: 10 13:02:35.415 [6892.2968] <16> bpcd main: get_vnetd_forward_socket failed: 21

Solution

Solution: Open the Administration Console, and go to Host Properties > Clients. Select the Client having issues, and display its properties. The following is an example of a Working configuration. Verify that the Media Server used to backup this client is located in the proper field (Media Servers):

The Media Server MUST be in the Media Servers: field. NOT in the Additional Servers list.

If the Media Server is on the Additional Servers list, delete it, and add it under Media Servers. To verify that the settings were successfully added, check for the following: Windows clients: Open the registry, and navigate to the following key: HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\CurrentVersion\C onfig On the right side, you should be able to find the following entries:
MEDIA_SERVER REG_MULTI_SZ MEDIA_SERVER1 MEDIA_SERVER2 Server REG_MULTI_SZ <Master_Server> SERVER1 SERVER2

UNIX Clients: Edit the bp.conf file. It must contain the following entries: SERVER = <Master_Server> ( The Master Server must ALWAYS be the first "SERVER" entry!!!!!!!!!!)
SERVER = SERVER1 SERVER = SERVER2 MEDIA_SERVER = MEDIA_SERVER1 MEDIA_SERVER = MEDIA_SERVER2

After verifying the changes, restart the NetBackup client services/daemons on the client.