Subscribe

SnapMirror for Exchange Business Continuance failed due to SnapDrive Check policy fail

I encounter a problem below,

I use SnapMirror for Exchange Business Continuance to realize DR process.

Anything is ok when I use production resource ( snapmirror source volume).

Process failed when I use DR resource (snapmirror destionation volume).

Error message is "Error in connecting LUN: [[Storage System: fas3020demo1, Lun: /vol/exchange2003_log_mirror/log.lun, Host Mount Point: L]], Details: Error 0xc0040359 occured. Description is not found." in Business Continuance report.

Another Error message is "

Failed to connect to LUN. Failure in checking policies.

LUN Name = log.lun
Storage Path = /vol/exchange2003_log_mirror/
Protocol Type = LUN
Storage System Name = fas3020demo1
Requested Mount Point = J
Assigned Mount Point = J

Error code : An attempt to quiesce snapmirror on a destination 'fas3020demo1:exchange2003_log_mirror' failed. Error code: 13102. Error description: snapmirror quiesce: exchange2003_log_mirror : destination is not in snapmirrored state ." in Windows Event log (SnapDrive error).

I think about business continuance fail due to SnapDrive protection policy.

But, the check policy will affect Busincess Continuance successful.

Anyone know any solution for this or what version can resolve the problem.

I have been tried SnapDrive 6.0 , 6.0p1 , 6.0.1

Re: SnapMirror for Exchange Business Continuance failed due to SnapDrive Check policy fail

Hi Sheng-mao...

Error code : An attempt to quiesce snapmirror on a destination 'fas3020demo1:exchange2003_log_mirror' failed. Error code: 13102. Error description: snapmirror quiesce: exchange2003_log_mirror : destination is not in snapmirrored state ." in Windows Event log (SnapDrive error).

This error leads me to believe that the snapmirror between the primary and secondary isn't in a "snapmirrored" state when you do your failover. Are you, by chance, manually breaking the mirror relationships, then executing the BCM failover?

Thanks...

Shannon