STK ACSLS and Veritas NetBackup Media Server

STK ACSLS and Veritas NetBackup media server - ¹¤×÷ - ¿Õ¼ä×ÔÓÉ Page 1 of 18
²©¿ÍÊ×Ò³ ×¢²á ½¨ÒéÓë½»Á÷ ÅÅÐÐ°ñ ¼ÓÈëÓÑÇéÁ´½Ó ÍÆ¼ö Í¶Ëß ËÑË
¶ÔÓÚÈÈ°®µÇÉ½µÄÈËÀ´Ëµ£¬Ñ©É½Ö®áÛÓÀÔ¶ÊÇÎÞ·¨¶ôÖÆµÄÏòÍù¡£¡°
¿Õ¼ä×ÔÓÉ ÎªÊ²Ã´ÒªµÇÉ½£¿¡±¡ª¡ª ¡°
ÒòÎªÉ½ÔÚÄÇÀï£¡¡±Õâ¾äÖøÃûµÄ»Ø´ðÀ´×ÔÂíÅµÀï¡ª¡ªµ±Ê±ÊÀ½çÉÏ×î¸»Ê¢ÃûµÄµÇÉ½¼Ò¡£
Ê×Ò³ ÎÄÕÂ µ¼ÈëÎÄÕÂ Ïà²á ÒôÀÖ ²©¿ÍÈ¦ ÊÕ²Ø¼Ð ÁôÑÔ ·¢ ¹ÜÀí²©¿Í

maping.cublog.cn ±íÎÄÕÂ
¹ØÓÚ×÷Õß
STK ACSLS and Veritas NetBackup media se
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)
Î»ÖÃ£ºÕ¾ÔÚ±±Î³30¡ã 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 drives
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 US
5 MEDIA
5.1 AVAILABLE MEDIA SCRIPT
5.2 HOW TO SPECIFY WHICH MEDIA ACCESS PORT (MAP) TO USE FO
file://H:\study\netbackup\Upload_site_done\done\New Folder\STK ACSLS and Veritas NetBackup media s... 7/6/2010

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 INITIA
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/acs
Event log location on ACS Library Server: /export/home/ACSSS/log/acsss_e

(There is also an install, configuration change, and statistics log in the same dir
Typical event log entries are cap operations, remote procedure call (RPC) and
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 an

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 directory.)
d. To turn off acsssi tracing:

kill -USR1 <pid of acsssi>
Tracing can be turned on or off multiple times using the same kill command

NOTE: To read the trace.log, it is necessary to use the StorageTek trace_dec

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 session
packets exchanged between the media server (SSI) and Library Server sy
a. Run toggle with the option "on" located in /export/home/ACSSS/diag/bi

#./toggle on
b. To turn on CSI tracing, simply send a SIGUSR1 signal to the CSI process. T
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/ACSS

log file contains a record of all packet activity between the media server and the
Each packet is displayed with a time stamp, the direction of the packet, the SSI
port, identifier, and a hex dump of the contents of the packet. To read the trace
to use the StorageTek trace_decode. Please contact StorageTek for a copy an
use. The decoder from StorageTek will output each packet with the time stamp
(to or from the ACSLS), the command type (i.e. start), the packet type (i.e. requ
number of bytes in the packet and the values of each of the fields in the CSI he
header structures, plus any command specific parameters. For each field in the
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 can b
multiple times using the same command.
For Windows:
Windows event logging is turned on using the mini_el and the ACSSEL functio
ACS product. The packet trace is controlled using the toggle_trace script. Both
Program Files\StorageTek\LibAttach\bin directory.
NOTE: Do not leave tracing on indefinitely because it may fill disk space over ti
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 access. A
client identification files and a series of allow or disallow files to manage access
control files reside on the ACSLS library server in the $ACS_HOME/data/exter
directory. The internet.addresses file allows access control of hosts. ACSLS w
against the user_id field in the received RPC request packet to determine whe
packet on for further processing. A non-zero return code for this operation will r
STATUS_INVALID_OPTION response being sent back to the media server.

Volume control can be done through the set owner command in the cmd_proc
ownership.assignment. A 'STATUS_INVALID_OPTION' status will return to c
rejected due to access control violations.
Volume access control applies to the following commands:

dismount, lock, mount_readonly, set_clean, set_scrat
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 Status:
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 automati
2.2.4 Query silos (Library Storage Modules)

ACSSA> q lsm all
2004-01-28 14:26:22 LSM Status
Identifier State Free
Cell Audit Mount Dismount Enter Eject
Count C/P C/P
C/P C/P
0, 0 online 36 0/0 0/0

0/0 0/0
2.2.5 Query Drives
ACSSA> q drive all
2004-01-28 14:27:34 Drive Status
Identifier State Status Volume
0, 0, 0, 0 online available DL
0, 0, 0, 1 online available DL
0, 0, 0, 2 online available 98
0, 0, 0, 3 online available 98
2.2.6 Query Volumes
ACSSA> q volume all
2004-01-28 15:58:36 Volume Status
Identifier 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 Volume Status
Identifier 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

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 Net
TapeAlert-based cleaning flag is set by LTID or avrd for an ACS, TLH, or an LM
will not release the drives.
To disable TapeAlert checking and eliminate "TapeAlert is not supported" mess

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 thro
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 cle
expired (MAX_USAGE), ACSLS will post an error message 376N into the acss
cleaning is disabled, ACSLS logs a message in the event log and displays a m
cmd_proc when cleaning is required.
This option is enabled or disabled using the acsss_config configuration utility.

you to specify how the cartridges are ordered for selection and queries.
NOTE: You cannot use the acsss_config configuration program to enable aut
attached to a SCSI connected library storage module (LSM).
For more information regarding ACSLS tape cleaning, please contact StorageT
3. DEVICE CONFIGURATION FOR ACSLS CONTROLLED TAPE DRIVES

This section covers device configuration.
3.1 DEVICE CONFIGURATION
NOTE: All Automated Cartridge System (ACS) robots configured on a media se

configured with at least one drive, or the acsd daemon will exit, putting all Auto
System Library Software (ACSLS) drives in Automatic Volume Recognition (AV
3.1.1 SSO Device Configuration for ACSLS
During setup (in the Device Configuration Wizard), NetBackup will attempt to d
drives available to it and, for robot types where serialization is available, their p
library.
NetBackup does not yet obtain drive serial numbers from the ACS robotic librar

manual configuration is required. The manual configuration cannot be avoided

Storage Option (non-SSO) environment, where drives are not being shared. Us
FP6, the user can significantly reduce the amount of manual configuration requ
these steps in an SSO environment.
1. Run the device configuration wizard on just one of the hosts where drives in
library are attached. Let the drives be added as standalone drives.
2. Add the ACS robot definition, and update each drive to indicate its appropria
robot. (Make the drive robotic, and add the ACS, LSM, Panel, and Drive inform
VERITAS Media Manager System Administration Guide, Configuring Storage D
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 step, b
documentation referenced above
4. Once the drive paths have been verified on one host, re-run the device confi
specify all hosts with ACS drives in the library to be scanned. The device config
add the ACS robot definition and the drives to the remaining servers automatic
device paths, assuming that the devices were successfully discovered, along w
numbers.
By following the above steps, the time savings can be significant. For example,
shared on 30 hosts, the above configuration steps require just 20 paths to be m
instead of 600 paths.
3.1.2 Non-SSO Device Configuration for ACSLS
During setup (in the Device Configuration Wizard), NetBackup will attempt to d
drives available to it, and, for robot types where serialization is available, their p
library. Do not use the Device Configuration Wizard. NetBackup does not obta
numbers from the ACS robotic library control interface, so manual configuration
3.1.3 Initial configuration of StorageTek T9940A and T9940B tape drives i

environment
It is advised to separate the two drive types within the NetBackup Media Manag
configuration to alleviate density conflicts.
This issue surfaces because ACS treats the T9940A and T9940B drive media a
the T9940B version writes at a higher density therefore the T9940A drive canno
by a T9940B drive. So, when trying to use both drives within a single library, dif
be used for each drive. The same issue will occur with SDLT220 and SDLT320
ACS-based library.
Workaround:
Add the ACS robot to the NetBackup device configuration according to the step
the NetBackup Media Manager Device Configuration Guide.
Configure the STK 9940A drives as type hcart and configure the STK 9940B dr
Then define a NetBackup storage unit for each density, hcart and hcart2.

Steps to inventory media for each density type:

1. In the /usr/openv/volmgr/vm.conf file on the server where vmupdate is run
add "IGNORE_WRONG_MEDIA_TYPE" to the end of the file
2. Run /usr/openv/volmgr/bin/vmupdate -rn <robot number
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 <robot n
acs -acs_stk2p hcart2 -- All new media found will be configured as
When an inventory of ACS robotics is done, NetBackup will receive a vendor m
well as the barcode. That vendor media type is mapped to one of the NetBacku
tag "IGNORE_WRONG_MEDIA_TYPE" allows NetBackup to map a single AC
to multiple NetBackup media types.
Disadvantages:
1. If for any reason, media is ejected from the library, verification is required wh
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 seg
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) ACSLS host = taco

Robot Selection
---------------
1) ACS 0
2) none/quit
Enter choice: 1
Robot selected: ACS(0) ACSLS host = taco, SSI sock
Invoking robotic test utility:
/usr/openv/volmgr/bin/acstest -r taco -s 13741 -d /d
0,3,1,0Server 0 with 24
free cells is in state "STATE_RUN"
QUERY SERVER complete
Enter acs commands (? returns help information)
4.2 ROBTEST SYNTAX

?

To exit the utility, type q or Q.

cancel <request_id> - Cancel server
defpool <pool> <lwm> <hwm> <attrib> - Define scratc
delpool <pool> - Delete empty
dm <vol> [<drive>|<drive_id>] [f] - Dismount volu
(optionally forced)
drstat <drive_id> - Print drive s
eject <cap_id> <vol_list> - Eject a list
the specified CAP
enter <cap_id> - Enter volumes
specified CAP
capstat [<cap_id>] - Print CAP sta
varycap <cap_id> online|offline - set the state
CAP
setmode <cap_id> automatic|manual - set the mode
CAP
setpriority <cap_id> <priority> - set the prior
given CAP
m <vol> [<drive>|<drive_id>] - Mount volume
qmmi - Query actual
information
qpool [<pool>] - Query pools
qreq [<request_id>] - Query server
qscr [<pool>] - Query scratch
pool
qserver - Query ACSLS s
qvol [<vol>] - Query volumes
setscr <pool> ON|OFF <vol> [<vol>] - Set scratch a
volume range
start - Start ACS Lib
(request RUN state)
types - Print list of
media types
SCSI commands:
unload <drive>|<drive_id> - Issue SCSI un
where:
<acs>=0-126, <lsm>=0-23, <cap>=0-2, <drive>=0-15, <p
<drive_id> = [<acs>,<lsm>,<panel>,<drive>]
<drive> = d1 if drive 1, d2 if drive 2, ..., d15 if
<lwm> = scratch pool low water mark
<hwm> = scratch pool high water mark

<cap_id> = <acs>,<lsm>,<cap>
<vol_list> = <vol1>[:<vol2>:...:<vol42>]
4.2.1 Command to Obtain Drive Status
drstat
Drive 1 information:
ID (acs,lsm,panel,drv): 0,0,0,0
drive type: DLT7000
volume ID: <none>
state: STATE_ONLINE
status: STATUS_DRIVE_AVAILABLE
drive type: DLT7000
volume ID: <none>
state: STATE_ONLINE
drive type: 9840
volume ID: <none>
state: STATE_ONLINE
drive type: 9840
volume ID: <none>
state: STATE_ONLINE
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

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 USIN
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
SET SCRATCH complete
qpool 4
Pool ID 4 has 5 volumes
QUERY POOL complete
Quit 'robtest' and perform a normal robot inventory with NetBackup.

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 repo
for ACS libraries. This is not a bug. The information on slot location is managed
Media Manager.
Below is a sample output from the available_media report, which can be gene
following command:
Windows: <install_path>\netbackup\bin\goodies\availabl
or
UNIX: /usr/openv/netbackup/bin/goodies/available_medi
media media robot robot robot side/ ret s

ID type type # slot face level K
----------------------------------------------------
-----------------------------
NetBackup pool
NB0001 DLT ACS 0 - - 0
NB0002 DLT ACS 0 - - 0
ABC234 DLT ACS 0 - - -
AVAILABLE
ABC345 DLT ACS 0 - - -
AVAILABLE
5.2 HOW TO SPECIFY WHICH MEDIA ACCESS PORT (MAP) TO USE FOR
In the media server's /usr/openv/volmgr/vm.conf file, it is possible to specify t

(MAP) to use when ejecting media to a particular ACS robot. If this entry is pres
(including the Vault extension) will eject to the specified MAP instead of the def
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 AC
via its 0,1,0 MAP, the following vm.conf entries would be necessary on the me
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 servi
program numbers into universal addresses. It must be running on the host to b

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 startup s
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. Se
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 RPC
between the media server and ACSLS Library Server. From a terminal window
issue the following command to ACSLS.
# rpcinfo
program version netid address servic
100000 4 ticots hotdog.rpc rpcbind
100000 3 ticots hotdog.rpc rpcbind
100000 4 ticotsord hotdog.rpc rpcbind
100000 3 ticotsord hotdog.rpc rpcbind
100000 4 ticlts hotdog.rpc rpcbind
100000 3 ticlts hotdog.rpc rpcbind
100000 4 tcp 0.0.0.0.0.111 rpcbind
100000 3 tcp 0.0.0.0.0.111 rpcbind
100000 2 tcp 0.0.0.0.0.111 rpcbind
100000 4 udp 0.0.0.0.0.111 rpcbind
100000 3 udp 0.0.0.0.0.111 rpcbind
100000 2 udp 0.0.0.0.0.111 rpcbind
If the service is not running, rpcinfo will report: "can't contact rpcbind: RPC: rpc
Failed ( unspecified error )"
Examine the /export/home/ACSSS/log/acsss_event.log for "RPC: Rpcbind fa
message should include an IP that it is trying to communicate with. Verify it is t
6.1.3 How to Verify the ACSSS Program Registration

#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 response
you are using
(2 = UDP or 3 = TCP). The NetBackup default for this communications service
6.1.4 Basic snoop Output
Basic snoop of a query server sent automatically by initiating the robtest utility:
# snoop salid carter

1 0.00000 salad -> carter.min.veritas.com P
GETPORT prog=300031 (?) vers=1 proto=UDP
2 0.00108 carter.min.veritas.com -> salad P
GETPORT port=1025
3 0.00056 salad -> carter.min.veritas.com R
XID=1066379121 PROG=300031 (?) VERS=1 PROC=1000
4 0.00091 carter.min.veritas.com -> salad R
XID=1066379121 Success
XID=1066114434 PROG=1073741824 (transient) VERS=1 PR
XID=1065841469 PROG=1073741824 (transient) VERS=1 PR
This trace shows that the portmapper and program registration was successful
For additional assistance with NetBackup options as they pertain to ACSLS, re

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 INITIAL
Resolution: Verify the IP address specified for the robotic host is correct in Lib
server.
7.2 ACS STATUS = 54, STATUS_IPC_FAILURE
Robtest will show:

acs_query_server() failed
Unable to query server taco, ACS status = 54, STATUS
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
Media Server event.log will log:
02-05-04 13:49:18 SSI[0]:
ONC RPC: csi_rpccall(): status:STATUS_NI_FAILURE; fa
clntudp_create()
RPC UDP client connection failed, RPC: Rpcbind failu
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) Response
returned by Mount command sequence 4434, ACS status
STATUS_PENDING
Nov 15 11:28:06 hoehpt07 acsd[8807]: ACS(0) Response
returned by Mount command sequence 4434, ACS status
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, N
timeout Errno = 0 (none) Remote Internet address: 20
Port: 53429
2003-05-22 11:33:51 CSI[0]:
1026 N csi_freeqmem.c 1 142

ONC RPC: csi_freeqmem(): status:STATUS_QUEUE_FAILURE

Dropping from Queue: Remote Internet address:
207.169.154.59,Port: 53429 , ssi_identifier: 1, Prot
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 server w
but the ACSLS server is unable to respond.
By default, the IP address sent to the ACSLS as part of the packet STATUS re
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) to
secondary interface on the media server.
If the issue is failure to do reserve name lookup, add the media server's IP to th
service (DNS) reverse tables or to the ACSLS /etc/hosts file.
If the ACSLS server cannot route to the media server's hostname, override the
using "ACS_SSI_HOSTNAME = <hostname>" in the /usr/openv/volmgr/vm.c
value for <hostname> is a hostname associated with an IP address the ACSLS
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 (ACS
actual "Waiting to obtain XXXXX ACS sequence YYY acknowledge response"
daemon has not received an acknowledgment from the LibraryStation module f
is a hard-coded limit) following a sent command. "Unable to obtain" means it ha
The timeouts seen occur after a 30 second delay, when no acknowledgment ha
These timeout periods are determined by two tunable environment variables:
CSI_RETRY_TIMEOUT - The default for which is 3 seconds, not 2 as describe

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 serve

CSI_RETRY_TIMEOUT=30
CSI_RETRY_TRIES=10
or
Change the OS environment variable CSI_RETRY_TIMEOUT to 30 and CSI_R

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.

Isolating the problem:

a. Ensure that the media server can successfully ping the ACS server and vice
b. Check that ltid has started the acsd, acsssi and assel service daemons on
server by performing a bpps -a from /usr/openv/netbackup/bin or vmps
from /usr/openv/volmgr/bin/volmgr. If acsssi is not running, ensure that RPC
c. Run snoop between the media server and ACS. Initiate robtest and check th
sent upon robtest initialization, is responded to by the ACSLS server (referenc
d. Verify the RPC communications between the media server and ACSLS host
command. The rpcinfo -t <acs_host> 300031 1 h command c
connectivity, portmapper registration and that the ACSLS program (service) is a
(reference 'How to start RPC' above).
e. Check the event logs from the media server and library server for errors (refe
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 Serve
entry for the requesting media server. This file is found on the ACSLS server in
$ACS_HOME/data/external/access_control directory and is used for granting
access. For example, entries of the users.ALL.allow consult the ACSLS admin
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
acsssi event.log:
02-05-04 13:31:54 SSI[0]:
ONC RPC: csi_rpccall(): status:STATUS_NI_FAILURE; fa
clntudp_create()
RPC UDP client connection failed, RPC: Program not r
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 t
Query ACS sequence 3420 acknowledge response, ACS st
STATUS_NI_TIMEDOUT
Aug 26 17:06:57 sdhra1a acsd[5476]: DecodeDismount()
driveid 0,0,10,5, Actual status: Unable to initializ
Aug 26 17:06:57 sdhra1a acsd[5476]: ACS(0) going to

status: Unable to initialize robot

Aug 26 17:07:15 sdhra1a acsd[15910]: ACS(0) Waiting
Query Drive sequence 3381 acknowledge response, ACS
STATUS_PENDING
Cause: The CSI (media server) has timed out waiting for a response from a cl
·¢±íÓÚ£º 2006-12-03£¬ÐÞ¸ÄÓÚ£º 2006-12-03 13:09£¬ÒÑä¯ÀÀ2069´Î£¬ÓÐÆÀÂ
ÍøÓÑÆÀÂÛ
¡¡·¢±íÆÀÂÛ
ÓÃ»§Ãû£º ÃÜÂë£º Ãâ·Ñ×¢²á
ÑéÖ¤Âë£º ¡¡ g
c ÄäÃû
d
e
f
Ìá½»

STK ACSLS and Veritas NetBackup Media Server

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

STK ACSLS and Veritas NetBackup Media Server

Hochgeladen von

Copyright:

Verfügbare Formate

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

²©¿ÍÊ×Ò³ ×¢²á ½¨ÒéÓë½»Á÷ ÅÅÐÐ°ñ ¼ÓÈëÓÑÇéÁ´½Ó ÍÆ¼ö Í¶Ëß ËÑË

Ê×Ò³ ÎÄÕÂ µ¼ÈëÎÄÕÂ Ïà²á ÒôÀÖ ²©¿ÍÈ¦ ÊÕ²Ø¼Ð ÁôÑÔ ·¢ ¹ÜÀí²©¿Í

file://H:\study\netbackup\Upload_site_done\done\New Folder\STK ACSLS and Veritas NetBackup media s... 7/6/2010

1.1 LOG LOCATIONS

1.1.1 Event Logs

Event log location on ACS Library Server: /export/home/ACSSS/log/acsss_e

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 an

a. Ensure this directory exists:

b. Find the acsssi PID by running the command:

d. To turn off acsssi tracing:

file://H:\study\netbackup\Upload_site_done\done\New Folder\STK ACSLS and Veritas NetBackup media s... 7/6/2010

NOTE: To read the trace.log, it is necessary to use the StorageTek trace_dec

1.2.2 ACSSS Tracing on the Library Server

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

Once enabled, an acsssi_trace.log will be created in the /export/home/ACSS

2. ACS LIBRARY SERVER (ACSLS) FUNCTIONS AND COMMANDS

2.1 ACCESS CONTROL ON THE ACS LIBRARY SERVER (ACSLS)

file://H:\study\netbackup\Upload_site_done\done\New Folder\STK ACSLS and Veritas NetBackup media s... 7/6/2010

Volume access control applies to the following commands:

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)

file://H:\study\netbackup\Upload_site_done\done\New Folder\STK ACSLS and Veritas NetBackup media s... 7/6/2010

2.2.7 Command to Start Request Processing

2.2.8 Vary on LSM

file://H:\study\netbackup\Upload_site_done\done\New Folder\STK ACSLS and Veritas NetBackup media s... 7/6/2010

2.2.9 Logoff from ACSSA (ACSLS Server interface)

2.3 ACSLS TAPE CLEANING

To disable TapeAlert checking and eliminate "TapeAlert is not supported" mess

This option is enabled or disabled using the acsss_config configuration utility.

3. DEVICE CONFIGURATION FOR ACSLS CONTROLLED TAPE DRIVES

3.1 DEVICE CONFIGURATION

NOTE: All Automated Cartridge System (ACS) robots configured on a media se

3.1.1 SSO Device Configuration for ACSLS

file://H:\study\netbackup\Upload_site_done\done\New Folder\STK ACSLS and Veritas NetBackup media s... 7/6/2010

manual configuration is required. The manual configuration cannot be avoided

3.1.2 Non-SSO Device Configuration for ACSLS

3.1.3 Initial configuration of StorageTek T9940A and T9940B tape drives i

file://H:\study\netbackup\Upload_site_done\done\New Folder\STK ACSLS and Veritas NetBackup media s... 7/6/2010

Steps to inventory media for each density type:

4 ROBTEST FOR ACS LIBRARIES

4.1 INVOKING ROBTEST

ACS(0) ACSLS host = taco

4.2 ROBTEST SYNTAX

file://H:\study\netbackup\Upload_site_done\done\New Folder\STK ACSLS and Veritas NetBackup media s... 7/6/2010

To exit the utility, type q or Q.

file://H:\study\netbackup\Upload_site_done\done\New Folder\STK ACSLS and Veritas NetBackup media s... 7/6/2010

4.2.2 Command to Query Volumes

4.2.3 Command to Mount a Volume

file://H:\study\netbackup\Upload_site_done\done\New Folder\STK ACSLS and Veritas NetBackup media s... 7/6/2010

4.2.4 Command to Dismount a Volume

Start the robtest utility:

NOTE: DEFINE POOL completes robot inventories for ACS,

Next, define ACSLS scratch volumes in this pool:

file://H:\study\netbackup\Upload_site_done\done\New Folder\STK ACSLS and Veritas NetBackup media s... 7/6/2010

5.1 AVAILABLE MEDIA SCRIPT

media media robot robot robot side/ ret s

In the media server's /usr/openv/volmgr/vm.conf file, it is possible to specify t

The vm.conf entry syntax: