Backup job reports error 213 for Puredisk storage unit

Article:TECH145405  |  Created: 2010-12-01  |  Updated: 2012-01-12  |  Article URL http://www.symantec.com/docs/TECH145405
Article Type
Technical Solution


Issue



When Netbackup writes to Puredisk storage unit, a backup job will fail with error 213, in some of the following situations.

1. The disk pool being down.

2. The storage server being down.

3. The Puredisk server being down

4. Check connectivity between the media server and the puredisk server

5. The Puredisk server being up, and the needed ports being blocked by firewall.

6. Disable the pdiptables on the puredisk server

 

 


Error



The below logs could be checked for firewall issues

/Storage/log/pdweb/mod_jk.log
 Dec 01 14:03:25.858 2010] [25388:1949167840] [error] ajp_send_request::jk_ajp_common.c (1467): (gui) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=111)
[Wed Dec 01 14:03:25.858 2010] [25388:1949167840] [info] ajp_service::jk_ajp_common.c (2407): (gui) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
[Wed Dec 01 14:03:25.959 2010] [25388:1949167840] [info] jk_open_socket::jk_connect.c (593): connect to 127.0.0.1:8009 failed (errno=111)
[Wed Dec 01 14:03:25.959 2010] [25388:1949167840] [info] ajp_connect_to_endpoint::jk_ajp_common.c (922): Failed opening socket to (127.0.0.1:8009) (errno=111)

Storage/log/pdweb-at.log
Wed Dec  1 17:19:43 2010  [ERROR]  Error unknown credential returned by

/Storage/log/slapd.log

Dec  1 13:15:02 svalbprdbck03 slapd[20513]: connection_read(16): no connection!
Dec  1 14:02:41 svalbprdbck03 slapd[20513]: daemon: shutdown requested and initiated.
Dec  1 14:02:41 svalbprdbck03 slapd[20513]: slapd shutdown: waiting for 0 threads to terminate
Dec  1 14:02:41 svalbprdbck03 slapd[20513]: slapd stopped.
Dec  1 14:03:07 svalbprdbck03 slapd[25079]: @(#) $OpenLDAP: slapd 2.3.32 (Oct 26 2009 11:13:24) $  abuild@vivaldi:/usr/src/packages/BUILD/openldap-2.3.32/servers/slapd
Dec  1 14:03:07 svalbprdbck03 slapd[25080]: slapd starting

/Storage/log/pdweb-error.log

[Wed Dec 01 14:02:38 2010] [notice] caught SIGTERM, shutting down
[Wed Dec 01 14:03:10 2010] [notice] Apache/2.2.15 (Unix) mod_jk/1.2.27 configured -- resumi ng normal operations
[Wed Dec 01 14:03:11 2010] [error] [client 127.0.0.1] client denied by server configuration : /opt/pdweb/error
[Wed Dec 01 14:03:13 2010] [error] [client 127.0.0.1] client denied by server configuration : /opt/pdweb/error


Environment



Netbackup 7.0.1 and Puredisk 6.6.1


Cause



Certain required ports in the firewall were blocked


Solution



Disabled iptables using command

#service pdiptables stop

Alternatively, you may use

#/sbin/chkconfig pdiptables off


Supplemental Materials

Description

To narrow down the troubleshooting for the error 213 during backup jobs, to identify a firewall issue

1. The disk pool being down.

Check the Netbackup Admin Gui -> Media and Device Management -> Devices -> Disk Pool

Check whether the disk pool is Full.

Or through command line using command, check whether Status is UP

/usr/openv/netbackup/bin/admincmd/nbdevquery -listdp -dp <diskpoolname> -stype PureDisk –U

2. The storage server being down.

Check the Netbackup Admin Gui -> Media and Device Management -> Credentials -> StorageServer. Select the Storage server and see properties.

Or execute the command, to check whether Status is UP

/usr/openv/netbackup/bin/admincmd/nbdevquery -liststs -storage_server server_name -stype PureDisk –U

3. The Puredisk server being down

Login to the Puredisk server, and check the status of the puredisk services using command

#service puredisk status

4. Check the connectivity between the media server and the puredisk server, using command

<install-path>/netbackup/bin/admincmd/bpstsinfo -si -sp PureDisk: -sn <puredisk-server>

5. The Puredisk server being up, and the needed ports being blocked by firewall.

Use the below command

# service pdiptables status

See the ports being excluded in the iptables using command

#iptables -L




Article URL http://www.symantec.com/docs/TECH145405


Terms of use for this information are found in Legal Notices