syspolicy_purge_history job failing

Basically, had to fix powershell command line to use the cluster virtual server name for each instance vs the server name...

Reference:
http://support.microsoft.com/kb/955726

SQL 2008 Cluster installation fixes

Spent all day working on trying get one named instance of SQL 2008 installed on a Win 2008 R2 cluster.

Anyway, these are the things I encountered:

• SQL server 2008 failover cluster 'RequireKerberos' error;  The fix was to slipstream SQL 2008 SP1 into the installation process
• SQL cluster resource would not startup at end of installation; Name resource could not come online.  The fix was to give cluster computer name FULL CONTROL of the virtual instance names in Active Directory using ADUC.
• Verification check prior to installation would fail and not allow me to install SQL.   After manual verification that things should be ok, I used this command "setup /SkipRules=Cluster_VerifyForErrors /Action=InstallFailoverCluster /PCUSource=c:\SP1" to finally start up the installation process.

References:
http://trilist.blogspot.com/2010/02/fix-sql-server-2008-failover-cluster.html

Active/active SQL 2005 Cluster problem

Our SQL 2005 cluster experienced a power blip due to computer room issue. Quorum and SQL3 instance were on physical SVR1 and SQL4 instance was on physical SVR2. The outage took out Active Directory and most of the network in the computer room. The cluster has shared disks on a Netapp connected via iSCSI. All equipment went down and came back up on their own.

When power came back up, SVR1 was offline in the cluster and all services were online on SVR2.

I rebooted SVR1 and it rejoined the cluster and was able to move the Quorum and SQL3 back to SVR1.

This is when we noticed a issue with the SQL4 instance. Applications on a .NET webserver that use SQL4 databases, could not connect to their databases. The developers (non-admin users) could not connect via SSMS 2008 to their databases on SQL4. I (admin on SQL servers) can connect to SQL4 with either SSMS 2005 and SSMS 2008.

To get the applications working, I failed over SQL4 to SVR1 and now everyone and all apps can connect to SQL4.

Any ideas what is wrong? I suspect a problem with SVR2, but not sure what since it appears to be functioning within the cluster ok and cluster groups have no problem failing over and starting up on that physical node.

UPDATE: Apps show this error when trying to connected to SQL4 on SVR2:

Error:
(A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified))

UPDATE 2: SQL Browser service was not starting on SVR2, duh. Fixed by removing SQL from node, evicting from cluster, then re-adding server to cluster, and adding node to SQL 2005 instances using SQL 2005 Setup.

Cluster service dependency in a pure iSCSI clustering environment

Reference:
http://support.microsoft.com/kb/883397

P2V SQL Cluster nodes

Using P2V to convert a cluster nodes to virtual server instances.

Reference: http://www.mssqltips.com/tip.asp?tip=2355