Você está na página 1de 18

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 1 of 18

²©¿ÍÊ×Ò³ ×¢²á ½¨ÒéÓë½»Á÷ ÅÅÐаñ ¼ÓÈëÓÑÇéÁ´½Ó ÍƼö ͶËß ËÑË
²©¿ÍÊ×Ò³ ×¢²á ½¨ÒéÓë½»Á÷ ÅÅÐаñ ¼ÓÈëÓÑÇéÁ´½Ó
ÍƼö ͶËß ËÑË
¿Õ¼ä×ÔÓÉ
¶ÔÓÚÈÈ°®µÇɽµÄÈËÀ´Ëµ£¬Ñ©É½Ö®áÛÓÀÔ¶ÊÇÎÞ·¨¶ôÖƵÄÏòÍù¡£¡°
ΪʲôҪµÇɽ£¿¡±¡ª¡ª ¡°
ÒòΪɽÔÚÄÇÀ¡±Õâ¾äÖøÃûµÄ»Ø´ðÀ´×ÔÂíŵÀ¡ªµ±Ê±ÊÀ½çÉÏ×ʢÃûµÄµÇɽ¼Ò¡£
Ê×Ò³
ÎÄÕÂ
µ¼ÈëÎÄÕÂ
Ïà²á
ÒôÀÖ
²©¿ÍȦ
ÊղؼÐ
ÁôÑÔ
·¢
¹ÜÀí²©¿Í
maping.cublog.cn
±íÎÄÕÂ

¹ØÓÚ×÷Õß

maping.cublog.cn ±íÎÄÕ ¹ØÓÚ×÷Õß ÐÕÃû£ºÉ½ÔÚÄÇÀï Ö°Òµ£º¡°°¤Ìß¡±
maping.cublog.cn ±íÎÄÕ ¹ØÓÚ×÷Õß ÐÕÃû£ºÉ½ÔÚÄÇÀï Ö°Òµ£º¡°°¤Ìß¡±

ÐÕÃû£ºÉ½ÔÚÄÇÀï

Ö°Òµ£º¡°°¤Ìß¡±

ÄêÁ䣺²»Òª³¤´ó

λÖãºÕ¾ÔÚ±±Î³30¡ã

¸öÐÔ½éÉÜ£ºÉ¶¸öÐÔµÄûÓÐ

|| <<

>> ||

ÎҵķÖÀà

ÎҵķÖÀà  
 
<< >> || ÎҵķÖÀà   STK ACSLS and Veritas NetBackup media TABLE OF CONTENTS 1.

STK ACSLS and Veritas NetBackup media

TABLE OF CONTENTS 1. LOGGING

1.1 LOG LOCATIONS 1.1.1 Event Logs

1.2 ACS PROCESS TRACING

1.2.1 ACSSSI Tracing on the VERITAS NetBackup ™ media server

1.2.2 ACSSS Tracing on the Library Server

2 ACS LIBRARY SERVER (ACSLS) FUNCTIONS AND COMMANDS

2.1 ACCESS CONTROL ON THE ACS LIBRARY SERVER (ACSLS)

2.2 ACSSA COMMANDS ON THE ACS LIBRARY SERVER

2.2.1 Log on to the ACSLS Server 2.2.2 Query the Library Management Unit 2.2.3 Query the Cartridge Access Ports 2.2.4 Query silos (Library Storage Modules)

2.2.5 Query Drives

2.2.6 Query Volumes

2.2.7 Command to Start Request Processing

2.2.8 Vary on LSM

2.2.9 Logoff from ACSSA (ACSLS Server interface)

2.3 ACSLS TAPE CLEANING

3 DEVICE CONFIGURATION FOR ACSLS CONTROLLED TAPE DRIVES

3.1 DEVICE CONFIGURATION

3.1.1 SSO Device Configuration for ACSLS

3.1.2 NON-SSO Device Configuration for ACSLS

3.1.3 Initial configuration of StorageTek T9940A and T9940B tape dri

environment

4 ROBTEST FOR ACS LIBRARIES

4.1 INVOKING ROBTEST

4.2 ROBTEST SYNTAX

4.2.1 Command to Obtain Drive Status

4.2.2 Command to Query Volumes

4.2.3 Command to Mount a Volume

4.2.4 Command to Dismount a Volume

4.3 HOW TO DEFINE ACSLS SCRATCH POOLS AND ADD VOLUMES

5 MEDIA

5.1 AVAILABLE MEDIA SCRIPT

5.2 HOW TO SPECIFY WHICH MEDIA ACCESS PORT (MAP) TO USE

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 2 of 18

6 COMMUNICATION

6.1 REMOTE PROCEDURE CALL

6.1.1 How to Start RPC on Different Operating Systems

6.1.2 How to Verify that RPC is Running

6.1.3 How to Verify the ACSSS Program Registration

6.1.4 Basic snoop Output

7 COMMON ACS ERROR MESSAGES

7.1 ACS (2) UNAVAILABLE: INITIALIZATION FAILED: UNABLE TO INI

7.2 ACS STATUS = 54, STATUS_IPC_FAILURE

7.3 ACS STATUS = 72, STATUS_PENDING

7.4 STATUS_NI_FAILURE

7.4.1 ACS status = 104, STATUS_NI_FAILURE

7.4.2 ACS status = 105, STATUS_NI_TIMEDOUT

1. LOGGING This section covers ACSLS log locations and ACS process tracing.

1.1 LOG LOCATIONS

1.1.1 Event Logs

Event log location on NetBackup media server: /usr/openv/volmgr/debug/

Event log location on ACS Library Server: /export/home/ACSSS/log/acsss (There is also an install, configuration change, and statistics log in the same

Typical event log entries are cap operations, remote procedure call (RPC) a robot errors, NI failures, and drive status changes.

1.2 ACS PROCESS TRACING

1.2.1 ACSSSI Tracing on the VERITAS NetBackup media server

1.2.1.1 To turn on acsssi tracing on the NetBackup media server, send the acsssi process as follows:

a. Ensure this directory exists:

/usr/openv/volmgr/debug/acsssi

b. Find the acsssi PID by running the command:

/usr/openv/volmgr/bin/vmps

c. Toggle on acsssi tracing:

kill -USR1 <pid of acsssi>

(This will start a trace.log in the /usr/openv/volmgr/debug/acsssi director

d. To turn off acsssi tracing:

kill -USR1 <pid of acsssi>

Tracing can be turned on or off multiple times using the same kill comm

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 3 of 18

NOTE: To read the trace.log, it is necessary to use the StorageTek trace_d StorageTek for a copy and instructions for use.

1.2.2 ACSSS Tracing on the Library Server

1.2.2.1 To turn on the Library Server ability to trace the ONC RPC sessi packets exchanged between the media server (SSI) and Library Server

a. Run toggle with the option "on" located in /export/home/ACSSS/diag

#./toggle on

b. To turn on CSI tracing, simply send a SIGUSR1 signal to the CSI process

accomplished by using the kill command as follows:

# kill -USR1 [CSI pid]

NOTE: It is necessary to first get the PID of the CSI using the ps command

Once enabled, an acsssi_trace.log will be created in the /export/home/AC log file contains a record of all packet activity between the media server and Each packet is displayed with a time stamp, the direction of the packet, the port, identifier, and a hex dump of the contents of the packet. To read the tr to use the StorageTek trace_decode. Please contact StorageTek for a cop use. The decoder from StorageTek will output each packet with the time sta (to or from the ACSLS), the command type (i.e. start), the packet type (i.e. r number of bytes in the packet and the values of each of the fields in the CSI header structures, plus any command specific parameters. For each field in offset, size, and value (in hex and ASCII) are also given.

To turn off tracing, use the same method used to turn on tracing. Tracing ca multiple times using the same command.

For Windows:

Windows event logging is turned on using the mini_el and the ACSSEL fun ACS product. The packet trace is controlled using the toggle_trace script. B Program Files\StorageTek\LibAttach\bin directory.

NOTE: Do not leave tracing on indefinitely because it may fill disk space ove

2. ACS LIBRARY SERVER (ACSLS) FUNCTIONS AND COMMANDS

This section covers ACSLS functions and commands.

2.1 ACCESS CONTROL ON THE ACS LIBRARY SERVER (ACSLS)

Under ACSLS there exists the ability to control command and volume acces client identification files and a series of allow or disallow files to manage acc control files reside on the ACSLS library server in the $ACS_HOME/data/ex directory. The internet.addresses file allows access control of hosts. ACSL against the user_id field in the received RPC request packet to determine w packet on for further processing. A non-zero return code for this operation w STATUS_INVALID_OPTION response being sent back to the media server.

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 4 of 18

Volume control can be done through the set owner command in the cmd_p ownership.assignment. A 'STATUS_INVALID_OPTION' status will return t rejected due to access control violations.

Volume access control applies to the following commands:

dismount, lock, mount_readonly, set_clean, set_scr mount, query_volume, set_owner, unlock

For further information on access control, please contact StorageTek.

2.2 ACSSA COMMANDS ON THE ACS LIBRARY SERVER

2.2.1 Log on to the ACSLS Server

# su - acsss

At the prompt, enter:

$ cmd_proc -ql

Wait for the ACSSA> prompt.

2.2.2 Query the Library Management Unit

ACSSA> q lmu all 2004-01-28 14:24:10

LMU Status

ACS:

0

Mode: SCSI LMU

Master

Status: Communicating

Standby Statu

Port

Port State

Role

CL

Port Name

0, 0

online

-

- /dev/mchanger2

2.2.3 Query the Cartridge Access Ports

ACSSA> q cap all

2004-01-28 14:25:30

CAP Status

Identifier

Priority Size State

Mode

0, 0,0

0

10

online

automa

2.2.4 Query silos (Library Storage Modules)

ACSSA> q lsm all 2004-01-28 14:26:22 Identifier State Cell Audit Mount

LSM Status

Free

Dismount Enter Eject

 

Count

C/P

C/P

C/P

C/P

0, 0

online

36

0/0

0/0

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 5 of 18

0/0

0/0

2.2.5 Query Drives

ACSSA> q drive all 2004-01-28 14:27:34

Identifier

State

Drive Status

Status

Volume

0, 0, 0, 0 online

available

0, 0, 0, 1 online

available

0, 0, 0, 2 online

available

0, 0, 0, 3 online

available

2.2.6 Query Volumes

ACSSA> q volume all 2004-01-28 15:58:36 Identifier Status

Volume Status Current Location

000002

home

0, 0,

1, 0, 0

000003

home

0, 0,

0, 2, 0

000004

home

0, 0,

0, 3, 0

000005

home

0, 0,

1, 5, 0

000006

home

0, 0,

1, 8, 1

000008

home

0, 0, 0,23, 0

000009

home

0, 0, 1,12, 1

<snip!> 2004-01-28 15:58:37

Identifier Status

Volume Status

Current Location

000047

home

0, 0,

1, 9, 0

000048

home

0, 0, 1,10, 1

000049

home

0, 0,

0, 7, 0

000050

home

0, 0,

0, 4, 0

FX0023

home

0, 0,

0, 0, 0

2.2.7 Command to Start Request Processing

ACSSA> start Start: ACSLM Request Processing Started: Success.

2.2.8 Vary on LSM

ACSSA> vary lsm LSM identifier (acs,lsm): 0,0 LSM identifier (acs/lsm):

State(diagnostic/offline/online): online 2004-03-26 11:20:53 107 LSM 0,0: online ACSSA> LSM 0,0 varied online

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 6 of 18

2.2.9 Logoff from ACSSA (ACSLS Server interface)

ACSSA> logoff

2.3 ACSLS TAPE CLEANING

ACS robot types are self cleaning. Tape cleaning should not be initiated by TapeAlert-based cleaning flag is set by LTID or avrd for an ACS, TLH, or an will not release the drives.

To disable TapeAlert checking and eliminate "TapeAlert is not supported" m add the NO_TAPEALERT touch file.

For UNIX:

/usr/openv/volmgr/database/NO_TAPEALERT

For Windows:

<install path>\volmgr\database\NO_TAPEALERT

The StorageTek library transport control unit tracks how much tape passes t and sends a message to ACSLS when a transport requires cleaning. If auto ACSLS automatically mounts a cleaning cartridge on the transport. If all the expired (MAX_USAGE), ACSLS will post an error message 376N into the a cleaning is disabled, ACSLS logs a message in the event log and displays a cmd_proc when cleaning is required.

This option is enabled or disabled using the acsss_config configuration util you to specify how the cartridges are ordered for selection and queries.

NOTE: You cannot use the acsss_config configuration program to enable attached to a SCSI connected library storage module (LSM).

For more information regarding ACSLS tape cleaning, please contact Stora

3. DEVICE CONFIGURATION FOR ACSLS CONTROLLED TAPE DRIVE

This section covers device configuration.

3.1 DEVICE CONFIGURATION

NOTE: All Automated Cartridge System (ACS) robots configured on a medi configured with at least one drive, or the acsd daemon will exit, putting all A System Library Software (ACSLS) drives in Automatic Volume Recognition

3.1.1 SSO Device Configuration for ACSLS

During setup (in the Device Configuration Wizard), NetBackup will attempt t drives available to it and, for robot types where serialization is available, the library.

NetBackup does not yet obtain drive serial numbers from the ACS robotic lib

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 7 of 18

manual configuration is required. The manual configuration cannot be avoid Storage Option (non-SSO) environment, where drives are not being shared. FP6, the user can significantly reduce the amount of manual configuration r these steps in an SSO environment.

1. Run the device configuration wizard on just one of the hosts where drives

library are attached. Let the drives be added as standalone drives.

2. Add the ACS robot definition, and update each drive to indicate its approp

robot. (Make the drive robotic, and add the ACS, LSM, Panel, and Drive info VERITAS Media Manager System Administration Guide, Configuring Storag the section "Co-relating Device Files to Physical Drives When Adding Drives

3. Verify the drive paths, if this hasn't already been done in the previous ste

documentation referenced above

4. Once the drive paths have been verified on one host, re-run the device co

specify all hosts with ACS drives in the library to be scanned. The device co

add the ACS robot definition and the drives to the remaining servers automa device paths, assuming that the devices were successfully discovered, alon numbers.

By following the above steps, the time savings can be significant. For exam shared on 30 hosts, the above configuration steps require just 20 paths to b instead of 600 paths.

3.1.2 Non-SSO Device Configuration for ACSLS

During setup (in the Device Configuration Wizard), NetBackup will attempt t drives available to it, and, for robot types where serialization is available, the library. Do not use the Device Configuration Wizard. NetBackup does not o numbers from the ACS robotic library control interface, so manual configura

3.1.3 Initial configuration of StorageTek T9940A and T9940B tape drive

environment

It is advised to separate the two drive types within the NetBackup Media Ma configuration to alleviate density conflicts.

This issue surfaces because ACS treats the T9940A and T9940B drive med the T9940B version writes at a higher density therefore the T9940A drive ca by a T9940B drive. So, when trying to use both drives within a single library, be used for each drive. The same issue will occur with SDLT220 and SDLT ACS-based library.

Workaround:

Add the ACS robot to the NetBackup device configuration according to the s the NetBackup Media Manager Device Configuration Guide. Configure the STK 9940A drives as type hcart and configure the STK 9940B Then define a NetBackup storage unit for each density, hcart and hcart2.

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 8 of 18

Steps to inventory media for each density type:

1. In the /usr/openv/volmgr/vm.conf file on the server where vmupdate is

add "IGNORE_WRONG_MEDIA_TYPE" to the end of the file

2. Run /usr/openv/volmgr/bin/vmupdate -rn <robot num

acs_stk2p hcart

-- All new media found will be configured as hcart

3. Next, add the STK 9940B media to the robot

4. Finally, run /usr/openv/volmgr/bin/vmupdate -rn <robo

acs -acs_stk2p hcart2

-- All new media found will be configured

When an inventory of ACS robotics is done, NetBackup will receive a vendo well as the barcode. That vendor media type is mapped to one of the NetBa tag "IGNORE_WRONG_MEDIA_TYPE" allows NetBackup to map a single to multiple NetBackup media types.

Disadvantages:

1. If for any reason, media is ejected from the library, verification is required

that it goes to the correct media type (hcart for 9940A, hcart2 for 9940B).

2.

T9940B drives cannot be used to read the 9940A media; they have to be

4

ROBTEST FOR ACS LIBRARIES This section covers acstest (robtest)

4.1 INVOKING ROBTEST

# /usr/open/volmgr/bin/robtest

Configured robots with local control supporting test utilities:

ACS(0)

Robot Selection

---------------

1)

2) none/quit Enter choice: 1

Robot selected: ACS(0)

Invoking robotic test utility:

/usr/openv/volmgr/bin/acstest -r taco -s 13741 -d 0,3,1,0Server 0 with 24 free cells is in state "STATE_RUN"

QUERY SERVER complete Enter acs commands (? returns help information)

ACSLS host = taco

ACS 0

ACSLS host = taco, SSI so

4.2 ROBTEST SYNTAX

?

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 9 of 18

To exit the utility, type q or Q.

- Cancel serv

defpool <pool> <lwm> <hwm> <attrib> - Define scra

delpool <pool> dm <vol> [<drive>|<drive_id>] [f] (optionally forced) drstat <drive_id> eject <cap_id> <vol_list> the specified CAP enter <cap_id> specified CAP capstat [<cap_id>] varycap <cap_id> online|offline CAP setmode <cap_id> automatic|manual CAP setpriority <cap_id> <priority> given CAP m <vol> [<drive>|<drive_id>] qmmi information qpool [<pool>] qreq [<request_id>] qscr [<pool>] pool qserver qvol [<vol>] setscr <pool> ON|OFF <vol> [<vol>] volume range start (request RUN state) types media types

- set the pri

- set the mod

cancel <request_id>

- Delete empt - Dismount vo

- Print drive - Eject a lis

- Enter volum

- Print CAP s - set the sta

- Mount volum - Query actua

- Query pools - Query serve - Query scrat

- Query ACSLS - Query volum - Set scratch

- Start ACS L

- Print list

SCSI commands:

unload <drive>|<drive_id>

where:

<acs>=0-126, <lsm>=0-23, <cap>=0-2, <drive>=0-15, <drive_id> = [<acs>,<lsm>,<panel>,<drive>]

<drive> = d1 if drive 1, d2 if drive 2, <lwm> = scratch pool low water mark <hwm> = scratch pool high water mark

- Issue SCSI

, d15 i

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 10 of 18

<cap_id> = <acs>,<lsm>,<cap> <vol_list> = <vol1>[:<vol2>:

4.2.1 Command to Obtain Drive Status

drstat

Drive 1 information:

ID (acs,lsm,panel,drv): 0,0,0,0

:<vol42>]

drive type:

DLT7000

volume ID:

<none>

state:

STATE_ONLINE

status:

STATUS_DRIVE_AVAILABLE

Drive 2 information:

ID (acs,lsm,panel,drv): 0,0,0,1

drive type:

DLT7000

volume ID:

<none>

state:

STATE_ONLINE

status:

STATUS_DRIVE_AVAILABLE

Drive 3 information:

ID (acs,lsm,panel,drv): 0,0,0,2

drive type:

9840

volume ID:

<none>

state:

STATE_ONLINE

status:

STATUS_DRIVE_AVAILABLE

Drive 4 information:

ID (acs,lsm,panel,drv): 0,0,0,3

drive type:

9840

volume ID:

<none>

state:

STATE_ONLINE

status:

STATUS_DRIVE_AVAILABLE

DRIVE STATUS complete

4.2.2 Command to Query Volumes

qvol

000002

STK1R

home

0, 0, 1, 0,

0

000003

STK1R

home

0, 0, 0, 2,

0

000004

STK1R

home

0, 0, 0, 3,

0

000005

STK1R

home

0, 0, 1, 5,

0

000006

STK1R

home

0, 0, 1, 8,

1

000008

STK1R

home

0, 0, 0, 23, 0

QUERY VOLUME complete

4.2.3 Command to Mount a Volume

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 11 of 18

m 000040 0,0,0,2

MOUNT complete

4.2.4 Command to Dismount a Volume

dm 000040 0,0,0,2 f

DISMOUNT complete

4.3 HOW TO DEFINE ACSLS SCRATCH POOLS AND ADD VOLUMES U

Start the robtest utility:

On UNIX:

# /usr/openv/volmgr/bin/robtest

On Windows:

<install_path>veritas\volmgr\bin\robtest.exe

Select the ACS robot. Enter the 'define pool' command as follows:

defpool 4 0 500 1 Scratch pool 4 has been defined

NOTE: DEFINE POOL completes robot inventories for ACS, where 4 is the pool number where 0 500 is the low and high water marks where 1 is overflow on (could be 0 for overflow off)

Next, define ACSLS scratch volumes in this pool:

qpool 4 Pool ID 4 has 0 volumes QUERY POOL complete

setscr 4 ON 000040 000044

000040 STATUS_SUCCESS

000041 STATUS_SUCCESS

000042 STATUS_SUCCESS

000043 STATUS_SUCCESS

000044 STATUS_SUCCESS

SET SCRATCH complete

qpool 4 Pool ID 4 has 5 volumes QUERY POOL complete

Quit 'robtest' and perform a normal robot inventory with NetBackup.

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 12 of 18

5 MEDIA This section covers "available_media" script output and tape ejection.

5.1 AVAILABLE MEDIA SCRIPT

The utility /usr/openv/netbackup/bin/goodies/available_media does not r for ACS libraries. This is not a bug. The information on slot location is mana Media Manager.

Below is a sample output from the available_media report, which can be ge following command:

Windows: <install_path>\netbackup\bin\goodies\avail

or

UNIX: /usr/openv/netbackup/bin/goodies/available_me

media

media robot

robot robot

side/

ret

ID

type

type

#

slot

face

level

--------------------------------------------------

-----------------------------

NetBackup pool NB0001 DLT

ACS

0

-

-

0

NB0002 DLT

ACS

0

-

-

0

ABC234 DLT

ACS

0

-

-

-

AVAILABLE ABC345 DLT AVAILABLE

ACS

0

-

-

-

5.2 HOW TO SPECIFY WHICH MEDIA ACCESS PORT (MAP) TO USE F

In the media server's /usr/openv/volmgr/vm.conf file, it is possible to speci (MAP) to use when ejecting media to a particular ACS robot. If this entry is p (including the Vault extension) will eject to the specified MAP instead of the

The vm.conf entry syntax:

MAP_ID = robot-num map-id

Example: If a user wants the ACS(0) robot to eject via its 0,0,1 MAP and the via its 0,1,0 MAP, the following vm.conf entries would be necessary on the these robots:

MAP_ID = 0 0,0,1 MAP_ID = 1 0,1,0

6. COMMUNICATION This section covers RPC and communication.

6.1 REMOTE PROCEDURE CALL (RPC)

NetBackup uses RPC to connect to the ACSLS server, and rpcbind is the se program numbers into universal addresses. It must be running on the host t

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 13 of 18

calls on a server on that machine.

6.1.1 How to start RPC on different operating systems

Starting RPC is best accomplished using the operating system vendor startu are the ways of starting RPC on various operating systems.

a. Solaris

# /etc/init.d/rpc start

b. HP-UX

# /sbin/init.d/Rpcd start

c. AIX

# startsrc -s portmap

d. Linux

# /etc/rc.d/init.d/portmap start

e. Tru/64

# /usr/sbin/portmap

f. Windows Click Start | Settings | Control Panel | Administrative Tools | Services Procedure Call (RPC) and click Start.

6.1.2 How to Verify that RPC is Running

The following commands will verify that the rpcbind is active and that the R between the media server and ACSLS Library Server. From a terminal wind issue the following command to ACSLS.

# rpcinfo

program version netid

address

serv

100000

4

ticots

hotdog.rpc

rpcbi

100000

3

ticots

hotdog.rpc

rpcbi

100000

4

ticotsord hotdog.rpc

rpcbi

100000

3

ticotsord hotdog.rpc

rpcbi

100000

4

ticlts

hotdog.rpc

rpcbi

100000

3

ticlts

hotdog.rpc

rpcbi

100000

4

tcp

0.0.0.0.0.111

rpcbi

100000

3

tcp

0.0.0.0.0.111

rpcbi

100000

2

tcp

0.0.0.0.0.111

rpcbi

100000

4

udp

0.0.0.0.0.111

rpcbi

100000

3

udp

0.0.0.0.0.111

rpcbi

100000

2

udp

0.0.0.0.0.111

rpcbi

If the service is not running, rpcinfo will report: "can't contact rpcbind: RPC:

Failed ( unspecified error )" Examine the /export/home/ACSSS/log/acsss_event.log for "RPC: Rpcbin message should include an IP that it is trying to communicate with. Verify it

6.1.3 How to Verify the ACSSS Program Registration

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 14 of 18

#rpcinfo -t {acsls_hostname} 300031 2 program 300031 version 2 ready and waiting #rpcinfo -t {acsls_hostname} 300031 1 program 300031 version 1 ready and waiting

You should get a response from both programs, but you only need a respon you are using (2 = UDP or 3 = TCP). The NetBackup default for this communications servi

6.1.4 Basic snoop Output

Basic snoop of a query server sent automatically by initiating the robtest utili

# snoop salid carter

1 0.00000

GETPORT prog=300031 (?) vers=1 proto=UDP

2 0.00108 carter.min.veritas.com -> salad GETPORT port=1025

3 0.00056

XID=1066379121 PROG=300031 (?) VERS=1 PROC=1000

salad -> carter.min.veritas.com

salad -> carter.min.veritas.com

4 0.00091 carter.min.veritas.com -> salad

XID=1066379121 Success

5 0.00459 carter.min.veritas.com -> salad

XID=1066114434 PROG=1073741824 (transient) VERS=1

6 0.00031

XID=1066114434 Success

salad -> carter.min.veritas.com

7 0.15656 carter.min.veritas.com -> salad

XID=1065841469 PROG=1073741824 (transient) VERS=1

salad -> carter.min.veritas.com

XID=1065841469 Success

This trace shows that the portmapper and program registration was success

8 0.00029

For additional assistance with NetBackup options as they pertain to ACSLS, Manager System Administrator's Guide.

7 COMMON ACS ERROR MESSAGES This section covers common ACSLS error messages.

7.1 ACS(2) UNAVAILABLE: INITIALIZATION FAILED: UNABLE TO INITI

Resolution: Verify the IP address specified for the robotic host is correct in server.

7.2 ACS STATUS = 54, STATUS_IPC_FAILURE

Robtest will show:

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 15 of 18

acs_query_server() failed Unable to query server taco, ACS status = 54, STAT Robotic test utility /usr/openv/volmgr/bin/acstest returned abnormal exit status (1). STATUS_PENDING

Cause: local network interface is down.

7.3 ACS STATUS = 72, STATUS_PENDING

Example 1:

robtest will show:

acs_response() failed Unable to obtain Query Server acknowledge response 72, STATUS_PENDING Robotic test utility /usr/openv/volmgr/bin/acstest returned abnormal exit status (1).

Media Server event.log will log:

02-05-04 13:49:18 SSI[0]:

ONC RPC: csi_rpccall(): status:STATUS_NI_FAILURE; clntudp_create() RPC UDP client connection failed, RPC: Rpcbind fai Remote Internet address:10.82.56.67, Port: 0

Cause: ACSLS server network interface is down

Example 2:

Media server system log :

Nov 15 11:18:06 hoehpt07 acsd[8807]: ACS(0) Respon returned by Mount command sequence 4434, ACS statu STATUS_PENDING Nov 15 11:28:06 hoehpt07 acsd[8807]: ACS(0) Respon returned by Mount command sequence 4434, ACS statu STATUS_PENDING

Event log from the ACSLS :

2003-05-22 11:33:51 CSI[0]:

1022 N csi_net_send.c 1 474

ONC RPC: csi_net_send(): status:STATUS_NI_TIMEDOUT st_net_send() Cannot send message to NI:discarded, timeout Errno = 0 (none) Remote Internet address:

Port: 53429

2003-05-22 11:33:51 CSI[0]:

1026 N csi_freeqmem.c 1 142

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 16 of 18

ONC RPC: csi_freeqmem(): status:STATUS_QUEUE_FAILU Dropping from Queue: Remote Internet address:

207.169.154.59,Port: 53429 , ssi_identifier: 1, Pr Connect type: 1

2003-05-22 11:33:51 ACSSA[0]:

1432 N sa_demux.c 1 273 Server System network interface timeout.

Cause:

The errors above indicate that NetBackup is able to reach the ACSLS serve but the ACSLS server is unable to respond.

By default, the IP address sent to the ACSLS as part of the packet STATUS primary hostname of the media server, i.e. the hostname given by uname when the ACSLS cannot resolve reverse name or is configured (via routing) secondary interface on the media server.

If the issue is failure to do reserve name lookup, add the media server's IP t service (DNS) reverse tables or to the ACSLS /etc/hosts file. If the ACSLS server cannot route to the media server's hostname, override t using "ACS_SSI_HOSTNAME = <hostname>" in the /usr/openv/volmgr/vm value for <hostname> is a hostname associated with an IP address the ACS media server.

7.4 STATUS_NI_FAILURE

Explanation of message: STATUS_NI_TIMEDOUT:

The CSI (media server) has timed out waiting for a response from a client (A actual "Waiting to obtain XXXXX ACS sequence YYY acknowledge respons daemon has not received an acknowledgment from the LibraryStation modu is a hard-coded limit) following a sent command. "Unable to obtain" means i The timeouts seen occur after a 30 second delay, when no acknowledgmen These timeout periods are determined by two tunable environment variables

CSI_RETRY_TIMEOUT - The default for which is 3 seconds, not 2 as descr Management manual. CSI_RETRY_TRIES - The default for this is 5 retries.

Changes: Add the following to /usr/openv/volmgr/vm.conf on the media se

CSI_RETRY_TIMEOUT=30

CSI_RETRY_TRIES=10

or

Change the OS environment variable CSI_RETRY_TIMEOUT to 30 and CS From bash/ksh prompt:

#CSI_RETRY_TIMEOUT=30;export CSI_RETRY_TIMEOUT #CSI_RETRY_TRIES=10;export CSI_RETRY_TRIES

Add to the NetBackup startup script for a permanent solution.

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 17 of 18

Isolating the problem:

a. Ensure that the media server can successfully ping the ACS server and v

b. Check that ltid has started the acsd, acsssi and assel service daemons

server by performing a bpps -a from /usr/openv/netbackup/bin or vmp

from /usr/openv/volmgr/bin/volmgr. If acsssi is not running, ensure that R

c. Run snoop between the media server and ACS. Initiate robtest and chec

sent upon robtest initialization, is responded to by the ACSLS server (refere

d. Verify the RPC communications between the media server and ACSLS h

command. The rpcinfo -t <acs_host> 300031 1 h comman

connectivity, portmapper registration and that the ACSLS program (service) (reference 'How to start RPC' above).

e. Check the event logs from the media server and library server for errors (

above)

f. Check the syslog or event file for errors

g. Enable tracing (reference Logging above)

h. This error can occur if the users.ALL.allow file on the ACSLS Library Se

entry for the requesting media server. This file is found on the ACSLS serve

$ACS_HOME/data/external/access_control directory and is used for gran access. For example, entries of the users.ALL.allow consult the ACSLS ad

7.4.1 ACS status=104, STATUS_NI_FAILURE

robtest will show:

acs_response() failed Unable to obtain Query Server acknowledge response 104, STATUS_NI_FAILURE Robotic test utility /usr/openv/volmgr/bin/acstest returned abnormal exit status (1).

acsssi event.log:

02-05-04 13:31:54 SSI[0]:

ONC RPC: csi_rpccall(): status:STATUS_NI_FAILURE; clntudp_create() RPC UDP client connection failed, RPC: Program not Remote Internet address:10.82.56.67, Port: 0;

Cause: ACSLS is down or not responding

7.4.2 ACS status = 105, STATUS_NI_TIMEDOUT

Example of the message log:

Aug 26 17:06:57 sdhra1a acsd[15914]: ACS(0) Unable Query ACS sequence 3420 acknowledge response, ACS STATUS_NI_TIMEDOUT Aug 26 17:06:57 sdhra1a acsd[5476]: DecodeDismount driveid 0,0,10,5, Actual status: Unable to initial Aug 26 17:06:57 sdhra1a acsd[5476]: ACS(0) going t

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ

Page 18 of 18

status: Unable to initialize robot Aug 26 17:07:15 sdhra1a acsd[15910]: ACS(0) Waitin Query Drive sequence 3381 acknowledge response, AC STATUS_PENDING

Cause: The CSI (media server) has timed out waiting for a response from a

·¢±íÓÚ£º 2006-12-03£¬ÐÞ¸ÄÓÚ£º 2006-12-03 13:09£¬ÒÑä¯ÀÀ2069´Î£¬ÓÐ

¡¡·¢±íÆÀÂÛ

Óû§Ãû£º

ÑéÖ¤Â룺

¡¡·¢±íÆÀÂÛ Óû§Ãû£º ÑéÖ¤Â룺 ÃÜÂ룺 ¡¡ g f e d c ÄäÃû

ÃÜÂ룺

¡¡ gfedc ÄäÃû

ÍøÓÑÆÀÂÛ

¡¡ g f e d c ÄäÃû ÍøÓÑÆÀÂÛ Ãâ·Ñ×¢²á Ìá½»

Ãâ·Ñ×¢²á

Ìá½»