Re: Startup problems on one of 2 nodes
- From: "Anthony Thomas" <ALThomas@xxxxxxxxx>
- Date: Sun, 11 Mar 2007 20:57:08 -0500
If you can get the resources running on the primary node, then while those
resources are online, then you can change the registry settings. If you try
to change the settings while the resources are offline, they will not take
since the keys will be reloaded from the local cluster database upon
startup.
Here is a link on how to repair cluster resource configurations, and a link
to a utility to reestablish checkpoints across the nodes.
http://support.microsoft.com/kb/258078
http://www.microsoft.com/downloads/details.aspx?familyid=2BE7EBF0-A408-4232-9353-64AAFD65306D&displaylang=en
The utility comes with a document that describes how to recover checkpoint
files as well as how to replace physical disk resources. The advantage of
using this utility is that you can swap out SAN LUNs and keep the original
drive letters. The advantage here is that there should be no need to modify
the registry keys for new path definitions.
Good Luck.
Sincerely,
Anthony Thomas
--
"R Stovall" <richard-at-@xxxxxxxxxxxxxxxxx> wrote in message
news:77800248-FD22-4351-ABCD-ED8ADF4C6ACE@xxxxxxxxxxxxxxxx
Update:SQL
There does not appear to be a registry checkpoint associated with the SQL
server resource. None of the GUIDs on the quorum disk are related to the
server resource. Could this be why the changes were not replicated to the
second node?
Additionally, cluster res "SQL resource name" /check returns no registry
checkpoints.
Is the fix simply to update the startup parameters in the registry on the
second node then create a registry checkpoint to prevent further issues in
the future?
Thanks,
RS
.
- Prev by Date: Re: SQL Resources FAIL when restarting "Passive" Node
- Next by Date: Re: SQL Resources FAIL when restarting "Passive" Node
- Previous by thread: Re: SQL Resources FAIL when restarting "Passive" Node
- Next by thread: SQL Connectivity Lost after Reboot
- Index(es):
Relevant Pages
|