• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1357
  • Last Modified:

Configuring D2D to work with Backup Exec 12.5

Hello.

I'm trying to configure a D2D device from HP on a Windows Server 2003 server using Backup Exec 12.5.

I used the correct drivers from HP, the iSCSI initiator applet in the control panel recognizes the drive.  In the HP web app which is used to configure the drive, the drive shows as having 8 cartridges connected and that iSCSI is working.  It has a valid IP address on the local network and the drives have plenty of space

When I go into Backup Exec, which is running on the server that I want to back up, I cannot "add" the D2D.  Backup Exec shows another tape drive, which we use on Sundays only, which is directly connected to the server, but it does not "see" the D2D.

Is there a step I missed?

Any help on this is greatly appreciated.

Happy New Year!

-Ted
0
tedwill
Asked:
tedwill
1 Solution
 
David WallCommented:
Have you added the disk to disk drive in the devices tab of BE?
 
0
 
tedwillAuthor Commented:
The only options on the devices tab are:
Robotic Libraries
Robotic Library Drives
Stand-alone Drives
Backup-to-disk folders
Removable backup-to-disk folders
Symantec Network Protection folders

Which of those categories would it fit under?  Also, should I be able to access the D2D as a drive\Folder with SMB?
0
 
andyalderCommented:
Presumably this is a virtual tape library, if so it should show as a rootic tape library since BE can't tell whether it is made from disks unde rthe hood. You shouldn't see it as a disk drive/SMB device. You have to add it as a library and tape drives using the device wizard in BE. You can generally set the personality to emulate particular makes of library with the VTL management software.
0
 
Thomas RushCommented:
It sounds as though you have created an 8-slot HP 1/8 Autoloader VTL (virtual tape library) on the D2D.

Verify that the vtl on the D2D has the correct IP address for the BE server in its iSCSI configuration.

You may have to run a 'discovery' (find new devices) in Windows device manager to see the new vtl.

Once device manager can see the tape library, it should be discoverable by BE as a tape library with bar code reader.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now