Vidéos d'aide de Screencast
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

NDMP_LOG_ERROR 2 DATA: Backup terminated: Unable to lookup Volume '/server105/data5/': VLDB Server return failure for volNameLookup (for /server105/data5/)

Created: 31 Oct. 2012 | 2 comments

I am unable to find any information on this error.  This policiy has worked for over a year now and just started throwing this error.  Any assistance would be greatly appreciated as I am running at risk without a good backup.

Thanks - Dave

10/28/2012 18:26:35 - Info nbjm (pid=17003) starting backup job (jobid=3833) for client gxnode1, policy gxnode1_data5, schedule Full
10/28/2012 18:26:35 - Info bpbrm (pid=17554) gxnode1 is the host to backup data from
10/28/2012 18:26:35 - Info bpbrm (pid=17554) reading file list from client
10/28/2012 18:26:35 - Info bpbrm (pid=17554) starting ndmpagent on client
10/28/2012 18:26:35 - Info ndmpagent (pid=17558) Backup started
10/28/2012 18:26:35 - Info bpbrm (pid=17554) bptm pid: 17559
10/28/2012 18:26:35 - Info nbjm (pid=17003) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=3833, request id:{8865CB98-214E-11E2-961D-5D4EA55420E7})
10/28/2012 18:26:35 - requesting resource Any
10/28/2012 18:26:35 - requesting resource g105netbackup.NBU_CLIENT.MAXJOBS.gxnode1
10/28/2012 18:26:35 - requesting resource g105netbackup.NBU_POLICY.MAXJOBS.gxnode1_data5
10/28/2012 18:26:35 - granted resource  g105netbackup.NBU_CLIENT.MAXJOBS.gxnode1
10/28/2012 18:26:35 - granted resource  g105netbackup.NBU_POLICY.MAXJOBS.gxnode1_data5
10/28/2012 18:26:35 - granted resource  0311L4
10/28/2012 18:26:35 - granted resource  IBM.ULTRIUM-TD4.001
10/28/2012 18:26:35 - granted resource  g105netbackup-hcart-robot-tld-0-gxnode1
10/28/2012 18:26:35 - estimated 7458222105 kbytes needed
10/28/2012 18:26:35 - Info nbjm (pid=17003) started backup job for client gxnode1, policy gxnode1_data5, schedule Full on storage unit g105netbackup-hcart-robot-tld-0-gxnode1
10/28/2012 18:26:35 - started process bpbrm (pid=17554)
10/28/2012 18:26:35 - connecting
10/28/2012 18:26:35 - connected; connect time: 0:00:00
10/28/2012 18:26:36 - Info bptm (pid=17559) start
10/28/2012 18:26:36 - Info bptm (pid=17559) using 30 data buffers
10/28/2012 18:26:36 - Info bptm (pid=17559) using 262144 data buffer size
10/28/2012 18:26:36 - Info bptm (pid=17559) start backup
10/28/2012 18:26:36 - Info bptm (pid=17559) Waiting for mount of media id 0311L4 (copy 1) on server g105netbackup.
10/28/2012 18:26:36 - mounting 0311L4
10/28/2012 18:27:12 - Info bptm (pid=17559) media id 0311L4 mounted on drive index 1, drivepath nrst1a, drivename IBM.ULTRIUM-TD4.001, copy 1
10/28/2012 18:27:12 - mounted 0311L4; mount time: 0:00:36
10/28/2012 18:27:12 - positioning 0311L4 to file 3
10/28/2012 18:28:12 - Error ndmpagent (pid=17558) NDMP_LOG_ERROR 2 DATA: Backup terminated: Clone removal failed on VolRpc error: VOLRPC BUSY (for /server105/data5)
10/28/2012 18:28:12 - Error ndmpagent (pid=17558) NDMP backup failed, path = /server105/data5
10/28/2012 18:28:12 - Error bptm (pid=17559) none of the NDMP backups for client gxnode1 completed successfully
10/28/2012 18:28:12 - positioned 0311L4; position time: 0:01:00
10/28/2012 18:28:12 - begin writing
10/28/2012 18:28:27 - Info bptm (pid=17559) EXITING with status 99 <----------
10/28/2012 18:28:27 - Info ndmpagent (pid=0) done. status: 99: NDMP backup failure
10/28/2012 18:28:27 - end writing; write time: 0:00:15
NDMP backup failure  (99)

Commentaires CommentairesAccéder au dernier commentaire

l'image des Nicolai

You need consult the storage admin and inspect the syslog. It's the NDMP device that report the error. If the device is a EMC brand use this T/N to retrive data:

http://www.symantec.com/docs/TECH150646

Assumption is the mother of all mess ups.

If this post answered your'e qustion -  Please mark as a soloution.