Hello group,
I know that DDS is not the all-time best for doing backups, but... I have
a small system for testing purposes (Windows 2000) with an Archive Python
06408-XXX drive, which is supposed to be a DDS4. But, when (By chance) I
issued a SHOW LIBRARY command, this is what came back:
MMSV->libList: head=002274E0, tail=002274E0
Library DDSLIB1 (type MANUAL):
reference count = 0, online = 1, borrowed drives = 0, update count = 0
basicCfgBuilt = 1, libInfoBuild = 1, definingPathToLibrary = 0
addLibPath = 0, driveListBusy = 0
libvol_lock_id=0, libvolLock_count=0, SeqnBase=0
library extension at 00000000
autochanger list:
drive list:
DDSDRIVE1:
Device Class = 4MM,
RD Capabilities = 0000003F,
(DDS3C,DDS3,DDS2C,DDS2,DDS1C,DDS1),
WR Capabilities = 0000003F,
(DDS3C,DDS3,DDS2C,DDS2,DDS1C,DDS1),
Drive state: UNKNOWN, Drive Descriptor state = NO PENDING CHANGES,
online = 1, polled = 0,
Inquiry String = ,
Device Type From Inquiry = ,
update count = 0, checking = 0,
offline time/date: 00:00:00 1900/00/00
Clean Freq(GB)=-1, Bytes Proc(KB)=0, needsClean=0.
MANUAL-specific fields:
None
If you look at RD Capabilities and WR Capabilities, it only goes to DDS3.
Should I expect something in the TSM device driver, or should I go to the
drive's salesman and ask for a real DDS4 drive?
--
Paul Gondim van Dongen
Engenheiro de Sistemas
MCSE
Tivoli Certified Consultant - Storage Manager
VANguard - Value Added Network guardians
http://www.vanguard-it.com.br <http://www.vanguard-it.com.br>
Fone: 55 81 3225-0353
