|
Product: StorageExpress™ Backup Server
E7001, E7002, E7003, E7004, E7005, E7006, E7007, E7008, E7009, E7010,
E7011, E7012, E7013, E7014, E7015, E7016, E7018, E7019, E7020,
E7001 - Bad NLM Registrations Signature was passed
E7003 - Bad Group Signature was passed
Problem
The STANDARD.NLM file may have become corrupted.
Resolution
Unload and reload ARCserve by typing ASTOP and ASTART at the file
server console. If the problem persists, replace the STANDARD.NLM
file located in the \ARCSERVE\NLM subdirectory with a new copy from
the ARCserve install disks (using the Microsoft EXPAND) utility.
E7002 - Maximum number of registered NLMs reached
E7004 - Maximum number of defined Tape Groups reached
Problem
The maximum number (7) of copies of STANDARD.NLM has been reached.
Resolution
Make sure that no more than seven devices are present on the SCSI
bus and in the ARCserve configuration files. See also TAPESVR.CFG
Parameters.
E7005 - Group Name [group name] is already in use
Problem
An attempt has been made to load a tape group using a name that
already exists.
Resolution
Change the name of the tape group to one that is not in use or add
the device to the group that already exists.
See TAPESVR.CFG Parameters.
E7006 - SCSI ID(s) [id number(s)] is already in use
Problem
The SCSI IDs specified have already been used by an earlier step in
the Tape Server configuration process. A single SCSI ID can only
be loaded into one group at any one time.
Resolution
Make sure that each device on the SCSI bus has been assigned a
unique ID and that the TAPESVR.CFG file accurately reflects the
hardware configuration.
E7007 - Error Occurred [error number]
E7008 - Failed To Register Tape Group Information, [group name] will
unload
Problem
When an ASTART command is issued at the file server console, the
following error messages are generated on the system console:
E7007: Error Occurred
E7008: Failed To Register Tape Group Information, [group
name] Will Unload
Also, the ARCserve Tape Manager screen will report a Device
Initialization Failure error message. This is due to ARCserve's
tape drive interface, TAPESVR.NLM having been unable to find any
tape devices.
Resolution
Make sure that the tape device is not set to SCSI ID 7. Since
most SCSI cards are set to ID 7, TAPESVR.NLM will not scan this
address for tape devices.
Recheck the SCSI and power cables to ensure that a proper
connection is present. In most cases, if the connectivity between
the tape drive and the SCSI card is correct, the device information
will be displayed during the cold boot sequence of the computer.
Check to see if termination is properly installed on the SCSI bus.
The owners guide for the SCSI card will offer additional
information, but for most cards the first and last devices on the
SCSI bus should be the only devices with terminators installed.
Change the SCSI ID of the tape device. Some SCSI cards reserve the
lower IDs (0,1) for hard drives.
If both tape drive(s) and hard disk(s) or other devices are on the
same adapter card, be sure that the multi-protocol interface (eg:
ASPI) is initialized and that ARCserve is properly configured (see
Multi-Protocol Driver Matrix for a list of common SCSI cards and
the drivers they require). If the correct adapter drivers have
already been loaded, be sure that the proper host number has been
selected on the load line of the ARCserve driver in the ASTART.NCF.
If the adapter card is dedicated to the tape drive, make sure that
the proper Cheyenne driver is loaded (see Dedicated Board Driver
Matrix for a list of common SCSI cards and the drivers they
require).
Some SCSI cards and/or tape drives do not support the scanning of
Logical Unit Numbers (LUNs). Since some devices, such as changers,
utilize LUNs, ARCserve.s TAPESVR.NLM will scan these IDs. If the
installation is running a changer that utilizes Logical Unit
Numbers, the scanning of the LUNs may be disabled by adding the
following lines to the TAPESVR.CFG file, found in the \ARCSERVE\NLM
directory on the ARCserve host server:
[CONFIG]
NOLUN=ENABLE
This feature is also supported as a command line argument on the
ASPI50.NLM load line (found in ASTART.NCF). For example:
LOAD SYS:ARCSERVE\NLM\ASPI50 HOST=0 NOLUN
When using an ASPI interface, TAPESVR.NLM will scan all available
host numbers looking for tape devices. Sometimes, the scanning of
the different host numbers will not recognize the tape device as
such. To disable the scanning of the other host numbers, add the
following lines to the TAPESVR.CFG file, found in the \ARCSERVE\NLM
directory on the ARCserve host server:
[CONFIG]
NOSCAN=ENABLE
This feature is also supported as a command line argument on the
ASPI50.NLM load line (found in ASTART.NCF). For example:
LOAD SYS:ARCSERVE\NLM\ASPI50 HOST=0 NOSCAN
Note: Both the NOSCAN and NOLUN parameters are only supported in
ARCserve versions 5.01d and later.
See also TAPESVR.CFG Parameters
E7009 - Tape Drive(s) cannot be found at the given SCSI IDs [idnumber]
Problem
When an ASTART command is issued at the file server console, the
following error message is generated:
E7009: Tape Drive(s) cannot be found at the given SCSI IDs [id
number]
This usually occurs if there is more than one tape drive on the
same SCSI bus, and STANDARD.NLM or CHANGER5.NLM could not find the
assigned SCSI tape drives.
Resolution
First, check the SCSI IDs of the tape drives to make sure that they
are unique. Then, make sure that the TAPESVR.CFG file is
configured correctly. (The TAPESVR.CFG file can be found within
the ARCserve home directory under the NLM subdirectory, ie:
SYS:\ARCSERVE\NLM\TAPESVR.CFG.)
Following are two examples of how Tape Group Information may be
configured within the TAPESVR.CFG file:
Example 1.
There are 2 tape drives, one at SCSI ID 3 and the other at SCSI ID
5. This configuration will support data cascading. Data cascading
(or tape spanning) means that ARCserve will send data to the second
tape drive once the tape in the first drive is full. Type the
following to configure both tape drives to be in the same Tape
Group, called ARCSERVE:
[NLM]
NLM1 = Standard Group-ARCSERVE SCSIID-35;(1st load)
Important: There are no commas, spaces, or hyphens between the ID
numbers and both tape devices must be of the identical make and
model!
Example 2.
There are 2 tape drives, one at SCSI ID 3 and the other at SCSI ID
5. This configuration will support parallel streaming. Parallel
streaming allows ARCserve to run two tape operations
(backup/restore) concurrently. Type the following to configure the
tape drives into two separate Tape Groups, naming them ARC1 and
ARC2, respectively:
[NLM]
NLM1 = Standard Group-ARC1 SCSIID-3;(1st load)
NLM2 = Standard Group-ARC2 SCSIID-5;(2nd load)
See also TAPESVR.CFG Parameters
E7010 - Only tape drives of the same type can be grouped together
Problem
An attempt has been made to put tape drives of different types into
the same group. All drives in a group must be of the same make and
model.
Resolution
If the tape drives are of different types, then they will have to
be configures into separate groups.
E7011 - A Non-Tape Device was included in the SCSI ID Group List
Problem
An attempt has been made to include a SCSI device other than a tape
drive into an ARCserve group.
Resolution
Make sure that the correct SCSI IDs have been specified in the
TAPESVR.CFG file.
E7012 - Illegal characters detected in Group Name
Problem
A group name has been specified that contains illegal characters or
is of an illegal length.
Resolution
ARCserve group names can only be up to 8 alphanumeric (and other
printable) characters in length. Spaces cannot be used.
E7013 - No Group Name Assigned to [standard/changer/stacker]
Problem
A tape device on the SCSI bus has not been configured as part of an
ARCserve group.
Resolution
Tape devices must be part of a group for them to be recognized by
ARCserve. Modify the TAPESVR.CFG file to include all tape devices
in properly defined groups.
E7014 - Illegal Command Line Parameter [contents of unrecognized command
line parameter] was given
Problem
An improperly specified command line parameter was specified during
the loading of TAPESVR.NLM
Resolution
Check for the proper syntax of the parameter specified in the error
message. See TAPESVR.NLM Command Line Parameters.
E7015 - Illegal characters detected in SCSIID parameter
E7016 - Given SCSI ID [id number] is out of range, Legal Range 0 to 6
Problem
A illegal SCSI ID has been specified.
Resolution
A SCSI ID can only be a numberal from 0 to 6. Modify the
TAPESVR.CFG file so that only valid numbers are specified as SCSI
IDs.
E7018 - Illegal characters [characters] in BUFFER parameter
E7019 - [Buffer size] is not a legal buffer size value
Problem
An illegal value has been entered for the BUFFERS parameter.
Resolution
Select only a BUFFER size lower than 32. The default is 6.
E7020 - Bad delimiter was detected on command line
Problem
Improper syntax was detected during the loading of TAPESVR.NLM.
For example, STANDARD.NLM didn't detect a "-" or "=" on the command
line.
Resolution
Check the syntax of the TAPESVR.CFG file for use of the proper
delimiters.
This applies to:
|
