Adding robot and drives

 
Thread Tools Search this Thread
Special Forums Windows & DOS: Issues & Discussions Adding robot and drives
# 1  
Old 04-27-2011
Adding robot and drives

Hi All

Im running veritas netbackup 6.5.5, on MWindows 2003 master server.
Ive just added a Quantum PX500 with 2 drives, the problem im facing is that now under the storage unit tab on console all the storage unit types for NDMP have the new robot listed and not the original one. The set up i need is to have the old robot TLD0 listed.
Can anyone help, the robot and drives were added via Configure storage devices Wizard.. The original robot is a ADIC 500 8 drive library.
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Hardware

Arduino Robot Tank Project

Normally I'm not into kits, but I thought my wife would enjoy this one since she is a big fan of robots and droids on StarWars! We are done with the basic mechanical assembly and starting on the electronics assembly today. The robot's "brain" consists of three levels. The Arduino board, on... (5 Replies)
Discussion started by: Neo
5 Replies

2. Solaris

Adding new hard drives on Sun SPARC T5440 server with Solaris 10

I need to add two new hard drives of 300 GB capacity to a SunSPARC T5440 server. The server currently has two hard drives of 146 GB each. How do I add the new drives to the existing UFS? What are the procedures involved in setting this server with the new hard drives? I am very new to Solaris... (6 Replies)
Discussion started by: ramatnmcc
6 Replies

3. Solaris

Adding new tape drives

hi, i am using Solaris 8 on a sparc box and already have 4 tape drives in a backup libaray attached to my unix server. we have recently added 2 new tape drives to the libaray and now want to get unix to see them. have it working in windows. how do i scan for new hardware and add theses new... (5 Replies)
Discussion started by: dshakey
5 Replies

4. Solaris

Adding logical drives

Hello, I have checked in here as I dont have enough experience as Solaris Admin. My Solaris seems to boot ok on a HP Proliant DL380 G6 server The release is 5.10, the kernel ID is Generic_137138-09. It was installed after creating one logical drive type RAID1, size 300GB. Now 2 further... (2 Replies)
Discussion started by: fogarino
2 Replies

5. Filesystems, Disks and Memory

Help adding new hard drives

Folks; I just added 2 physical new hard drives to my SUSE server. My server is already running SUSE 10.3 version. Is there a command i can use to add the new space or even see if the system can sees them? (3 Replies)
Discussion started by: Katkota
3 Replies

6. Shell Programming and Scripting

how floppy disks, CDs and flash drives (pen drives) are accessed in UNIX

hi how floppy disks, CDs and flash drives (pen drives) are accessed in UNIX? thanks (0 Replies)
Discussion started by: nokia1100
0 Replies
Login or Register to Ask a Question
CD(9)							   BSD Kernel Developer's Manual						     CD(9)

NAME
cd -- CDROM driver for the CAM SCSI subsystem DESCRIPTION
The cd device driver provides a read only interface for CDROM drives (SCSI type 5) and WORM drives (SCSI type 4) that support CDROM type com- mands. Some drives do not behave as the driver expects. See the QUIRKS section for information on possible flags. QUIRKS
Each CD-ROM device can have different interpretations of the SCSI spec. This can lead to drives requiring special handling in the driver. The following is a list of quirks that the driver recognize. CD_Q_NO_TOUCH This flag tell the driver not to probe the drive at attach time to see if there is a disk in the drive and find out what size it is. This flag is currently unimplemented in the CAM cd driver. CD_Q_BCD_TRACKS This flag is for broken drives that return the track numbers in packed BCD instead of straight decimal. If the drive seems to skip tracks (tracks 10-15 are skipped) then you have a drive that is in need of this flag. CD_Q_NO_CHANGER This flag tells the driver that the device in question is not a changer. This is only necessary for a CDROM device with multiple luns that are not a part of a changer. CD_Q_CHANGER This flag tells the driver that the given device is a multi-lun changer. In general, the driver will figure this out auto- matically when it sees a LUN greater than 0. Setting this flag only has the effect of telling the driver to run the initial read capacity command for LUN 0 of the changer through the changer scheduling code. CD_Q_10_BYTE_ONLY This flag tells the driver that the given device only accepts 10 byte MODE SENSE/MODE SELECT commands. In general these types of quirks should not be added to the cd(4) driver. The reason is that the driver does several things to attempt to determine whether the drive in question needs 10 byte commands. First, it issues a CAM Path Inquiry command to determine whether the protocol that the drive speaks typically only allows 10 byte commands. (ATAPI and USB are two prominent exam- ples of protocols where you generally only want to send 10 byte commands.) Then, if it gets an ILLEGAL REQUEST error back from a 6 byte MODE SENSE or MODE SELECT command, it attempts to send the 10 byte version of the command instead. The only reason you would need a quirk is if your drive uses a protocol (e.g., SCSI) that typically does not have a problem with 6 byte commands. FILES
/sys/cam/scsi/scsi_cd.c is the driver source file. SEE ALSO
cd(4), scsi(4) HISTORY
The cd manual page first appeared in FreeBSD 2.2. AUTHORS
This manual page was written by John-Mark Gurney <gurney_j@efn.org>. It was updated for CAM and FreeBSD 3.0 by Kenneth Merry <ken@FreeBSD.org>. BSD
September 2, 2003 BSD