SMHV Restore operation failed Error code: 102 SDSnapshotRestore failed

[#1]

i communities,

with latest NetApp version "P" software, in Hyper-v r2 environment , all Restore Job failed with VSS errors and lun clone stay on NetApp Box with snapshots in busy status.

Manual operation with snapdrive are ok.

Here's the job log report :

Recovery Report file Created
[1/15/2011 10:31:46 PM, (5)] SnapManager Restore Report

Object to be restored:
LAB-SQL1[Hyper-V]

Backup to be used for restore:
FIRST_01-15-2011_22.11.04[FIRST_01-15-2011_22.11.04] created at 1/15/2011 10:11:04 PM

Input Parameters:
StartVM : true
verify_snapshots : false
time_stamp : 1/15/2011 10:31:45 PM
job_id : 05ab435f-18dd-46e7-97f3-f218eb12e10a

[1/15/2011 10:31:47 PM, (5)] Validating restore request
[1/15/2011 10:31:47 PM, (5)] Validation of restore request completed.
[1/15/2011 10:31:47 PM, (5)] Processing restore of hyper-V VM on host HV1...
[1/15/2011 10:31:47 PM, (5)] Retrieving backup metadata...
[1/15/2011 10:31:47 PM, (5)] Checking whether SnapManager for Hyper-V is licensed to run on the host..
[1/15/2011 10:31:48 PM, (5)] SnapManager for Hyper-V is licensed to run on the host, starting the restore operation
[1/15/2011 10:31:48 PM, (5)] Finding the host for restore operation
[1/15/2011 10:31:48 PM, (5)] Checking if [HYPERV] is a clustered system..
[1/15/2011 10:31:48 PM, (5)] Retrieving resource information for VM [4D9FC721-8B44-4C1E-AF0D-1571B447707C]
[1/15/2011 10:31:49 PM, (5)] Retrieval of resource information for VM [4D9FC721-8B44-4C1E-AF0D-1571B447707C] completed successfully.
[1/15/2011 10:31:49 PM, (5)] Owner of VM [HV1]
[1/15/2011 10:31:49 PM, (5)] Restore host is HV1
[1/15/2011 10:31:49 PM, (5)] Continuing restore operation on host HV1
[1/15/2011 10:35:12 PM, (5)] Taking VM cluster resource Virtual Machine LAB-SQL1 offline...
[1/15/2011 10:35:41 PM, (5)] Taking VM Configuration cluster resource Virtual Machine Configuration LAB-SQL1 offline...
[1/15/2011 10:35:42 PM, (5)] Determining Snapinfo disk owner..
[1/15/2011 10:35:44 PM, (5)] Determining Snapinfo disk owner completed successfully.
[1/15/2011 10:35:44 PM, (5)] SnapInfo Disk owner: HV1
[1/15/2011 10:35:44 PM, (5)] Executing VSS restore...
[1/15/2011 10:35:44 PM, (5)] Initializing VSS for restore
[1/15/2011 10:35:44 PM, (5)] Initializing VSS writer/component information
[1/15/2011 10:35:45 PM, (5)] Adding components for restore
[1/15/2011 10:35:45 PM, (5)] Notifying VSS writers to prepare for restore
[1/15/2011 10:35:46 PM, (5)] Restoring data
[1/15/2011 10:55:53 PM, (5)] Error: Vss Requestor - Restore Components failed.Failed to restore one or more components.
Failed component: \4D9FC721-8B44-4C1E-AF0D-1571B447707C
Error code: 102
Error message: SDSnapshotRestore failed

[1/15/2011 10:55:53 PM, (5)] Restore task: failed to complete
[1/15/2011 10:55:53 PM, (5)] AutoSupport is disabled, AutoSupport update will not be performed
[1/15/2011 10:55:53 PM, (5)] An error occured while performing the VM restore.
[1/15/2011 10:55:53 PM, (5)] An error occured while executing the restore operation.
[1/15/2011 10:55:53 PM, (5)] Error: Vss Requestor - Restore Components failed.Failed to restore one or more components.
Failed component: \4D9FC721-8B44-4C1E-AF0D-1571B447707C
Error code: 102
Error message: SDSnapshotRestore failed

[1/15/2011 10:55:53 PM, (5)] An error occured while processing the recovery.
Error: Vss Requestor - Restore Components failed.Failed to restore one or more components.
Failed component: \4D9FC721-8B44-4C1E-AF0D-1571B447707C
Error code: 102
Error message: SDSnapshotRestore failed

[Error Code: -1056898792]

Christophe

[#2]

Hi,

Please check the Windows application event log on Hyper-V parent host for any errors from SnapDrive during restore operation.

Thanks,

Anagha

[#3]

Here the filtered log from application Event :

snap shot copy OK, begin of restore operation ok, and after minutes operation failed

Level Date and Time Source Event ID Task Category
Information 1/15/2011 10:58:53 PM VSS 8224 None The VSS service is shutting down due to idle timeout.
Error 1/15/2011 10:55:53 PM SnapMgrServiceHost 109 Restore Event "SnapManager for Hyper-V restore operation failed to complete
Error: Vss Requestor - Restore Components failed.Failed to restore one or more components.
Failed component: \4D9FC721-8B44-4C1E-AF0D-1571B447707C
Error code: 102
Error message: SDSnapshotRestore failed

"
Error 1/15/2011 10:55:52 PM SnapDrive 437 Snapshot Copy event File Level Restore failed with error code 0xc0041045
Error 1/15/2011 10:55:52 PM SnapDrive 425 Snapshot Copy event SnapDrive was unable to dismount snapshot C:\ProgramData\NetApp\SnapDrive\SDWFLR\79fb13cd-96c1-4adc-8a0d-2847e5a09954-2\. Please manually cleanup snapshot mount.
Error 1/15/2011 10:55:52 PM SnapDrive 182 Generic event "Failed to force disconnect the LUN in Snapshot copy, drive (C:\ProgramData\NetApp\SnapDrive\SDWFLR\79fb13cd-96c1-4adc-8a0d-2847e5a09954-2\).

LUN Name = Not available
Storage Path = Not available
Storage System Name =

Error code : The requested operation is not supported.
."
Error 1/15/2011 10:54:27 PM SnapDrive 425 Snapshot Copy event SnapDrive was unable to dismount snapshot C:\ProgramData\NetApp\SnapDrive\SDWFLR\8abcf30f-e142-45a6-b314-2e6e87549a29-2\. Please manually cleanup snapshot mount.
Error 1/15/2011 10:54:27 PM SnapDrive 182 Generic event "Failed to force disconnect the LUN in Snapshot copy, drive (C:\ProgramData\NetApp\SnapDrive\SDWFLR\8abcf30f-e142-45a6-b314-2e6e87549a29-2\).

LUN Name = Not available
Storage Path = Not available
Storage System Name =

Error code : The requested operation is not supported.
."
Information 1/15/2011 10:51:59 PM SnapDrive 427 Snapshot Copy event Restoring using File Copy for file C:\ClusterStorage\Volume2\Virtual Machines\4D9FC721-8B44-4C1E-AF0D-1571B447707C\4D9FC721-8B44-4C1E-AF0D-1571B447707C.vsv from snapshot FIRST_HYPERV_HV1_01-15-2011_22.11.04_backup
Information 1/15/2011 10:51:50 PM SnapDrive 427 Snapshot Copy event Restoring using File Copy for file C:\ClusterStorage\Volume2\Virtual Machines\4D9FC721-8B44-4C1E-AF0D-1571B447707C\4D9FC721-8B44-4C1E-AF0D-1571B447707C.bin from snapshot FIRST_HYPERV_HV1_01-15-2011_22.11.04_backup
Warning 1/15/2011 10:50:47 PM Microsoft-Windows-WMI 5605 None The root\MSCluster namespace is marked with the RequiresEncryption flag. Access to this namespace might be denied if the script or application does not have the appropriate authentication level. Change the authentication level to Pkt_Privacy and run the script or application again.
Warning 1/15/2011 10:49:16 PM Microsoft-Windows-WMI 5605 None The root\MSCluster namespace is marked with the RequiresEncryption flag. Access to this namespace might be denied if the script or application does not have the appropriate authentication level. Change the authentication level to Pkt_Privacy and run the script or application again.
Information 1/15/2011 10:47:18 PM SnapDrive 427 Snapshot Copy event

Christophe

[#4 · Accepted solution]

As per the burt464870 this is a known issue in SnapDrive for Windows.

This issue happens during the disconnect of the snapshot mount LUN when the LUN from snapshot is backed

by a LUN clone instead of flexclone. This issue does not happen when the LUN from snapshot is backed by a flexclone volume.

[mostly when the flexclone license is not present and SDW uses the LUN clone to connect the LUN to the host]

Following is the public report about this burt, please try to use flexclone license and see whether the issue goes away.

%%% TITLE: Dismounting connected LUN in snapshot is throwing error "The requested operation is not supported".
%%% DESCRIPTION:
SnapDrive creates LUN clone when users connect to LUN in snapshot and if we dont
have flexclone license on the storage system. And dismounting the LUN through
'sdcli snap unmount' is failing with the error "The requested operation is not
supported". The same error we get when SMSQL does the backup verification.
The disconnect LUN from MMC and 'sdcli disk disconnect' works fine.

%%% WORKAROUND:
Enabling flexclone license will let SnapDrive use flexclones instead of LUN
clones.

%%% NOTES:
None

Thanks,

Vineeth

[#5]

vineeth,

Restore job with Flexclone License are ok.

Thanks you for the help

Christophe