FUJITSU VSS Hardware Provider 2.1 User Manual
Page 78
Chapter 9 Messages
9.1 Event Log Messages
ETERNUS VSS Hardware Provider 2.1 User’s Guide
Copyright 2012 FUJITSU LIMITED
P3AM-4582-03ENZ0
78
■
Event ID: 517
Type:Information
Messages:STXV0517 INFO Management file cannot be found. Internal code = "internal code"
Details:
The copy set management file cannot be found.
When performing backup using VSSHP, perform either of the following.
-
Register the Shadow Copy destination information in the target disk pool management file.
-
Register the copy set information in the copy set management file.
•
When "internal error code" is 3
Set the VSSHP communication environment.
To start the Communication Environment Setup function, click the [Start] button – [All
Programs] – [ETERNUS VSS Hardware Provider] – [Communication Environment Setup].
•
For a Server Core environment
Execute the "Communication Environment Setup Command".
For details, refer to
"8.8 Communication Environment Setup Command (stxvsetcommu)"
■
Event ID: 518
Type:Error
Messages:STXV0518 ERROR Target disk not found. Error code = "internal error code"
Details:
The Shadow Copy destination is not sufficient in the target disk pool management file.
The process is canceled.
Register a Shadow Copy destination that has the same size as those of the source disk in the target
disk pool management file.
-
When "internal error code" is 1
The server configuration in the requester uses the same Windows PC for both the production
server and backup server.
-
When "internal error code" is 2
The server configuration in the requester uses a different Windows PC for the production server
and backup server.
There is also a possibility that the Shadow Copy destination disk cannot be checked via [Disk
Management] since the backup ended abnormally. Use the "Shadow Copy Destination Recovery
Command" to make the Shadow Copy destination disk checkable via [Disk Management]. For
details, refer to
"8.11 Shadow Copy Destination Recovery Command (stxvrecoverydisk)" (page 73)
.
Review the server configuration setting, and try again.