Veritas-bu

[Veritas-bu] Catalog Compression

2006-03-22 05:43:53
Subject: [Veritas-bu] Catalog Compression
From: d_clooney AT yahoo DOT com (Clooney)
Date: Wed, 22 Mar 2006 02:43:53 -0800 (PST)
Hi all

Seem to be having an issue with drives going down within an ACS library setup.

Index DriveName              DrivePath                Type    Shared   Status
***** *********              **********               ****    ******   ******
  0   U17_drive0_1654        /dev/rmt/c16t15d0BESTnb  hcart2   No       UP
        ACS(1) Definition       ACS=1, LSM=6, PANEL=5, DRIVE=4
  1   U17_Drive1_1754        /dev/rmt/c16t15d1BESTnb  hcart2   No       UP
        ACS(1) Definition       ACS=1, LSM=7, PANEL=5, DRIVE=4
  2   U17_Drive2_1854        /dev/rmt/c16t15d2BESTnb  hcart2   No       UP
        ACS(1) Definition       ACS=1, LSM=8, PANEL=5, DRIVE=4
  3   U17_drive3_1954        /dev/rmt/c16t15d3BESTnb  hcart2   No       UP
        ACS(1) Definition       ACS=1, LSM=9, PANEL=5, DRIVE=4

Currently defined robotics are:
  ACS(1)     ACSLS server = gbahee01,
             volume database host = gbaheu17

Problem is that there is a cronned script in place to automatically UP drives
which has hidden the problem for quite some time, from /var/adm/syslog/syslog
we are seeing on a constant basis the below, a whole bunch of ACS error's
Down'ing drives . As i understand this, this does not seem to be a Netbackup
issue and more an ACS issue. In turn we are getting jobs that just hang and it
is causing major resource issues , can anyone point me in the right direction
as to where to start anyalysing the ACS setup and a point to start
troubleshooting this setup.

Thanks in advance,

David Clooney


Mar 22 07:58:48 gbaheu17 acsd[22662]: ACS(1) driveid 1,6,5,4 (device 0) is
being DOWNED, status: Robotic mount failure
Mar 22 08:14:21 gbaheu17 acsd[22662]: ACS(1) driveid 1,8,5,4 (device 2) is
being DOWNED, status: Robotic mount failure
Mar 22 08:14:36 gbaheu17 ltid[22605]: Request for media ID 408682 is being
rejected because it is in a DOWN drive
Mar 22 08:28:56 gbaheu17 acsd[22662]: ACS(1) driveid 1,6,5,4 (device 0) is
being DOWNED, status: Robotic mount failure
Mar 22 08:30:01 gbaheu17 ltid[22605]: Request for media ID 408262 is being
rejected because it is in a DOWN drive
Mar 22 08:55:02 gbaheu17 acsd[22662]: ACS(1) driveid 1,9,5,4 (device 3) is
being DOWNED, status: Robotic mount failure
Mar 22 09:19:40 gbaheu17 acsd[22662]: ACS(1) driveid 1,6,5,4 (device 0) is
being DOWNED, status: Robotic mount failure
Mar 22 09:22:54 gbaheu17 ltid[22605]: Request for media ID 408525 is being
rejected because it is in a DOWN drive

Mar 22 09:25:39 gbaheu17 acsd[14480]: ACS(1) Response has not been returned by
Mount command sequence 17305, ACS status = 72, STATUS_PENDING
Mar 22 09:27:56 gbaheu17 acsd[14722]: ACS(1) Response has not been returned by
Mount command sequence 17334, ACS status = 72, STATUS_PENDING
Mar 22 09:30:39 gbaheu17 acsd[14480]: ACS(1) Response has not been returned by
Mount command sequence 17305, ACS status = 72, STATUS_PENDING
Mar 22 09:32:56 gbaheu17 acsd[14722]: ACS(1) Response has not been returned by
Mount command sequence 17334, ACS status = 72, STATUS_PENDING
Mar 22 09:37:56 gbaheu17 acsd[14722]: ACS(1) Response has not been returned by
Mount command sequence 17334, ACS status = 72, STATUS_PENDING
Mar 22 09:40:39 gbaheu17 acsd[14480]: ACS(1) Response has not been returned by
Mount command sequence 17305, ACS status = 72, STATUS_PENDING
Mar 22 09:45:39 gbaheu17 acsd[14480]: ACS(1) Unsuccessful response returned by
Mount command sequence 17305, ACS status = 72, STATUS_PENDING








__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

<Prev in Thread] Current Thread [Next in Thread>