Chapter 23 Messages of Vmlink Prefix

vmlink00001

Internal error occurred.

Explanation

An internal error has occurred.

System Response

The system terminates processing.

System Administrator Corrective Action

Collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink00003

Two or more operations were executed at the same time for the virtual machine or ETERNUS Disk storage system.
Server name : serverName
Storage device name : storageName

Explanation

Multiple operations were simultaneously executed for the virtual machine or the ETERNUS Disk storage system.

Parameters

serverName : Name of the virtual machine in which the operation failed
storageName : Name of the ETERNUS Disk storage system in which the operation failed

System Response

The system terminates processing.

System Administrator Corrective Action

For the virtual machine that is displayed in serverName or the ETERNUS Disk storage system that is displayed in storageName from the ETERNUS SF system, multiple operations may have been executed simultaneously.

In the Operation History screen of Web Console, check whether any processes are running for the virtual machine that is displayed in serverName or the ETERNUS Disk storage system that is displayed in storageName.
If a running process exists, after that the process is completed, re-execute the operation.

If you still have a problem, collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink00004

The information on operational object was not found.
Error code : errCode

Explanation

The information of the operation target did not exist.

Parameters

errCode : Error number

System Response

The system terminates processing.

System Administrator Corrective Action

In the Operation History screen of Web Console, check whether the operations for the target resource are conflicted and take appropriate action according to the error number that is displayed in errCode. If you still have a problem or if the error number that does not exist in the following table is displayed, collect the information required for troubleshooting and contact Fujitsu Technical Support.

Value of errCode	Action Plan
1	After re-registering the ETERNUS Disk storage system, re-execute the operation.
2	If this error occurred during the Snapshot restore, Clone restore, or Single item restore operation Re-execute the operation. If this error occurred during an operation other than those above After re-registering the virtual machine, re-execute the operation.
3	Check whether the VM host where virtual machines run is registered. If not, after re-registering the VM host, re-execute the operation. Check whether vCenter Server managing the VM host where virtual machines run is registered. If not registered, after re-registering vCenter Server, re-execute the operation. If registered, the configuration of the VMware environment may have been changed after vCenter Server was registered. After reloading vCenter Server, re-execute the operation. If both the VM host and vCenter Server are registered, performing a name resolution might not be possible for the VM host on the Management Server. Configure the DNS settings so that a name resolution can be performed for the VM host using both DNS lookup and reverse DNS lookup on the Management Server. After configuring the DNS settings so that a name resolution can be performed, reload vCenter Server, and re-execute the operation.
4	Check whether a Clone backup VVOL datastore exists. If not, after creating a Clone backup VVOL datastore, re-execute the operation.
5	The process failed because Storage vMotion was in progress for the target virtual machine. After Storage vMotion has been completed, re-execute the operation.
6	If this error occurred during the Clone backup operation The volume that is assigned to the virtual machine may have been deleted. Re-execute the operation. The device information may be synchronized between the ETERNUS Disk storage system and the ETERNUS SF system. After waiting for a while, re-execute the operation. If you still have a problem, after performing the Reload Conf. operation, re-execute the operation. If this error occurred during the Snapshot restore, Single item restore, or Snapshot backup history deletion operation The target Snapshot may have been deleted from vCenter Server. Check whether the target Snapshot exists on vCenter Server. If not, specify any existing Snapshot and re-execute the operation. The device information may be synchronized between the ETERNUS Disk storage system and the ETERNUS SF system. After waiting for a while, re-execute the operation. If you still have a problem, after performing the Reload Conf. operation, re-execute the operation.
7	The target Snapshot backup may have been deleted for other operation such as Snapshot backup or Snapshot backup history deletion. Check whether the target Snapshot exists on vCenter Server. If not, specify any existing Snapshot and re-execute the operation.
8	In the VVOL Backup Management screen of Web Console, check whether the virtual machine exists. If not, review the operation target.
9	In the VVOL Backup History screen of Web Console, check whether the Clone backup history exists. If not, Clone backup history deletion and restore from Clone backup cannot be performed. Review the executed operation.
10	The communication from the Management Server to the ETERNUS Disk storage system may have failed, or a Clone backup destination volume may be removed from the ETERNUS Disk storage system. Check the status of the ETERNUS Disk storage system and whether there is any fault in the network communication path between the Management Server and the ETERNUS Disk storage system. If an error has occurred, after removing the cause of the error, re-execute the operation. If there is no error, the Clone backup history deletion and restore from Clone backup cannot be performed because the Clone backup destination volume is deleted from the ETERNUS Disk storage system. Review the executed operation.
11	The target scheduler task was deleted. If this error occurred when executing the scheduler task to delete the temporary volume that was created by executing Single item restore From vCenter Server, check whether the temporary volume for Single item restore is assigned to the virtual machine. If so, delete the temporary volume manually. If this error occurred when executing the scheduler task to perform the virtual machine backup The virtual machine backup could not be performed because the policy was changed. To perform the auto execution of virtual machine backup, reset the Operation Mode of the virtual machine backup policy to "Auto" from vCenter Server. If this error occurred in cases other than the case of scheduler task execution No action is required.
13	The communication from the Management Server to the ETERNUS Disk storage system has failed. Check the status of the ETERNUS Disk storage system and whether there is any fault in the network communication path between the Management Server and the ETERNUS Disk storage system. If an error has occurred, after removing the cause of the error, re-execute the operation.

vmlink00007

Failed to backup because the size of Volume had been changed.
Volume name : volumeName
VMDK file name : vmdkName

Explanation

Clone backup cannot continue because the size of the volume for the Clone backup has been changed.

Parameters

volumeName : Volume name
vmdkName : VMDK file name

System Response

The system terminates processing.

System Administrator Corrective Action

With Web Console, delete the Snapshot backup history and the Clone backup history. After that, re-execute the operation.

vmlink00008

The license required to perform this function is not registered.
Storage device name : storageName

Explanation

The necessary license to execute this function has not been registered.

Parameters

storageName : Storage device name

System Response

The system terminates processing.

System Administrator Corrective Action

With Web Console, register the ETERNUS SF AdvancedCopy Manager Local Copy License for the ETERNUS Disk storage system that is displayed in storageName. After that, re-execute the operation.

vmlink00010

Failed to create the volume for Clone backup.
Command : commandLine
Content of error : detail

Explanation

Creating a volume for Clone backup failed.

Parameters

commandLine : Storage Cruiser command name
detail : Error context returned by the Storage Cruiser command

System Response

The system terminates processing.

System Administrator Corrective Action

Refer to [System Administrator Corrective Action] of the Storage Cruiser error message that is displayed in detail and take the required action. After that, re-execute the operation.

If the content of the error is not displayed in detail, check whether the service for the Storage Cruiser's manager is running. If not running, start the service for the Storage Cruiser's manager. Refer to "Starting and Stopping Manager" in the Storage Cruiser Operation Guide for information on how to check and start the service for the Storage Cruiser's manager. After that, re-execute the operation.

If you still have a problem, collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink00019

A virtual machine of the same name already exists.
Server name : serverName

Explanation

A virtual machine with the same name already exists.

Parameters

serverName : Virtual machine name

System Response

The system terminates processing.

System Administrator Corrective Action

Specify a different virtual machine name and re-execute the operation.

vmlink00020

The ETERNUS Disk storage system is not registered on ETERNUS SF AdvancedCopy Manager Copy Control Module.
Storage device name : storageName

Explanation

The ETERNUS Disk storage system that is connected to the virtual machine to be run is not registered in AdvancedCopy Manager Copy Control Module.

Parameters

storageName : Storage device name

System Response

The system terminates processing.

System Administrator Corrective Action

With Web Console, set the connection configuration of the ETERNUS Disk storage system that is displayed in storageName. Refer to "Configuration of Advanced Copy Connection Type" in the Storage Cruiser / AdvancedCopy Manager Operation Guide for VMware vSphere Virtual Volumes for information on how to set the connection configuration.

After that, re-execute the operation.

vmlink00021

There is no Clone backup VVOL datastore existing.
Storage device name : storageName

Explanation

A Clone backup VVOL datastore does not exist.

Parameters

storageName : Storage device name

System Response

The system terminates processing.

System Administrator Corrective Action

Create a Clone backup VVOL datastore for the ETERNUS Disk storage system that is displayed in storageName. After that, re-execute the operation.

vmlink00022

Operation failed because restore from Clone backup was being processed.
Copy group : copyGroup
Storage device name : storageName

Explanation

The operation failed because a restore from a Clone backup is currently in progress.

Parameters

copyGroup : Copy group name
storageName : Storage device name

System Response

The system terminates processing.

System Administrator Corrective Action

The volume in the copy group that is displayed in copyGroup may be executing a physical copy. After the physical copy is complete, re-execute the operation.

Or the repository information of the ETERNUS SF system may not be up to date. Reload the configuration for the ETERNUS Disk storage system that is displayed in storageName. After that, re-execute the operation.

vmlink00023

vCenter Server is not registered.
IP address : ipAddress

Explanation

vCenter Server is not registered.

Parameters

ipAddress : IP address of vCenter Server

System Response

The system terminates processing.

System Administrator Corrective Action

The information of vCenter Server that is displayed in ipAddress is not registered in the ETERNUS SF system. Or the information of vCenter Server that was registered in the ETERNUS Disk storage system may have been deleted or changed. In the Operation History screen of Web Console, check whether the information of vCenter Server that is displayed in ipAddress has been deleted or changed.
If the information has been deleted, after re-registering vCenter Server, re-execute the operation.
If the information has been changed, re-execute the operation.

If you still have a problem, collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink00024

A temporary volume for Single Item Restore already exists.

Explanation

A temporary volume for Single item restore already exists.

System Response

The system terminates processing.

System Administrator Corrective Action

Execute the Remove Temporary Volume task registered on the scheduler task to remove the temporary volume. Refer to "Regarding Temporary Volume for Single Item Restore Connected to Virtual Machine" in "Restoration" in the Storage Cruiser / AdvancedCopy Manager Operation Guide for VMware vSphere Virtual Volumes for details about the scheduler task that deletes a temporary volume.
After that, re-execute the operation.

If the temporary volume deletion task has been deleted before executing the temporary volume deletion task registered in the scheduler task, the temporary volume is not deleted. In this case, after manually deleting the temporary volume assigned to the virtual machine, re-execute the operation.

vmlink00032

Failed to delete the volume for Clone backup.
Command : commandLine
Content of error : detail

Explanation

Deleting the volume for Clone backup failed.

Parameters

commandLine : Command name
detail : Error context returned by the command

System Response

The system terminates processing.

System Administrator Corrective Action

Perform the following action according to the command that is displayed in commandLine.

If the command name begins with "ac"
Refer to [System Administrator Corrective Action] of the AdvancedCopy Manager Copy Control Module error message that is displayed in detail and take the required action.
If the command name begins with "storageadm"
Refer to [System Administrator Corrective Action] of the Storage Cruiser error message that is displayed in detail and take the required action.

After that, re-execute the operation.

If the command name and the contents of the error are not displayed, collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink00036

Failed to execute Clone backup.
Command : commandLine
Content of error : detail

Explanation

Executing a Clone backup failed.

Parameters

commandLine : AdvancedCopy Manager Copy Control Module command name
detail : Error context returned by the AdvancedCopy Manager Copy Control Module command

System Response

The system terminates processing.

System Administrator Corrective Action

Refer to [System Administrator Corrective Action] of the AdvancedCopy Manager Copy Control Module error message that is displayed in detail and take the required action. After that, re-execute the operation.

If the command name and the contents of the error are not displayed, collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink00037

Failed to restore from Clone backup.
Command : commandLine
Content of error : detail

Explanation

Restoration from the Clone backup failed.

Parameters

commandLine : AdvancedCopy Manager Copy Control Module command name
detail : Error context returned by the AdvancedCopy Manager Copy Control Module command

System Response

The system terminates processing.

System Administrator Corrective Action

If the command name and the contents of the error are not displayed, collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink00038

Failed to copy the temporary volume for Single Item Restore.
Command : commandLine
Content of error : detail

Explanation

Copying a temporary volume for Single item restore failed.

Parameters

commandLine : AdvancedCopy Manager Copy Control Module command name
detail : Error context returned by the AdvancedCopy Manager Copy Control Module command

System Response

The system terminates processing.

System Administrator Corrective Action

If the command name and the contents of the error are not displayed, collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink00046

Failed to obtain a list of ETERNUS Disk storage systems.
Command : commandLine
Content of error : detail

Explanation

Obtaining the list of ETERNUS Disk storage systems failed.

Parameters

commandLine : AdvancedCopy Manager Copy Control Module command name
detail : Error context returned by the AdvancedCopy Manager Copy Control Module command

System Response

The system terminates processing.

System Administrator Corrective Action

If the command name and the contents of the error are not displayed, collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink00047

No Tier pool exists for which Clone backup can be created.
Storage device name : storageName

Explanation

Tier pools where a Clone backup can be performed do not exist.

Parameters

storageName : Storage device name

System Response

The system terminates processing.

System Administrator Corrective Action

In a Clone backup VVOL datastore for the ETERNUS Disk storage system that is displayed in storageName, add a Tier pool that can secure enough capacity for performing a Clone backup. After that, re-execute the operation.

vmlink00049

Two or more operations were executed at the same time for the virtual machine.
Server name : serverName

Explanation

Multiple operations were simultaneously executed for the virtual machine.

Parameters

serverName : Virtual machine name

System Response

The system terminates processing.

System Administrator Corrective Action

For the virtual machine that is displayed in serverName from vCenter Server, multiple operations may have been executed simultaneously. Check whether any processes are running for the virtual machine that is displayed in serverName from vCenter Server.
If a running process exists, after that process is completed, re-execute the operation.

If you still have a problem, collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink00052

An unexpected error occurred during operation of vCenter Server.
Content of error : detail

Explanation

An unexpected error occurred in the operation of vCenter Server.

Parameters

detail : Error context

System Response

The system terminates processing.

System Administrator Corrective Action

From the error contents that are displayed in detail, take corrective action according to the error number that is displayed in "Error Code =".
If you still have a problem or if the error number that does not exist in the following table is displayed, collect the information required for troubleshooting and contact Fujitsu Technical Support.

Error Number	Action Plan
1, 2, 3	Check whether there are any problems in the network environment between the Management Server and vCenter Server. If there is a problem, after resolving the network abnormality, re-execute the operation. Check whether vCenter Server is running normally. If not running, after starting vCenter Server, re-execute the operation. Check whether vCenter Server is in a maintenance mode. When in a maintenance mode, after canceling maintenance mode, re-execute the operation. Check whether the vCenter Server information (username and password) that is registered in the ETERNUS SF system is correct. If there is an error in the registration information, after updating the vCenter Server information that is registered in the ETERNUS SF system with the correct information, re-execute the operation. Grant system administration privileges to the vCenter Server login account that is used with the ETERNUS SF system, or register the account that has system administration privileges in the ETERNUS SF system. After that, re-execute the operation. Check whether the following vCenter Server information is changed: IP address Port number If information was changed, after deleting the vCenter Server registration information that is registered in the ETERNUS SF system, re-register vCenter Server to the ETERNUS SF system. After that, re-execute the operation.
4, 5, 6, 8, 9	If this error occurred during the Single item restore operation From vCenter Server, check the status of the operation target virtual machine. After taking corrective action for the error that is occurring in the virtual machine, re-execute the operation. The operation target virtual machine cannot connect all disks of the VMDK files that are specified with Single item restore. When performing Single item restore, adjust the number of selected VMDK files so that the number of disks that are connectable with the virtual machine is not exceeded. Or change the configuration of the virtual machine so that all disks of the selected VMDK files can connect. After that, re-execute the operation. If there is no space in the SCSI controller, after adding a SCSI controller, re-execute the operation. If this error occurred during an operation other than those above From vCenter Server, check the status of the operation target virtual machine. After taking corrective action for the error that is occurring in the virtual machine, re-execute the operation.
10	There may be an error with the settings or the operating environment of vCenter Server and the VM host where the operation target virtual machine is running. If an error is output for vCenter Server and the VM host, after taking corrective action according to the error, re-execute the operation.
12, 13	From vCenter Server, check the status of the operation target virtual machine. After taking corrective action for the error that is occurring in the virtual machine, re-execute the operation.
14, 21, 27	There may be an error with the settings or the operating environment of vCenter Server and the VM host where the operation target virtual machine is running. If an error is output for vCenter Server and the VM host, after taking corrective action according to the error, re-execute the operation.
40, 41	Check whether there are any problems in the network environment between the Management Server and vCenter Server. If there is a problem, after resolving the network abnormality, re-execute the operation. Check whether vCenter Server is running normally. If not running, after starting vCenter Server, re-execute the operation. Check whether vCenter Server is in a maintenance mode. When in a maintenance mode, after canceling maintenance mode, re-execute the operation. Check whether the vCenter Server information (username and password) that is registered in the ETERNUS SF system is correct. If there is an error in the registration information, after updating the vCenter Server information that is registered in the ETERNUS SF system with the correct information, re-execute the operation. Grant system administration privileges to the vCenter Server login account that is used with the ETERNUS SF system, or register the account that has system administration privileges in the ETERNUS SF system. After that, re-execute the operation. Check whether the following vCenter Server information is changed: IP address Port number If information was changed, after deleting the vCenter Server registration information that is registered in the ETERNUS SF system, re-register vCenter Server to the ETERNUS SF system. After that, re-execute the operation.
100, 101	If this error occurred during the restoration operation from Clone backup The VM host name, IP address, or datastore name may have been changed after the time of Clone backup. After returning the VM host or datastore configuration to the time of Clone backup, re-execute the operation. From vCenter Server, check whether the operation target virtual machine exists. If the virtual machine exists, re-execute the operation by specifying another name. For the operation target virtual machine, the following resources may have been removed or changed from vCenter Server: Virtual machine Connected disk From vCenter Server, check the status of the above resources. If an error has occurred, after removing the cause of the error, re-execute the operation. If this error occurred during an operation other than those above For the operation target virtual machine, the following resources may have been removed or changed from vCenter Server: Virtual machine Connected disk VVOL datastore VM host Snapshot From vCenter Server, check the status of the above resources. If an error has occurred, after removing the cause of the error, re-execute the operation.
110	Re-execute the operation.
113	The number of disks for connecting to the restoration target virtual machine may have reached the upper limit. When performing Single item restore, adjust the number of selected VMDK files so that the number of disks that are connectable with the virtual machine is not exceeded. Or change the configuration of the virtual machine so that all disks of the selected VMDK files can connect. After that, re-execute the operation. If there is no space in the SCSI controller, after adding a SCSI controller, re-execute the operation.
115, 116	Re-execute the operation.
201	When "Timeout occurred in waiting for the response." is displayed in detail Snapshot of a virtual machine to be backed up may have been created. Check the task with vCenter Server for whether any snapshot not existing in the snapshot backup history on the ETERNUS SF system is created. If any snapshot is created, after removing it, re-execute the operation. Also, the vCenter Server environment and Management Server may be highly loaded. If they are highly loaded, after removing the cause, re-execute the operation. In a case other than listed above From vCenter Server, check the task. If an error has occurred, after taking corrective action according to the error, re-execute the operation. If the error cause cannot be determined from the tasks of vCenter Server, take the following actions: Check the status of the storage device where the volume of the virtual machine exists and the connection status between the storage device and the VM host. If an error has occurred, after removing the cause of the error, re-execute the operation. Check whether the ETERNUS Information Provider service of the Management Server is stopped. If the ETERNUS Information Provider service is stopped, after starting the service, re-execute the operation. The number of generations of Snapshot backups may have reached the upper limit. If the number of generations has reached the upper limit, after deleting any unnecessary Snapshot backups from vCenter Server, re-execute the operation. In the vSphere HA environment, VM host switchover may have been in progress by a failover. If a failover is in progress, after completing VM host switchover, re-execute the operation.
202	When "Timeout occurred in waiting for the response." is displayed in detail The virtual machine specified at restore time may have been created. Check the task with vCenter Server for whether the virtual machine with the name specified at restore time is created. If the virtual machine is created, after removing it, re-execute the operation. Also, the vCenter Server environment and Management Server may be highly loaded. If they are highly loaded, after removing the cause, re-execute the operation. In a case other than listed above From vCenter Server, check the task. If an error has occurred, after taking corrective action according to the error, re-execute the operation. If the error cause cannot be determined from the tasks of vCenter Server, take the following actions: Check the status of the storage device where the volume of the virtual machine exists and the connection status between the storage device and the VM host. If an error has occurred, after removing the cause of the error, re-execute the operation. Check whether the ETERNUS Information Provider service of the Management Server is stopped. If the ETERNUS Information Provider service is stopped, after starting the service, re-execute the operation. A virtual machine with the same name as the virtual machine name that was specified at restore may exist. In that case, specify another virtual machine name and re-execute the operation. Due to VVOL datastore free space shortage, the creation of the virtual machine that was specified at restore may have failed. Check whether there is enough free space in the VVOL datastore. If not, after adding a Tier pool that can secure enough free space to create a virtual machine, re-execute the operation. In the vSphere HA environment, VM host switchover may have been in progress by a failover. If a failover is in progress, after completing VM host switchover, re-execute the operation.
203	When "Timeout occurred in waiting for the response." is displayed in detail A temporary volume of Single item restore may have been created. Check with vCenter Server the disks connected to the virtual machine to be restored. If any temporary volume is added, after removing it, re-execute the operation. Also, the vCenter Server environment and Management Server may be highly loaded. If they are highly loaded, after removing the cause, re-execute the operation. In a case other than listed above From vCenter Server, check the task. If an error has occurred, after taking corrective action according to the error, re-execute the operation. If the error cause cannot be determined from the tasks of vCenter Server, take the following actions: Check the status of the storage device where the volume of the virtual machine exists and the connection status between the storage device and the VM host. If an error has occurred, after removing the cause of the error, re-execute the operation. Check whether the ETERNUS Information Provider service of the Management Server is stopped. If the ETERNUS Information Provider service is stopped, after starting the service, re-execute the operation. A temporary volume for Single item restore may already exist. If any temporary volume exists in the virtual machine, delete it from vCenter Server. Also, if the VMDK file specified for the temporary volume exists in the datastore, delete the VMDK file. Refer to "Single Item Restore" in the Storage Cruiser / AdvancedCopy Manager Operation Guide for VMware vSphere Virtual Volumes for details about the temporary volume. The number of disks for connecting to the restoration target virtual machine may have reached the upper limit. When performing Single item restore, adjust the number of selected VMDK files so that the number of disks that are connectable with the virtual machine is not exceeded. Or change the configuration of the virtual machine so that all disks of the selected VMDK files can connect. After that, re-execute the operation. If there is no space in the SCSI controller, after adding a SCSI controller, re-execute the operation. In the vSphere HA environment, VM host switchover may have been in progress by a failover. If a failover is in progress, after completing VM host switchover, re-execute the operation.
204	When "Timeout occurred in waiting for the response." is displayed in detail The vCenter Server environment and Management Server may be highly loaded. If they are highly loaded, after removing the cause, re-execute the operation. In a case other than listed above From vCenter Server, check the task. If an error has occurred, after taking corrective action according to the error, re-execute the operation. If the error cause cannot be determined from the tasks of vCenter Server, take the following actions: Check the status of the storage device where the volume of the virtual machine exists and the connection status between the storage device and the VM host. If an error has occurred, after removing the cause of the error, re-execute the operation. Check whether the ETERNUS Information Provider service of the Management Server is stopped. If the ETERNUS Information Provider service is stopped, after starting the service, re-execute the operation. If you perform the Snapshot from vCenter Server while a temporary volume exists, the temporary volume may not be deleted. After deleting all Snapshots taken after creating a temporary volume, re-execute the operation. If you perform the Snapshot backup while a temporary volume exists, the temporary volume may not be deleted. After deleting histories of all Snapshot backups performed after creating a temporary volume, re-execute the operation. When performing automatic backup operation, stop automatic backup operation temporarily while a temporary volume exists. In the vSphere HA environment, VM host switchover may have been in progress by a failover. If a failover is in progress, after completing VM host switchover, re-execute the operation.
205, 206	When "Timeout occurred in waiting for the response." is displayed in detail The vCenter Server environment and Management Server may be highly loaded. If they are highly loaded, after removing the cause, re-execute the operation. In a case other than listed above From vCenter Server, check the task. If an error has occurred, after taking corrective action according to the error, re-execute the operation. If the error cause cannot be determined from the tasks of vCenter Server, take the following actions: Check the status of the storage device where the volume of the virtual machine exists and the connection status between the storage device and the VM host. If an error has occurred, after removing the cause of the error, re-execute the operation. Check whether the ETERNUS Information Provider service of the Management Server is stopped. If the ETERNUS Information Provider service is stopped, after starting the service, re-execute the operation. In the vSphere HA environment, VM host switchover may have been in progress by a failover. If a failover is in progress, after completing VM host switchover, re-execute the operation.
999	An internal error has occurred in vCenter Server. Collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink00057

Resource data is not consistent.
Server name : serverName

Explanation

Inconsistency in resource information occurred between the ETERNUS SF system and vCenter Server.

Parameters

serverName : Virtual machine name

System Response

The system terminates processing.

System Administrator Corrective Action

The following resources may have been removed or changed from vCenter Server during operation as to the virtual machine that is displayed in serverName:

Virtual machine
Snapshot
Connected disk
VVOL datastore
VM host

From vCenter Server, check the status of the above resources. If an error has occurred, after removing the cause of the error, re-execute the operation.

From vCenter Server, check whether the virtual machine exists. If the virtual machine does not exist, no action is required.

If you still have a problem, collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink00063

Failed to delete Snapshot backup.
Task name : taskName

Explanation

Deleting the Snapshot backup failed because the Snapshot backup is a backup for the temporary volume source of Single item restore.

Parameters

taskName : Scheduler task name

System Response

The system terminates processing.

System Administrator Corrective Action

Execute the scheduler task that is displayed in taskName to remove the temporary volume. Refer to "Regarding Temporary Volume for Single Item Restore Connected to Virtual Machine" in "Restoration" in the Storage Cruiser / AdvancedCopy Manager Operation Guide for VMware vSphere Virtual Volumes for details about the scheduler task.
After that, re-execute the operation.

vmlink00064

The Clone backup volume information was not found.
Storage device name : storageName

Explanation

The volume information for Clone backup is not found because the information failed to obtain from the ETERNUS Disk storage system.

Parameters

storageName : ETERNUS Disk storage system name

System Response

The system terminates processing.

System Administrator Corrective Action

To update to the latest information, reload the configuration for the ETERNUS Disk storage system that is displayed in storageName. After that, re-execute the operation.

vmlink00065

Processing was terminated because virtual machine backup scheduler task was being executed.
Task name : taskName

Explanation

Processing is terminated because the scheduler task of the virtual machine backup is being executed.

Parameters

taskName : Scheduler task name

System Response

The system terminates processing.

System Administrator Corrective Action

After the completion of the execution of the scheduler task of the virtual machine backup that is displayed in taskName, re-execute the operation.

vmlink00067

Failed to delete the backup created beyond the number of generations.
Copy group(s) : copyGroupName
Snapshot name(s) : snapshotName

Explanation

The Snapshot resources or Clone backup resources that are a generation overflow failed to delete.

Parameters

copyGroupName : Copy group name
snapshotName : Snapshot name

System Response

The system continues processing.

System Administrator Corrective Action

If a copy group name is displayed in copyGroupName, refer to the AdvancedCopy Manager Operation Guide for Copy Control Module and delete the copy group.

If a Snapshot name is displayed in snapshotName, the retained generation number of Snapshots is temporarily exceeded. Delete unnecessary Snapshot histories so as to reduce them to the maximum retainable generation number or less.

vmlink00068

Failed to delete the Clone backup history.
Command : commandLine
Content of error : detail

Explanation

Deleting the Clone backup history failed.

Parameters

commandLine : AdvancedCopy Manager Copy Control Module command name
detail : Error context returned by the AdvancedCopy Manager Copy Control Module command

System Response

The system terminates processing.

System Administrator Corrective Action

If the command name and the contents of the error are not displayed, collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink00070

Temporary volumes for Single Item Restore were not found on the virtual machine configuration.
VMDK file names : temporaryVolumeName

Explanation

The temporary volume could not be deleted because the temporary volume was not found in the virtual machine configuration information.

Parameters

temporaryVolumeName : Undeleted temporary volume (VMDK file)

System Response

The system continues processing.

System Administrator Corrective Action

The temporary volume may have been disconnected from the virtual machine.
Since a temporary volume may exist in the datastore, check whether the temporary volume (VMDK file) that is displayed in temporaryVolumeName exists in the datastore of vCenter Server. If so, delete the temporary volume (VMDK file).
When a temporary volume was connected to the virtual machine, the virtual machine migration (Storage vMotion) may have been performed.
The VMDK file name of the temporary volume connected to the VM may be changed and different to the temporary volume (VMDK file) that is displayed in temporaryVolumeName. Delete the temporary volume that is currently connected to the virtual machine manually.
The virtual machine may have been deleted.
From vCenter Server, check whether the virtual machine exists. If not, no action is required.

vmlink00072

The process was terminated because the auto execution of virtual machine backup had already been enabled.
Server name : serverName
Task name : taskName

Explanation

The process was terminated because the auto execution of virtual machine backup had already been enabled.

Parameters

serverName : Virtual machine name
taskName : Scheduler task name

System Response

The system terminates processing.

System Administrator Corrective Action

The auto execution of virtual machine backup is already enabled. Check whether the status of the scheduler task that is displayed in taskName is "Waiting".

vmlink00073

The process was terminated because the auto execution of virtual machine backup had already been disabled.
Server name : serverName
Task name : taskName

Explanation

The process was terminated because the auto execution of virtual machine backup had already been disabled.

Parameters

serverName : Virtual machine name
taskName : Scheduler task name

System Response

The system terminates processing.

System Administrator Corrective Action

The auto execution of virtual machine backup is already disabled. Check whether the status of the scheduler task that is displayed in taskName is "Disable".

vmlink00074

Resource data is not consistent.
VVOL Datastore name(s) : datastoreName
VM Host name : vmHostName

Explanation

The restoration from Clone backup failed because inconsistency occurred in the resource information of vCenter Server after the time of Clone backup.

Parameters

datastoreName : VVOL datastore name
vmHostName : VM host name

System Response

The system terminates processing.

System Administrator Corrective Action

The following resources may have been changed after the time of Clone backup:

VVOL datastore
From vCenter Server, check whether the VVOL datastore that is displayed in datastoreName exists. If the VVOL datastore does not exist, after performing one of the following actions, re-execute the operation:
- Create a VVOL datastore with the name that is displayed in datastoreName
- Change the name of the restore source VVOL datastore of Clone backup to the name that is displayed in datastoreName
VM host
From vCenter Server, check whether the VM host that is displayed in vmHostName exists. If the VM host does not exist, after changing the name of the VM host where the restore source virtual machine of Clone backup exists to the name that is displayed in vmHostName, re-execute the operation.

If you still have a problem, collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink00080

Failed to execute Clone backup.
Server name : serverName
Message : message

Explanation

As an error occurred during Clone backup, Clone backup failed.

Parameters

serverName : Name of the virtual machine in which the operation failed
message : Error Message

System Response

The system terminates processing.

System Administrator Corrective Action

If the message starts with "STXS"
Take appropriate action indicated by [System Administrator Corrective Action] in "A.2 Messages of STXS Prefix".
If the message is "errorCode=0060"
Another processing may be using the device. After waiting for a few minutes, re-execute the operation.
If the message is "errorCode=03" or "errorCode=5324"
A failure may have occurred in the hardware. Check the status of the volume whose number is displayed in message. If an error has occurred, after removing the cause of the error, re-execute the operation.
If the message is "errorCode=5316"
Cascade copy (copy to another volume) from a Clone backup volume is in progress. After waiting for the cascade copy from the Clone backup volume of virtual machine that is displayed in serverName to complete, re-execute the operation.
If the message is "errorCode=5373"
Backup failed because, during backup, another operation was executed toward the volume to be backed up from the ETERNUS SF system. After the operation toward the volume to be backed up has finished, re-execute the operation.
During backup, do not perform any other operation toward the volume to be backed up from the ETERNUS SF system.
If the message is "errorCode=5360" or "errorCode=5395"
Currently, the specified operation is not executable. After waiting for a few minutes, re-execute the operation.
In cases other than those listed above
While the backup was in progress, for the virtual machine that was displayed in serverName, the following resources may have been removed or changed from vCenter Server:
- Virtual machine
- Snapshot
- Connected disk
From vCenter Server, check the status of the above resources. If an error has occurred, after removing the cause of the error, re-execute the operation.

If you still have a problem, collect the information required for troubleshooting and contact Fujitsu Technical Support.

vmlink90001

Failed to apply policy. Two or more operations were executed at the same time for the virtual machine specified for "Server". Execute the operation again. If this error is repeated, contact the system administrator.
Server name : serverName

Explanation

The policy failed to apply.

Parameters

serverName : Virtual machine name

System Response

The system terminates processing.

Operator Corrective Action

Multiple operations may have been performed simultaneously for the virtual machine that is displayed in serverName.

From vCenter Server, check whether any processes are running for the virtual machine that is displayed in serverName.
If a running process exists, after that process is completed, re-execute the operation.

If this error repeats, contact the system administrator.

System Administrator Corrective Action

Multiple operations may have been performed for the virtual machine that is displayed in serverName at one time.

In the Operation History screen of Web Console, check whether any processes are running for the virtual machine that is displayed in serverName.
If a running process exists, after that the process is completed, re-execute the operation.

If this error repeats, collect the information required for troubleshooting and contact Fujitsu Technical Support.