drive in state AVR

[riad]

Hello,

We are making saves with netbackup 7.5 in a server with windows 2008 R2 standard as OS , we use also a robot with tow drive (dell PowerVault TL4000).  

One of the drives is a full high TD4 and the other is a half high HH4.

Question:

• The HH4 is very slow then the TD4 is it normal?
• I stopped the HH4 it’s very slow and I work with TD4 but sometimes it goes to AVR state ,then I tried to see the configuration with that command tpconfig –d, and I had the result in the picture the TD4 is the control path drive and the SCSI coordinates take a different path is it normal ??? If not how to fix it??

[revarooo]

AVR is usually nothing to do with NetBackup but communication issue between robot and drive or media server and robot.

The screenshot is not telling us anything.

you mention the HH4 is very slow, but you've not said how slow. Slow for you may be fast for someone else.

[Marianne]

Drives are configured as position 1 and 3 in the robot?

Please show us output of 'scan'
(command is in same ...\volmgr\bin folder)

To troubleshoot device issues, please add 
VERBOSE
entry to vm.conf (in ...\volmgr folder) and restart NetBackup Device Manager service.

NBU Device Manager will log actions/problems in Event Viewer System and Application logs.

[riad]

There is the scan.

I add the verbose to the vm.conf.

For the HH4 speed 5GB in 1hour and the TD4 15GB in 15minut same job.  

[Marianne · Accepted solution]

NBU config seems fine - the middle drive slot of the robot (position 2) is empty.

You will need to troubleshoot at OS -> hardware level.

The AVR issue is the robot and tape drive losing comms/connectivity.
If the robot has a web interface, you should be able to check the robot logs.

Check Event Viewer logs for OS -> device issues.

To troubleshoot slow throughput, check physical config - how is the HH4 drive connected to the server?
How is TD4 connected to the server?

Which tape driver is used for these tape drives? Same or different?

NBU has no control over drive speed - it simply sends data to the device driver.