2003 Cluster Lost Data Drive

• Previous message: Peter: "Re: Cluster migration from NT4 domain to Windows 2003 domain"
• Messages sorted by: [ date ] [ thread ]

Date: Tue, 29 Jun 2004 14:53:29 -0400

Here's the setup:
    Windows 2003 Enterprise (Fully Patched)
    SQL Server 2000 SP 3
    Quorum(E:) and Data(F:) disks on same external SCSI Raid

Here's the problem:
    I've lost the ability to do anything to Data(F:) drive. I am able to
work with Quorum(E:) disk with no problems.

Here's the symptoms:
    This problem is causing the MSSQL service not to start, stating that it
does not have permissions on Data(E:), however I can't access that disk via
any account (local admin or domain admin). The Cluster Service does start,
however I cannot connect to cluster via Cluster Administrator. Nor can I
connect to my virtual instances via SQL Server Enterprise Manager.

Here's how it happened:
    I have had two web servers also serving as domian controllers being
serviced by my active/passive SQL Server Cluster in testing for the past 6
months with no noticeable problems. However, since we're now moving them
into production, our Security Manager said that we can't have ADS and IIS on
the same machine in the production environment.
    So I setup another 2003 machine with plans to add it to the domain as a
BDC (not really as all 2003's are peers) and then pass control of everything
from the current PDC to the new machine. However, it appears that
unbenownst to me and the log files, the PDC became corrupt and would not
accept another controller, nor would it let me remove the current BDC. It
also would not allow me to remove ADS from it no matter how much I begged
and pleaded ;o)
    So I setup the new machine as the PDC from the get go and rejoined my
cluster to the new domain (not really new as it was named the same), slicked
the web/ADS computers, and added them to the domain. That's when I lost
both the Quorum(E:) and Data(F:) drives.
    I was able to get the Quorum back by deleting the old SIDs and assiging
the new user account with no problems, however, I'm stuck with the problem
listed above.
    Since I am unable to use the SEM to change user info on the database,
I've done it manually using KB283811, but to no avail.

Here's what I'm doing now:
    Banging my head against the wall in frustration ;o)

TIA,

Jim

• Previous message: Peter: "Re: Cluster migration from NT4 domain to Windows 2003 domain"
• Messages sorted by: [ date ] [ thread ]