Table of Contents
Advertisement
Whether S-VOL is mapped to a backup server
For a failure during a backup by Business Copy, confirm that the target S-VOL is not mapped to
a backup server using Storage Management Software.
When the target S-VOL is mapped to a backup server, un-map it using Storage Management
Software.
Whether V-VOL is created by VSS Provider
For a failure during a backup by Snapshot, confirm the V-VOL# created by VSS Provider from
VSS Provider log.
Checking for the existence a V-VOL created by VSS Provider and V-VOL#
When a V-VOL is created, the following message is output in the VSS Provider log:
Message ID "S100001F", Message "Successfully created V-VOL", V-VOL#
Shown below is the example of the log message which is output during V-VOL creation.
[5184] [13/07/26-12:03:25.001] [HIAPI
Successfully created V-VOL:[??:-01:-1(64033)] for P-VOL:[6F:037:0(8204)]
When the target V-VOL remains, delete the target V-VOL by using the GUI tool or Storage
Management Software.
NOTE:
For the VMware Guest to Guest Backup (FC) function, confirm that the target V-VOL
has not been set to RDM by using vSphere Client. If RDM has been set, delete V-VOL after
unmapping RDM.
An online status of the P-VOL
For a failure during a restore by ResyncLun, confirm the online/offline status of the P-VOL.
When a failure occurs during a restore by ResyncLuns, P-VOL remains in offline status to protect
the consistency of the data. Set the target LUN online status from Server Manager->Disk
Management as needed.
Resource lock status
For a failure when using VSS Provider and GUI tool, confirm the resource lock status of the disk
array system.
Check the resource lock status using Storage Management Software or RAID Manager. If a user
name (user name used for the registration through the Add Storage function of GUI tool) which
is used for the user authentication of the disk array system locks the resource, unlock the
corresponding resource.
Existence or non-existence of RDM setting and VMDK file
If a failure occurs during a backup, check an existence of RDM setting and VMDK file created
during RDM setting.
From the VSS provider log:
1.
Check the virtual device node performed the RDM setting during the backup time and the
VMDK file name created during RDM setting.
Naming rule of VMDK file is as follows:
136 Troubleshooting
]
STAT
[S100001F] {CHiManagementAPI::createVVOL}:
Advertisement
Table of Contents
