Re: [Veritas-bu] ACSLS+SL8500 Issues Remain..
2007-09-01 13:52:50
LOL.... Sorry, don't check the date.. :"> I'm just look from Wesley who replied you also on 31 Aug.. :P
Regards, mTz
On 9/2/07,
Justin Piszcz <jpiszcz AT lucidpixels DOT com> wrote:
This is from 2006, did you just reply? I got everything working now.
On Sun, 2 Sep 2007, Martin Ruslan wrote:
> Justin, > the ACSLS has a few patches.. not only the firmware on the library, can you
> ask that to your STK support guy? > > Regards, > mTz > > > On 12/19/06, Justin Piszcz <jpiszcz AT lucidpixels DOT com> wrote: >>
>>> ACS_TCP_RPCSERVICE >>> ACS_SSI_SOCKET = media_server.your.domain.com 13741 >> >> These items are set. >> >>> ACSSA> display drive *,*,*,* -f type serial_num
>>> 2006-12-18 10:45:59 Display Drive >>> Acs Lsm Panel Drive Type Serial_num >>> 0 0 1 0 HP-LTO-2 HUM9X00200 >> Again, when I do the backups one media server at a time, there are no
>> issues. It is only when there is a *burst* of jobs, the SN's match the >> corresponding addresses for the drives. >> >>> 1. Tail the acsss_event.log (good for viewing results for the below
>> suggestio$ >> Yeah we get that LH_DRIVE_BUSY error. >> >> We're still investigating. >> >> Justin. >> >> On Mon, 18 Dec 2006, Scott Jacobson wrote:
>> >>> >>> Justin, >>> For my benefit as well, a review from all the suggestions. >>> 1.Make sure vm.conf has specific entries: >>> ACS_TCP_RPCSERVICE
>>> ACS_SSI_HOSTNAME = media_server.your.domain.com >>> ACS_SSI_SOCKET = media_server.your.domain.com 13741 >>> ENABLE_AUTO_PATH_CORRECTION (optional) >>> 2. From cmd_proc use:
>>> ACSSA> display drive *,*,*,* -f type serial_num >>> 2006-12-18 10:45:59 Display Drive >>> Acs Lsm Panel Drive Type Serial_num >>> 0 0 1 0 HP-LTO-2 HUM9X00200 >>> and make sure the serial numbers, acs, lsm, panel and drive number match
>> up with what is displayed under devices/hosts on the master server. >>> And though this is painful, I would again try: >>> 1. Tail the acsss_event.log (good for viewing results for the below
>> suggestions) >>> 2. From ACSSA use the mount command to move a tape into each drive and >> verify it lands in the correct acs, lsm, panel and drive by using *query >> drive all* and look for the vol ser.
>>> 3. From the Veritas device (Master/Media server) controlling the drives, >> use robtest to again move a tape into each drive and verify it lands in the >> correct acs, lsm, panel and drive, then look under Device Monitor and locate
>> the vol ser that is mounted and select Drive Details. Make sure the acs, >> lsm, panel and drive from Veritas matches the acs, lsm, panel and drive from >> *query drive all*. >>> If they don't match, 1) you may have a zoning problem or 2) you've
>> possibly configured your drives incorrectly with Veritas. >>> If that isn't it, I'll anxiously be awaiting to hear what Veritas finds. >>> Scott >>> >>>
>>>>>> Justin Piszcz <jpiszcz AT lucidpixels DOT com> 12/18/2006 9:58 AM >>> >>> Still not resolved, working with Veritas/STK on this.
>>> >>> On Mon, 18 Dec 2006, Hall, Christian N. wrote: >>> >>>> Justin, >>>> >>>> Did you get this resolved with Veritas tech support? What was the
>>>> outcome? >>>> >>>> -----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 Justin >>>> Piszcz >>>> Sent: Monday, December 11, 2006 10:25 AM
>>>> To: Veritas-bu AT mailman.eng.auburn DOT edu >>>> Subject: [Veritas-bu] ACSLS+SL8500 Issues Remain.. >>>> >>>> Hi all,
>>>> >>>> I tried everyone's suggestions thus far, have not had any luck though: >>>> >>>> 1) tried using TCP communication on all the media servers instead of
>> UDP >>>> 2) tried increasing the media unmount delay from 120 seconds to 600 >>>> seconds, 10 minutes >>>> >>>> And the problem remains/persists, I kick off 45 jobs and NetBackup
>> shows >>>> 32 active jobs. However 1/2 or 3 (random) jobs will hang saying >>>> 'Mounting MediaID' - I can check ACSLS and run query drive *, the tape >>>> it is requesting sometimes is and is not in the drive that it is
>>>> supposed to be in, confusing... For firmware, what is the >> current/latest >>>> firmware and for those who have SL8500s without any issues, what >>>> firmware are you running?
>>>> >>>> Justin. >>>> >>>> _______________________________________________ >>>> 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
>>> >> _______________________________________________ >> 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
|
|
|