Virtual TapeServer 8.2 Configuration Guide
Table Of Contents
- Virtual TapeServer for NonStop Servers Configuration Guide
- Preface
- Introduction
- Overview of Tasks
- Reconfiguring Vaults
- Enabling Licensed Features
- Configuring Ports
- Creating and Managing VTLs and VTDs
- Enabling and Performing Tape-to-tape Exports
- Enabling and Performing Stacked Exports
- Enabling and Configuring Data Replication
- Enabling and Configuring Role Swapping
- Configuring EMS Communication
- Enabling and Configuring Data Encryption
- Creating and Managing Virtual Media
- Enabling and Configuring Scan/Cleanup
- Configuring User Accounts
- Configuring Web Interface Preferences
- Managing the VTS Server
- Troubleshooting
- Maintaining GFS for VTS
- Reinstalling and Restoring VTS
- Attaching External Devices after Initial Deployment
- TCP/IP Ports and Protocols
- Index

152 | Troubleshooting
EMS messages
The following table lists the messages that are generated by VTS if EMS is enabled and
configured. Here is an explanation of the information for each EMS message:
• The message text.
Some of the text in the messages and errors is parameterized, as indicated by the dollar
sign ($). In a real message, the parameterized text is replaced by a real value. For
example, the host system that initiated the request is represented in the message text as
$host, but an actual message displays the real hostname, such as DEV2.
• The severity of the message. The levels of severity include the following:
• Informational (Inform) — A normal operation has occurred.
• Warning — A suspicious operation, configuration, or user error has occurred. The
system or application can handle the error with no interruption and limited
degradation of service.
• Critical — A system or service error has occurred. The system can recover but a
momentary loss or permanent degradation of service may occur.
• The recommended action to take.
Message Text Severity Recommended Action
(Error:) Non-zero return-code ($rc)
from dsmc (try this url … for
$cart_request.
Critical An IBM Tivoli Storage Manager (TSM)
failure occurred. Examine the return
error code and correct the problem.
AUTOCOPY FAILED: Request by:
$requestor ($retry_number) cannot
create directory $target (rc=$rc)
Critical No action is required. The task will be
retried.
AUTOCOPY FAILED: Request by:
$requestor ($retry_number) cannot
reach $target/$filename (rc=$rc)
Critical No action is required. The task will be
retried.
AUTOCOPY FAILED: Requested
by: $requestor ($retry_number)
from $target/$filename(rc=$rc)
Critical The autocopy task failed. Correct the
problem and resubmit the job.
AUTOCOPY STARTING: Request
by: $requestor ($retry_number) scp
from $sourcedir/$filename to
$target/$filename
Inform
AUTOCOPY SUCCESSFUL:
Requested by: $requestor
($retry_number) from $sourcedir/
$filename to $target/$filename
Inform
BEX – No files found to restore Inform