Fujitsu 2.1 9.3 Detailed Error Codes

Chapter 9 Messages

9.3 Detailed Error Codes

ETERNUS VSS Hardware Provider 2.1 User’s Guide

Copyright 2012 FUJITSU LIMITED P3AM-4582-03ENZ0

125

9.3 Detailed Error Codes

The detailed error codes output by the ETERNUS Disk storage systems are listed below.

Table 9.1 Detailed Error Codes

Detailed error code Action

Invalid logical volume name Take one of the following actions:

•Check that the specified copy source or destination device

exists.

•Check that the user privilege with which the operation is

performed is correct.

•Check that the disk is initialized.

invalid source OLU. Check the partition information for the copy source device.

invalid destination OLU. Check the partition information for the copy destination

device.

invalid extent. Check the slice information on the copy source or destination

device.

memory allocation error. Allocate sufficient memory or a swap area, or terminate any

other programs that are being executed.

not STX. The disk is not ETERNUS Disk storage systems disk.

SCSI command busy. Take the applicable action as follows:

•Ensure that the OPC/EC copy source is not used for

another copy target.

•Ensure that the OPC/EC copy target is not used for

another copy source.

•Ensure that the OPC/EC copy target is not used for

another copy target.

•Wait for about five seconds and then re-execute

processing.

•Confirm the status of the copy by using ETERNUS Web

GUI.

For other cases, contact a Fujitsu customer engineer.

SCSI command conflict. SCSI error (Commandconflict) was detected.

Check the device connection status and then retry. If the error

recurs, contact your Fujitsu customer engineer (CE).

SCSI queue full. SCSI error (Queuefull) was detected.

Check the device connection status and then retry. If the error

recurs, contact your Fujitsu customer engineer (CE).

hardware error requiring CE-CALL. SCSI error (CheckCondition) was detected.

Check the device connection status and then retry. If the error

recurs, contact your Fujitsu customer engineer (CE).

SCSI condition met. SCSI error (Condition met) was detected.

Check the device connection status and then retry. If the error

recurs, contact your Fujitsu customer engineer (CE).

unexpected SCSI error. SCSI error (Abnormal status) was detected.

Check the device connection status and then retry. If the error

recurs, contact your Fujitsu customer engineer (CE).

Contents

Main Page Preface Intended Audience The Structure of this Manual Page Naming Conventions Notes when deleting the server graphic shell on Windows Server 2012 Acknowledgments Release Information ETERNUS VSS Hardware Provider Modification History Page ETERNUS VSS Hardware Provider Updates Page Page Table of Contents Chapter 1 ETERNUS VSS Hardware Provider 14 Chapter 2 Workflow 27 Chapter 3 Preparation 28 Chapter 4 Environment Creation 34 Chapter 5 Operation 44 Chapter 6 Operation Change 45 Chapter 7 Operation End 50 Chapter 8 Commands 52 Page Chapter 1 ETERNUS VSS Hardware Provider 1.1 Overview 1.2 Functions Cooperation with Advanced Copy functions Management methods and operation modes for Shadow Copy destination volumes with VSSHP Target disk pool operation Copy set operation 1.3 Operational Procedure 1.3.1 Server Configuration 1.3.1.1 Local Copy Configuration 1.3.1.2 Transportable Copy Configuration Copyright 2012 FUJITSU LIMITED P3AM-4582-03ENZ0 -Example of n:1 case 1.3.1.3 Local Copy Configuration (when Backing Up a Hyper-V Virtual Machine) 1.3.1.4 Transportable Copy Configuration (when Backing Up a Hyper-V Virtual Machine) -Example of n:1 case 1.3.2 Disk Conditions 1.3.3 Volume Management Methods and Management Files 1.4 Supported Environment 1.4.1 Possible VSSHP Version Combinations for Production Servers and Backup Servers 1.4.3 Notes on Using VSSHP on Windows Server 2012 1.4.3.1 Combined Use of VSSHP and Offloaded Data Transfer (ODX) 1.4.3.2 Use of Virtual Disks with the Storage Pool Function 1.5 Required Resources This section describes the resources required for backup operation using VSSHP. 1.5.1 Required Disk Capacity for Installation 1.5.2 Required Disk Capacity for Operation Chapter 2 Workflow Perform preparation, install VSSHP, and setup the environment according to the following workflow. Chapter 3 Preparation 3.1 Advanced Copy License Registration Source disk Source disk 3.2 Shadow Copy Destination Disk Creation Example 1 Page Example 4 3.2.1 Selection of the Shadow Copy Destination Disk Type 3.2.2 Shadow Copy Destination Disk Capacity Estimation 2 3 Command". 4 3.2.3 Volume Creation Chapter 4 Environment Creation 4.1 New Installation Page 3 4 5 management file appears. 6 installation. 4.1.1.2 Production Server 2 Page Page 3 4 5 6 installation. 4.2 Upgrade Installation 2 3 Chapter 5 Operation Chapter 6 Operation Change 6.1 When Changing the Shadow Copy Destination Displaying the Target Disk Pool Registration/Deletion window Changing the Shadow Copy Destination 1 6.2 When Changing the Communication Environment Backup server Production server Chapter 7 Operation End 7.1 Copy Session Stop 7.2 VSSHP Uninstallation For Windows Server 2008/Windows Server 2012 1 7.2.1 Operations After Uninstalling Change the firewall settings (Only the backup server) Chapter 8 Commands This chapter explains how to use each command. 8.1 Provider Registration/Deletion Command (stxvprovider) Reference 8.2 Update Volume Measurement Command (stxvtestcopy) Page 8.3 Backup Control Command (stxvcopy) Page 8.4 Batch Stop Command (stxvstopall) 8.5 Backup Status Query Command (stxvquery) This command displays the Advanced Copy status. Execute this command on a backup server. 8.6 OLU Number Display Command (stxvgetolu) Device information that is not registered in a definition file is also output. Reference 8.7 Communication Environment Check Command (stxvchkcommu) Page Page Page Page 8.9 Target Disk Pool Registration/Deletion Command (stxvsetdiskpool) Description of subcommands The input format of the "add" subcommand and "delete" subcommand Page 8.10 Hyper-V Environment Setup Command (stxvhyperv) Page 8.11 Shadow Copy Destination Recovery Command (stxvrecoverydisk) Page Chapter 9 Messages 9.1 Event Log Messages Event ID: 501 Event ID: 502 Event ID: 503 Event ID: 504 Event ID: 505 Event ID: 513 Event ID: 514 Event ID: 515 Event ID: 516 Event ID: 517 Event ID: 518 Event ID: 520 Event ID: 551 Event ID: 552 Event ID: 560 Event ID: 561 Event ID: 565 Event ID: 570 Event ID: 571 Event ID: 572 Event ID: 573 Event ID: 574 Event ID: 575 Event ID 576 Event ID 577 Event ID: 578 Event ID: 579 Event ID: 580 Event ID: 581 Event ID: 583 Event ID: 585 Event ID: 591 Event ID: 592 Event ID: 593 Event ID: 594 Event ID: 595 Event ID: 596 Event ID: 1001 Event ID: 1002 Event ID: 1003 Event ID: 1004 Event ID: 1005 Event ID: 1006 Event ID: 1007 Event ID: 1008 Event ID: 1009 Event ID: 1010 Event ID: 1011 Event ID: 1012 Event ID: 1013 Event ID: 1101 Event ID: 1102 Event ID: 1201 Event ID: 1202 Event ID: 1203 Event ID: 1204 Event ID: 1205 Event ID: 1206 Event ID: 1207 Event ID: 2001 Event ID: 2002 Event ID: 2003 Event ID: 2004 Event ID: 2005 Event ID: 2006 Event ID: 2007 Event ID: 2008 Event ID: 2102 Event ID: 2103 Event ID: 2104 Event ID: 2105 9.2 Command Messages STXV0001 ERROR Failed to register hardware provider. STXV0002 WARNING Hardware provider already registered. STXV0003 ERROR Failed to delete hardware provider. STXV0004 WARNING Hardware provider already deleted. STXV0005 ERROR Invalid number of parameters. STXV0006 ERROR Invalid parameter. Parameter="Parameter" STXV0101 ERROR Invalid number of parameters. STXV0102 ERROR Invalid parameter. Parameter = "Parameter" STXV0103 ERROR Pseudo SnapOPC already started. Page STXV0202 ERROR Invalid parameter. Parameter = "Parameter" STXV0203 ERROR Copy set file does not exist. STXV0204 ERROR Failed to access copy set file. STXV0205 ERROR Line["line number"] Invalid number of items. STXV0206 ERROR Line["line number"] Invalid copy type. Page STXV0213 ERROR Line["line number"] Target disk is the same as the source disk. STXV0214 ERROR Line["line number"] Size of the source disk differs from target disk. STXV0217 ERROR Line["line number"] Duplicated source disk setting. STXV0218 ERROR Line["line number"] Duplicated target disk setting. Page STXV0224 ERROR Failed to access copy set information. STXV0225 ERROR Invalid copy set information. STXV0226 ERROR Failed to register copy set information. STXV0227 INFO Number of errors: ["number of errors"] STXV0228 INFO Number of warnings: ["number of errors"] Page Page Page Page STXV0302 ERROR Invalid parameter. Parameter = "Parameter" STXV0303 ERROR Management file cannot be found. STXV0304 ERROR Failed to access copy set information. STXV0305 ERROR Invalid copy set information. STXV0306 ERROR Source disk number cannot be found in Management file. Page Page Page Page STXV0403 ERROR Management file cannot be found. STXV0404 ERROR Failed to access copy set information. STXV0405 ERROR Invalid copy set information. Page Page Page STXV0604 WARNING Failed to access device. 1 [Computer Management] to start. 2 STXV0605 ERROR Internal inconsistency. STXV0701 ERROR Invalid number of parameters. STXV0703 ERROR Management file cannot be found. STXV0704 ERROR Failed to access copy set information. STXV0705 ERROR Invalid copy set information. STXV0706 ERROR Source disk number cannot be found in Management file. Page Page STXV0803 ERROR Failed to access to services file("event ID") STXV0804 ERROR No port number is able to use. STXV0805 ERROR Access error in VSSHP environment file. Internal code = "internal code" STXV0902 ERROR Failed to access device. Error code = "internal error code","detailed error code" STXV0903 WARNING the back-up disk Pool control file was updated. These changes will be discarded. STXV3001 ERROR Invalid number of parameters. STXV3002 ERROR Invalid parameter. Parameter = "Parameter" STXV3003 ERROR Internal inconsistency. STXV3004 ERROR Failed to create a VSSHP Hyper-V environment STXV3005 ERROR Failed to delete a VSSHP Hyper-V environment STXV3006 ERROR Not a Server Core environment STXV3007 ERROR Insufficient memory. STXV3008 ERROR Failed to obtain device information. STXV3009 ERROR Failed to access the target disk pool management file. STXV3010 ERROR Failed to obtain device information. Error = "error number","detailed error code" STXV3011 ERROR Failed to update the target disk pool management file. STXV3012 ERROR The specified session does not exist. Page Page 9.3 Detailed Error Codes Page 9.4 Output Error Messages in Message Box Installation Provider registration Backup server settings for Transportable Copy Configuration Production server settings for Transportable Copy Configuration Chapter 10 Troubleshooting 10.1 How to Deal with Errors/Warnings This section explains how to deal with errors/warnings. 10.2 How to Obtain Error Information Obtaining information with the Error Information Acquisition function 1 2 3 1 2 3 4 (Comma delimited)(*.csv)], and save it. OS information