Troubleshooting
Problem
nzbackup error occurs when using Veritas NetBackup
Symptom
When trying to generate a backup using the Veritas NetBackup connector, the message, 'Error: Connector exited with error: 'ERROR: BSACreateObject() failed with errcode (25) : Server Status: cannot connect on socket' is encountered.
Environment
When the backup starts, the NetBackup client (NPS host) first connects to the NetBackup Master Server and several things happen.
1. The Master Server confirms that the DATASTORE_POLICY being referenced exists.
2. The Master Server confirms that the client belongs to this policy.
3. The Master Server confirms that a schedule with a start/end window that supports running the backup operation now exists.
4. The Master Server reviews the storage options associated with the policy and returns that information for the client, instructing the client on where to write the data.
The storage options are almost endless; NetBackup supports many different types of media. To utilize storage allocated to a different server (DAS, SAN, etc), NetBackup allows you to designate a system as a Media Server -- thus allowing other clients to leverage that server's storage.
Diagnosing The Problem
The error could occur because a policy has been updated to either explicitly use storage that exists on a NetBackup Media Server or the Master Server is implicitly using it (first or any available storage unit). If a NetBackup client receives instructions from the NetBackup Master Server to write to a media server BUT that client does not list that Media Server in the /usr/openv/netbackup/bp.conf file, the error below would be reported by the nzbackup utility:
Error: Connector exited with error: 'ERROR: BSACreateObject() failed with errcode (25) : Server Status: cannot connect on socket
Another symptom of this will exist in the NetBackup log /usr/openv/netbackup/logs/bpbrm/log.YYMMDD on the NetBackup Media Server. If the problem described in this article is the issue that you are facing, you will find a log entry similar to the following:
00:33:00.339 [24544] <16> bpbrm send_info_via_progress_file: bpcd on cs-spubox5 exited with status 59: access to the client was not allowed
Resolving The Problem
To resolve this error, simply add the following line to the NetBackup client's /usr/openv/netbackup/bp.conf file:
SERVER = <NetBackup Media Server hostname>
For example, the error above was produced using a client with the following configuration file:
[nz@cs-spubox5 ~]$ cat /usr/openv/netbackup/bp.conf
SERVER = cs-spubox6
CLIENT_NAME = cs-spubox5
To correct this problem, add the hostname of the NetBackup Media Server to the configuration file and save your changes:
[nz@cs-spubox5 ~]$ cat /usr/openv/netbackup/bp.conf
SERVER = cs-spubox6
SERVER = cs-spubox4
CLIENT_NAME = cs-spubox5
'cs-spubox4' is the NetBackup Media Server that the backup was attempting to write to when it failed.
Historical Number
NZ530252
Was this topic helpful?
Document Information
More support for:
IBM PureData System
Software version:
1.0.0
Document number:
463231
Modified date:
17 October 2019
UID
swg21570994