Please post all info in Details tab.

This will hopefully give an indication of WHICH resource allocation is failing...

Have you verified VTL functionality with robtest?

Was Robot inventory successful?

Maybe also consider upgrade to 6.5.6 - not that it will solve your problem, but status 800 is replaced with more meaningful status codes and error messages.

Hi,

I haven't tested the functionality with 'robtest', but the Robot inventory was successful.

Please find below info fron the Details tab:

25/10/2010 18:00:00 - requesting resource MediaSTU2
25/10/2010 18:00:00 - requesting resource nbu-win-svr.NBU_CLIENT.MAXJOBS.winclient
25/10/2010 18:00:00 - requesting resource nbu-win-svr.NBU_POLICY.MAXJOBS.Client2Media_VTL
25/10/2010 06:58:17 - collecting BMR information
25/10/2010 06:58:17 - connecting
25/10/2010 06:58:18 - connected; connect time: 00:00:01
25/10/2010 06:58:18 - transferring BMR infomation to the master server
25/10/2010 06:58:18 - connecting
25/10/2010 06:58:18 - connected; connect time: 00:00:00
25/10/2010 18:00:00 - granted resource nbu-win-svr.NBU_CLIENT.MAXJOBS.winclient
25/10/2010 18:00:00 - granted resource nbu-win-svr.NBU_POLICY.MAXJOBS.Client2Media_VTL
25/10/2010 18:00:00 - granted resource LT06L1
25/10/2010 18:00:00 - granted resource drive1
25/10/2010 18:00:00 - granted resource MediaSTU2
25/10/2010 18:00:02 - estimated 0 kbytes needed
25/10/2010 18:00:02 - begin Parent Job
25/10/2010 18:00:02 - begin Bare Metal Restore , Start Notify Script
Status 26
25/10/2010 18:00:02 - end Bare Metal Restore , Start Notify Script; elapsed time: 00:00:00
25/10/2010 18:00:02 - begin Bare Metal Restore , BMR Save
25/10/2010 18:00:03 - started process bpbrm (14885)
25/10/2010 06:58:23 - Error bpbrm(pid=14885) BMRERR: Received BMR error: Failed to import Config file. (1)   
25/10/2010 06:58:23 - Error bpbrm(pid=14885) BMRERR: Received BMR error: Failed sending the discovery. (1)    
25/10/2010 06:58:24 - Error bpbrm(pid=14885) BMRERR: Received BMR error: The NBU client version is incompatible with the master server. (1)
25/10/2010 18:00:14 - end writing
Status 1
25/10/2010 18:00:14 - end Bare Metal Restore , BMR Save; elapsed time: 00:00:12
25/10/2010 18:00:14 - begin Bare Metal Restore , Policy Execution Manager Preprocessed
Status 800
25/10/2010 18:24:45 - end Bare Metal Restore , Policy Execution Manager Preprocessed; elapsed time: 00:24:31
25/10/2010 18:24:45 - begin Bare Metal Restore , Stop On Error
Status 0
25/10/2010 18:24:45 - end Bare Metal Restore , Stop On Error; elapsed time: 00:00:00
25/10/2010 18:24:45 - begin Bare Metal Restore , End Notify Script
Status 26
25/10/2010 18:24:45 - end Bare Metal Restore , End Notify Script; elapsed time: 00:00:00
Status 800
25/10/2010 18:24:45 - end Parent Job; elapsed time: 00:24:43
resource request failed(800)

Chk this technote

http://www.symantec.com/business/support/index?page=content&id=TECH60242

Ensure that PARTED is available on the client. Else the PARTED package needs to be installed to the client.

Seems physical resources were allocated correctly:

25/10/2010 18:00:00 - granted resource LT06L1
25/10/2010 18:00:00 - granted resource drive1
25/10/2010 18:00:00 - granted resource MediaSTU2

Please disable BMR in the backup policy to test basic functionality.

Once that is working, troubleshoot the BMR error.

Regarding BMR error:

Error bpbrm(pid=14885) BMRERR: Received BMR error: The NBU client version is incompatible with the master server. (1)

Please can you confirm NBU client version installed on your client machine. Also what is your client OS/Version? I suspect either of these has supportability issue.

BMR master server logs (119 id) will help to confirm this problem.

Thanks.

-Mandar

Sorry for the delay but I was very busy today.

@Mandar 

I'm using NBU 6.5 on all machines..

@Marianne

I've disabled BMR in the backup policy as you suggested, but I have the same problem.. The job freezes on the mount operation for a long time and then gives a similar error:

26/10/2010 16:14:16 - requesting resource MediaSTU2
26/10/2010 16:14:16 - requesting resource nbu-win-svr.NBU_CLIENT.MAXJOBS.winclient
26/10/2010 16:14:16 - requesting resource nbu-win-svr.NBU_POLICY.MAXJOBS.Client2Media_VTL
26/10/2010 16:14:16 - granted resource nbu-win-svr.NBU_CLIENT.MAXJOBS.winclient
26/10/2010 16:14:16 - granted resource nbu-win-svr.NBU_POLICY.MAXJOBS.Client2Media_VTL
26/10/2010 16:14:16 - granted resource 8MM002
26/10/2010 16:14:16 - granted resource drive1_Quantum
26/10/2010 16:14:16 - granted resource MediaSTU2
26/10/2010 16:14:16 - estimated 0 kbytes needed
26/10/2010 16:14:18 - started process bpbrm (22510)
26/10/2010 16:14:21 - connecting
26/10/2010 16:14:21 - connected; connect time: 00:00:00
26/10/2010 16:14:26 - mounting 8MM002
26/10/2010 05:46:23 - Error bptm(pid=22511) error requesting media, TpErrno = Robot operation failed     
26/10/2010 05:46:24 - Warning bptm(pid=22511) media id 8MM002 load operation reported an error     
26/10/2010 16:28:38 - current media 8MM002 complete, requesting next media Any
26/10/2010 05:46:32 - Error bptm(pid=22511) NBJM returned an extended error status: resource request failed (800)   
26/10/2010 16:28:48 - end writing
extended error status has been encountered, check logs(252)

Thanks a lot for your help.

error requesting media, TpErrno = Robot operation failed     
Warning bptm(pid=22511) media id 8MM002 load operation reported an error

Please use robtest on the media server to test mount/dismount. Let us know what the outcome is.

Also ensure that you have bptm log as well as VERBOSE entry in vm.conf on media server (restart NBU daemons after adding VERBOSE entry). Media Manager errors will be logged to /var/log/messages.

For BMR error:

Please attach your bmrd (119) log on master server. Please make sure debug level in nblog.conf is set to 6. If level is not 6 then please set it, restart services, take another bmr enabled backup, collect 119 log.

Thanks.

-Mandar

Hi,

Well, the BMR error apears only when backing up on VTL, on DSU works fine - so the problem is VTL related.

I've run the robtest and attached the output from the console. The robot seems to be OK, but there is a problem with the drives I think.
When I run drive diagnostics it failes for all of the drives with "Unable to allocate resources for diagnostics"

Thank you All!

Hi Mandar,

I have also attached the bmrd (119) log from master server. However I think the problem is with the VTL as the backups on DSU (with BMR enabled) are successful.

Cheers,

Virgil.

Which VTL are you using . Media server is windows or linux ?

If it is a windows , in device manager check all the VTL drives has proper driver installed . I have encountered lot of issues in windows like driver missing for VTL drives after reboot.

Run the below command on the media server and check whether all the drives are up or not .

Volmgr\bin>tpconfig -d

Run Robtest and verify the command excute and try to load a media and unload .

 Rajesh 

I've downloaded the vtl from the link: http://sites.google.com/site/linuxvtl2/ and I'm trying to use them in a test environment.

I've installed NBU media server on the server where I've loaded the vtl and the master server is on a W2003 machine.

Volmgr\bin>tpconfig -d shows all drives UP.

Using robtest all seems to be OK, I am able to load/unload media without problems.

Thanks.

Have you applied VTL license ? , it seems to be license missing . Please verify your license whether you have applied or not , it will be like "Vitural Tape Option" .

 Rajesh 

Please do the following test again:

Use robtest to mount a tape (preferably 8MM002).

In another window, check drive status:

vmoprcmd -d

Also check drive status from O/S point of view:

mt -f /dev/rmt...... status

If I look at robtest output - there seems to be a mix of SDLT, 8MM and ULT media. Are there matching tape drives for all these media types? And different STU's?

How was the media and tape drives configured in NBU? Hopefully different densities?

Please post output of:

On master:

vmquery -a -bx

bpstulist -U

On media server:

tpconfig -l

Just out of curiosity, since you are using the MHVTL, have you tried contacting the Author? He is listed (with emails) on the link page you posted, and is an employee of Symantec tech support in Australia. You also don't mention what version of the MHVTL you are using... is it a stable release vs dev release, etc.

Also, I should probably assume you are using iSCSI initiators in the Windows machine (since the VTL is running in a remote linux VM), so the versioning of that would be relevant as well, possibly.

I don't ask these questions for myself, as I wouldn't be able to troubleshoot this, but this is the type of thing that would probably be relevant.

T

Were you able to successfully move a tape into the drive in question and back again (without any SCSI sense code errors) ?

The 'robtest' only showed a listing of the library. no attempts to move media around.

Can you please supply the output of the following commands also:

/usr/openv/volmgr/bin/tpconfig -d

/usr/openv/volmgr/bin/vmoprcmd -d

/usr/openv/volmgr/bin/vmquery -a -j

/usr/openv/volmgr/bin/bpstulist -U

The 'tpconfig -d' shows the tape/library configuration from NetBackups point of view

The 'vmoprcmd -d' reports on the daemon status and if the devices are operational.

The 'vmquery -a -j' reports the status of all media (volumes) known to NetBackup.

The 'bpstulist -U' reports the configuration NetBackups storage unit(s).

Cheers

Mark

Thanks a lot for your help.

In seems that I don't have the Vitural Tape Option key. I didn't know that I need a license in order to work with VTL in NBU 6.5.

Cheers

Virgil

Hello Virgil,

When you say you have the same identical issue, I assume you now have a new temporary NetBackup license key that is valid.

From the VTL side of things, please :
- edit the /etc/mhvtl/mhvtl.conf and enable VERBOSE = 3
- Re-start the daemons

Re-test and create the fault symptoms using NetBackup.

Can you then supply me with:
 /var/log/messages

The output of the following commands (I still have not seen them)

/usr/openv/volmgr/bin/tpconfig -d
/usr/openv/volmgr/bin/vmoprcmd -d
/usr/openv/volmgr/bin/vmquery -a -j
/usr/openv/volmgr/bin/bpstulist -U

Cheers