On a dark and stormy night an Active Directory upgrade was underway, Windows Server 2003 domain controllers decommissioned, consolidated and replaced with Window Server 2008 R2 servers. Suddenly I got a call from those doing the upgrade, “I can’t see some of the new domain controllers on the existing domain controllers, what’s wrong?” A replication island had been created and several domain controllers were trapped on it. Could we rescue them in time?
David, I can’t figure this one out easily s… Anu - Mar 1, 2009David, I can’t figure this one out easily since I don’t have a deep knowledge of SQL. I’d appreciate your feedback. I am beginning to understand the different options and implementaions for scaling out SQL HA/DR/automatic failover. In ILM “2” architecture, with scaling out MIIS and its SQL, can performace improvements and concurrent MA runs be achieved? I think not but I’d like to wrong this time!
First, let me say thank you to Alex Tcherniakhovski for pioneering the way in clustering the MIIS Service or as it is now known the ILM Sync Engine. That blog, presentation and script was an excellent set of work. http://blogs.msdn.com/alextch/archive/2005/12/17/clusteredmiis.aspx On Windows Server 2008, a few things have changed that break the script that Alex T. provides. In Windows Server 2003 the cluster services runs as a domain account and as long as the user has access to all nodes, to stop and start services, and as an MIIS Administrator then it should be able to do the trick.
Yeah, WOW, not a quick and easy process by any means! Brad Turner - Sep 3, 2008Yeah, WOW, not a quick and easy process by any means! Good Info - Important Note: If you are dealing with a vm guest attached to a Hyper-V Cluster, You’ll need to use Failover Cluster Manager in Administration Tools on one of the Cluster Nodes - After making the change, go to a Command Prompt and enter the following:
While building out some virtual machines for our ILM 2 Beta 3 environment… We setup a few virtual machines 64 bit Windows Server 2008 SP 1 (since SP 1 is built in to the RTM) running on HyperV. Everything is very slick! Except we only set aside 16 GB for the virtual disk for the system partition. Despite installing SQL, SharePoint, and ILM 2 to another drive the system partition quickly filled up, and didn’t have enough room for Visual Studio (even though I wanted to install it on another partition).
