I know the issue is not related to me, but David you just explained to
me why I have NEVER been able to get auto config to work. I have always
had to configure my robots and tape drives by hand. So I gave up on
ever trying auto config and have just stuck we the manual config.
Thanks for letting me know why I had issues with my first robot.
-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of David
McMullin
Sent: Wednesday, March 11, 2009 3:37 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] STK SL3000 - NBU 6.5.3
Saw this in " Additional NetBackup 6.5 Operational Notes 45"
Enhanced device discovery and auto configuration
This version of NetBackup enhances device discovery by upgrading the
Device Configuration Wizard so it now configures robots and drives in
StorageTek's Automated Cartridge System Library Software (ACSLS) and
ADIC's Scalar Distributed Library Controller (SDLC) libraries.
Note: For NetBackup ACS Robot Auto Configuration to work, the ACSLS
Server must be able to report the serial numbers of the robotic tape
drives. ACSLS 6.1 and later releases report drive serial numbers by
using the display command.
However, ACSLS can only report serial numbers when the drives report
their serial numbers to the library and the library reports the drive
serial numbers to ACSLS.
The following drives and libraries report drive serial numbers to ACSLS
and allow Auto Configuration:
| Drives:
T9x40x, LTO (Gen 1, 2, 3), DLT 7000 and later drives, T1000, and SDLT.
| Libraries:
SCSI attached and SCSI over Fibre Channel attached STK libraries 97xx,
L20/40/80, L180, L700, L700e, L5500, SL500, and SL8500.
The following drives and libraries do not report serial numbers to ACSLS
and must be configured manually:
| Drives:
9490 (TimberLine), SD3 (RedWood) and earlier drives.
| Libraries:
9310 (PowderHorn), 9360 (WolfCreek), 4410, and serial-attached 9740.
Note: NetBackup ACS Robot Auto Configuration will not work with
HSC/LibStation attached libraries since LibStation does not report drive
serial numbers.
You must configure these devices manually. ***** is this what you are
seeing?
David McMullin
----------------------------------------------------------------------
Date: Wed, 11 Mar 2009 13:30:58 +0000
From: "Clooney, David" <david.clooney AT bankofamerica DOT com>
Subject: [Veritas-bu] STK SL3000 - NBU 6.5.3
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Message-ID:
<94462EC4A32D6C4DB34699EF631CC78C047348FE AT ex2k.bankofamerica DOT com>
Content-Type: text/plain; charset=us-ascii
Hi All
Hit another snag in a new deployment, seem to be requiring knowledge
from the group on a number of occasions over the last couple of months,
its appreciated.
Our DR environment has just acquired an STK SL3000 and we are having
issues with the robotic config in NBU.
If you run the wizard the results are that NBU interprets the library as
remote for some unknown reason.
We have downloaded the device mappings and applied successfully however
don't seem to be able to get it working.
... message summarized ...
However, even I try add the library through tpconfig I just don't seem
to be able to get is working.
Anyone know of any gotach'a with this particular library??
Regards
David Clooney
Enterprise Storage Services
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
