1. Support
  2. Knowledge base
  3. 100018431

Enterprise Vault migration to NetBackup will only run a single job when many files are available for migration. Windows Application Event logs on the Enterprise Vault system report errors Event ID 6954 and Event ID 6918.

Article: 100018431
Last Published: 2015-01-19
Ratings: 1 0
Product(s): NetBackup

Problem

Enterprise Vault migration to NetBackup will only run a single job when many files are available for migration. Windows Application Event logs on the Enterprise Vault system report errors Event ID 6954 and Event ID 6918.

Error Message

bsa_QueryFile: ERR - bsa_bplist() failed 131

Cause

Details:
Enterprise Vault migration to NetBackup will only run a single job when many files are available for migration. Windows Application Event logs on the Enterprise Vault system report errors Event ID 6954 and Event ID 6918.  

Scenario: NetBackup clustered media server running on the same cluster as Enterprise Vault client.
nodeA = cluster node physical name
nodeB = cluster node physical name
ev = Enterprise Vault virtual name
nbu = NetBackup media server virtual name

Enterprise Vault data migration should run a separate NetBackup job for each .cab file to be migrated.  In this situation only a single job runs ending with a Status 0.  Each time the Enterprise Vault data migration runs the same .cab file is backed up and ends with Status 0 when there should be multiple jobs each with a separate .cab file being backed up.


Log Files:
<install_path>\NetBackup\logs\ exten_client on the Enterprise Vault Server:
0:47:31.745 [7472.1816] <8> dbc_GetServerClientConfig: WARNING - NBU's client name= <nodea> differs from gethostname()= <nbu>
***snip***
10:49:17.251 [7472.1816] <16> bsa_QueryFile: ERR - bsa_bplist() failed 131


<install_path>\NetBackup\logs\ bprd log on the NetBackup master:
10:47:31.060 [6960.4724] <2> hosts_equal: Comparing hosts <nodea> and <nbu>
***snip***
10:47:31.060 [6960.4724] <2> db_valid_client: no alternate names to check in C:\\Program Files\VERITAS\NetBackup\db\altnames - No such file or directory (2)
10:47:31.060 [6960.4724] <2> db_valid_client: client_name=nodea peername=nbu
10:47:31.060 [6960.4724] <2> db_valid_client: nbu is not a valid client
***snip***
10:47:31.060 [6960.4724] <2> process_request: client nodea peername nbu invalid for delete request
 

Solution



Solution:
1. Create the necessary touch file entries in the altnames directory on the master server:

For the above scenario the following touch files would need to be created:
-  install_path\NetBackup\db\altnames\nodeA
-  install_path\NetBackup\db\altnames\nodeB
NOTE: Edit each touch file so it contains the NetBackup virtual server name 'nbu' on one line in the file (see "Managing Client Backups and Restores" in the NetBackup System Administrator's Guide Vol I)
 
 

 

Was this content helpful?

Article Languages