Question Locked

Windows 2003 DR fails (SAN boot)

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I've a setup with a primary site with a HP bladesystem booting from SAN (Windows 2003) with SAN replication to a secondary site. When I start the secondary server Windows mashup the IP configuration because of detection of new networkcards.

The hardware configuration seems to be fully equeal including biossettings and hardwarerevision of the nics.

Any idea why Windows detects new NICS?

2 replies

by muzza2005

IP change on remote DR server (local prod server = ?A?, so remote DR server= ?B?):

Ensure DNS TTL values are set to maximum time it takes to failover e.g. 15 minutes

Reverse R1-R2 replication to R2-R1

Assume ?B? operational on DR LUNs, so remote log into ?B? ILO and reconfig to point at R2, and reboot

?B? boots with Production configuration so IP identity is wrong: re-access ?B? ILO and change IP parameters (source, gateway, subnet mask, etc); Win2003 recognises new parameters without reboot and *DDNS server automatically updates the entry

(*this is 2009 ? no excuse for not having DDNS)

This discussion is closed to new replies.