Hi,
we have a win2000 adv cluster with sql server 2000 ent.
last time i had to move resources from active node to passive node, i
had big troubles.
Moving groups caused many sql db files damaged, having db marked
'suspect'
Why ? Do you know any possible reason ?
This cluster does not have a different drive for quorum disk and i
think that files needed by cluster service (log, checkpoint, ...) are
on the only shared disk, where are stored all db files.
Could be this the reason ?
Thanks in advance...
I'm not even going to ask how you got this to work in this configuration.
But, yes, it would be a problem.
Although, I suspect, that a bigger problem is that you have some form of
Disk Write Back Caching enabled.
I'd look through you server's System Event logs for various disk related
errors.
Normally, SQL Server REQUIRES a dedicated resource group, with an
independent Disk, IP Address, and Network Name resource, although the SQL
Server setup program will add the IP and Name resources for you (it will
actually bomb if those resources already exist in the group).
Sincerely,
Anthony Thomas
"The Bedroom" <thebedroom71@.gmail.com> wrote in message
news:1163973423.582387.314090@.m7g2000cwm.googlegro ups.com...
> Hi,
> we have a win2000 adv cluster with sql server 2000 ent.
> last time i had to move resources from active node to passive node, i
> had big troubles.
> Moving groups caused many sql db files damaged, having db marked
> 'suspect'
> Why ? Do you know any possible reason ?
> This cluster does not have a different drive for quorum disk and i
> think that files needed by cluster service (log, checkpoint, ...) are
> on the only shared disk, where are stored all db files.
> Could be this the reason ?
> Thanks in advance...
>
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment