Greg
you could enable logging - I know when seeing this, its always been cable /
hardware related - worse case would be to scrub your storage unit / robot
and start again (worse case remember!!)
Best of luck!
Regards
Simon Weaver
3rd Line Technical Support
Windows Domain Administrator
EADS Astrium Limited, B32AA IM (DCS)
Anchorage Road, Portsmouth, PO3 5PU
Email: <mailto:Simon.Weaver at Astrium-eads.net> Simon.Weaver at
Astrium-eads.net
-----Original Message-----
From: Pero, Greg [mailto:GPero at downeysavings.com]
Sent: 08 June 2006 16:15
To: Johnny Oestergaard
Cc: veritas-bu at mailman.eng.auburn.edu
Subject: Re: [Veritas-bu] Inventory failed: unable to open robotic path
(201)
Thanks - I have a support call into them but have yet to speak to anyone.
Greg Pero
NetSys Systems Engineer Senior
Downey Savings
(949) 509-4488 - office
7142003420 at vtext.com <mailto:7142003420 at vtext.com> - pager/text message
(714) 200-3420 - cell
gpero at downeysavings.com
_____
From: Johnny Oestergaard [mailto:joe at joe.dk]
Sent: Wednesday, June 07, 2006 8:31 PM
To: Pero, Greg
Cc: veritas-bu at mailman.eng.auburn.edu
Subject: RE: [Veritas-bu] Inventory failed: unable to open robotic path
(201)
The error "inventory failed: unable to open robotic path" is very generic in
that it basicly can be anything.
First thing I would try is to update the driver for the library from the
vendor. And after that try to check if Veritas has a driver for your
library.
/johnny
_____
From: veritas-bu-bounces at mailman.eng.auburn.edu
[mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Pero, Greg
Sent: 7. juni 2006 22:40
To: veritas-bu at mailman.eng.auburn.edu
Subject: [Veritas-bu] Inventory failed: unable to open robotic path (201)
I have a single W3k server as the master connected via Adaptec 39160 SCSI
adapter to a Qualstar 46120 Robotic tape library. If the server reboots for
whatever reason - it appears Netbackup loses the path to the Robot. The OS
itself appears to be fine - the Robot, tape drives and scsi adapters all
appear in Device Manager. When I run "Configure Storage Devices" in
Netbackup - it recognizes the tape drives (as stand-alone) but not the Robot
itself. If I go into Device Manager and blow away the tape drives and Robot
and reboot - Netbackup will then see the robot when I run "Configure Storage
Devices". I assume this is related to the SCSI path changing and Netbackup
not being able to handle it. If I run "tpconfig - l" it reports 6 tape
drives with a status of "up" and it reports the tape library with a status
of "-". Is there a work around for this - or any way to configure it so
that the SCSI path does not change?
Thanks,
Greg
Greg Pero
NetSys Systems Engineer Senior
Downey Savings
(949) 509-4488 - office
7142003420 at vtext.com <mailto:7142003420 at vtext.com> - pager/text message
(714) 200-3420 - cell
gpero at downeysavings.com
This message and any attachments are for the intended recipient(s) only and
may contain privileged, confidential and/or proprietary information about
Downey Savings or its customers, which Downey Savings does not intend to
disclose to the public. If you received this message by mistake, please
notify the sender by reply e-mail and delete the message and attachments.
This email is for the intended addressee only.
If you have received it in error then you must not use, retain, disseminate or
otherwise deal with it.
Please notify the sender by return email.
The views of the author may not necessarily constitute the views of EADS
Astrium Limited.
Nothing in this email shall bind EADS Astrium Limited in any contract or
obligation.
EADS Astrium Limited, Registered in England and Wales No. 2449259
Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://mailman.eng.auburn.edu/pipermail/veritas-bu/attachments/20060609/83ab260c/attachment-0001.html
|
