Hi All,
I'm doing upgrading tape library to SL8500 with LTO 3, for unix env so
far running well but for win2003 SP1 even the server already can see the
drive (using veritas driver) and able to run query server on lib attach
( I've tried ver 1.3 and 1.4) backup still failed 219, I've check and
make
I am fighting this one.
I have Quantum M1500 lib with 2 LTO2 drives. Put in 3rd drive but it is
LTO3. Logically to me (and confirmed by people here) I should be able
to tell the drive to write hcat2 density and all should be well but it
is not. The installation notes from the drive said
Does anyone know how we can confirm what maint pack level we are running
on our Solaris clients. I tried to find this out
before but never got any hits. Is there a version command or something we
can run.
Running Netbackup Enterprise 5.1 mp6 on media servers. Backing up all
platforms. Need to
sigh This thread, rather than dispelling unsupported speculation, is
now generating it in droves. It's time to let it go, though I'll
cherry-pick a few points on the way out.
The only place where the drive index is stored, AFAIK, is in the
FRAGMENT records in the backup's metadata file, as
I agree with Bob, there is no affinity between physical
tape media and a physical tape drive.
You're obviously a man of keen intellect. :-)
However, what would have happened (and caused VX support to suggest
bpexpdate'ing the media) is a RVSN/EVSN mismatch. Consider a
[scenario of
* Bobby R Windle [EMAIL PROTECTED] [2006-12-29 22:43]:
Does anyone know how we can confirm what maint pack level we are running
on our Solaris clients. I tried to find this out
before but never got any hits. Is there a version command or something we
can run.
Running Netbackup Enterprise
