Subject
미러 볼륨 페일오버 실패
APPLIES TO:
Windows2003ent
MCCS 3.1
SYMPTOMS
"Split-Brain Issue
CreateMirror Failure Issue"
CAUSE
"Mirror Volume : F
For the SPLIT-BRAIN, I did following steps to produce the issue.
checked that mirror role on primary server 'adam' was SOURCE and mirror role on secondary server 'eve' was TARGET and mirror state was MIRROR.
shutdown primary server 'adam'
reboot secondary server 'eve'
""emcmd . deletelocalmorroronly"" on 'eve',
""emcmd 200.200.200.2 createmirror f 200.200.200.1 s 3"" on 'eve', immediately after #4 had returned 0
""emcmd . getvolumeinfo f 3"" on 'eve' said that mirror role was SOURCE and mirror state was RESYNC_PENDING
startup primary server 'adam'
""emcmd . getvolumeinfo f 3"" on 'adam' said that mirror role was SOURCE and mirror state was PAUSED
Why couldn't mirror volume on primary server 'adam' change it's mirror role to TARGET during ""boot time mirror role check""?
You can check detailed kernel logs in the attached Debugview log files named as 'split-brain-adam.LOG' and 'split-brain-eve.LOG'.
For the CREATEMIRROR FAILURE issue, I did following steps
checked that mirror role on primary server 'adam' was SOURCE and mirror role on secondary server 'eve' was TARGET and mirror state was MIRROR.
shutdown primary server 'adam'
reboot secondary server 'eve'
""emcmd . deletelocalmorroronly"" on 'eve',
""emcmd 200.200.200.2 createmirror f 200.200.200.1 s 3"" on 'eve', immediately after #4 had returned 0
""emcmd . getvolumeinfo f 3"" on 'eve' said that mirror role was NO_MIRROR
according to windows system events, mirror role changed like ""TARGET->NONE->SOURCE-NONE""
retried #5, and it failed with result of ""Status = 87""
startup primary server 'adam'
""emcmd . getvolumeinfo f 3"" on 'adam' said that mirror role on primary server 'adam' was SOURCE and mirror role on secondary server 'eve' was TARGET and mirror state was MIRROR.
Why did mirror role on 'eve' change from SOURCE to NONE? I couldn't find any reason for second 'Mirror Deleted' event.
Furthermore, why did mirror role on 'eve' change from NONE to TARGET after primary server had come up again?
You can check detailed kernel logs in the attached Debugview log files named as 'createmirror_error-adam.LOG' and 'createmirror_error-eve.LOG'.
Also I attached Windows system event logs for both systems.
We have been experiencing many troubles in integrating DK with MCCS, but we couldn't report these issues before without the exact case.
If you do those steps 10 times, I'm sure you can reproduce these issues at least one time."
SOLUTION
Attached is the 32-bit driver.
If you are still getting BSOD, I'd like to get the MEMORY.DMP file from your system so I can see what's happening. But I hope it's simply a matter of using the 32-bit driver.
ExtMirr_32.zip.OK
패치 버전을 이후로 문제가 재현되지 않음으로 종결
Fixed MCCS 3.2