VMware Intelligent Policy or query base VMware backups fail with Status 69 "invalid filelist specification"

Article: 100008579
Last Published: 2012-06-23
Ratings: 1 0
Product(s): NetBackup & Alta Data Protection

Problem

VMware Intelligent Policy or query base VMware backups are failing with Status 69 because the VMware Access Host is unable to access the Master server.

Error Message

Failed VMware Job Detail Status from the Activity Monitor:

05/11/2012 16:31:32 - begin Application Resolver: Policy Execution Manager Preprocessed
05/11/2012 16:31:32 - Error nbpem (pid=26534) could not parse iteration vmware:/?filter= Powerstate Equal poweredOn
Operation Status: 69
05/11/2012 16:31:32 - end Application Resolver: Policy Execution Manager Preprocessed; elapsed time 0:00:00
05/11/2012 16:31:32 - begin Application Resolver: Stop On Error
Operation Status: 0
05/11/2012 16:31:32 - end Application Resolver: Stop On Error; elapsed time 0:00:00
05/11/2012 16:31:32 - begin Application Resolver: End Notify Script
05/11/2012 16:31:32 - Info RUNCMD (pid=3745) started
05/11/2012 16:31:32 - Info RUNCMD (pid=3745) exiting with status: 0
Operation Status: 0
05/11/2012 16:31:32 - end Application Resolver: End Notify Script; elapsed time 0:00:00
Operation Status: 69
05/11/2012 16:31:32 - end Parent Job; elapsed time 0:03:43
Operation Status: 0
invalid filelist specification (69)

Snip from nbpem unified logs (OID 116), on the master server:

5/31/2012 10:22:21.224 [Debug] NB 51216 nbpem 116 PID:6918 TID:3 File ID:116 [No context] 4 [JobListener_i::updateJobStatus] (ID:19160e0) received status for jobid=316380, status EC_filelist_str_invalid (69), birthtime 2012/05/31 10:18:41 (1338481121), CallbackInfo (schedName=Full policyName=VWS-VMware1 clientName=nbu02_bkhost.test.com streamNumber=-1 keyWord= groupId=316380 userName=root mediaServer=master01 brmstarted=false disableResume=false)(JobListener_i.cpp:70)
5/31/2012 10:22:21.224 [Debug] NB 51216 nbpem 116 PID:6918 TID:3 File ID:116 [No context] 4 [JobListener_i::notifyAll] (ID:19160e0) delivery of status EC_filelist_str_invalid (69), jobid=316380 to interface ID:1a0c7a8, param 0(JobListener_i.cpp:204)
5/31/2012 10:22:21.224 [Debug] NB 51216 nbpem 116 PID:6918 TID:3 File ID:116 [No context] 3 [PemHandlerEntry::invokeRunWithCancelSafety] (ID:1d1bc08) Job Completion Task Handler call run on task ID:1c345f8 CTX:1adcd90, parameter 5, event ID:1d1bc08, reoccurring(PemHandlerEntry.cpp:55)

Snip from ncfvmwarepi unified logs (OID 386):

6/5/2012 08:19:29.179 [Debug] NB 51216 ncfvmwarepi 386 PID:4116 TID:5336 File ID:366 [No context] 4 [VMwarePlugin::getServerCred] Credentials coming from server master01 (../VMwarePlugin.cpp:231)
6/5/2012 08:23:15.573 [Application] NB 51216 ncfvmwarepi 386 PID:4116 TID:5336 File ID:366 [No context] [Error] V-386-1 Unable to obtain credentials from master server.
6/5/2012 08:23:15.573 [Application] NB 51216 ncf 309 PID:4116 TID:5336 File ID:366 [No context] [Error] V-309-39 could not parse iteration vmware:/?filter=Powerstate Equal poweredOn

Cause

The issue occurs because the VMware Access Host cannot talk to the master server. For example, ping commands may be failing from the VMware Access Host to the Master. The master server name used during this backup will be the name shown in the following command:

  • UNIX/Linux: /usr/openv/netbackup/bin/admincmd/nbemmcmd -listhost
  • Windows: install_path\Veritas\NetBackup\bin\admincmd\nbemmcmd -listhost

Note: Run this command from the master, as running it from the media server may hang if communication is impacted.

Solution

Address the communication issue between the VMware Access Host and the Master Server. Verify you can ping the Master Server name shown from nbemmcmd -listhost command from the VMware Access Host.

Was this content helpful?