September 15, 2011 at 9:31 am
We have an odd situation, not helped by the fact that our main server admin guy has moved on to pastures new and I know little about cluster configuration / troubleshooting.
At the weekend the SQL cluster (two nodes, active passive) was shut down for some UPS maintenance work. When it was bought back up the SQL cluster looked Ok all databases there etc.
Previously I was able to get to the backup drive via \\cluster_name\share_name now however I have to use \\active_node_name\share_name
I don’t know if I have given enough information for anyone to start to help – tried google but haven’t had much luck there.
Anyone have any ideas on how to get this rectified?
Thanks
-------------------------------Posting Data Etiquette - Jeff Moden [/url]Smart way to ask a question
There are naive questions, tedious questions, ill-phrased questions, questions put after inadequate self-criticism. But every question is a cry to understand (the world). There is no such thing as a dumb question. ― Carl Sagan
I would never join a club that would allow me as a member - Groucho Marx
September 15, 2011 at 9:41 am
I take it that the share is on one of the cluster nodes and not somewhere on the shared disk? If so, what has happened is that the cluster group was previously running on the same node that the share was on, so \\ClusterName\ShareName took you straight to the share. Now, however, the cluster group has failed over (or been moved) to the other node, so \\ClusterName\ShareName is not found because the share does not exist on the same node that the cluster is running on. To verify this, run Cluster Administrator to see what node owns the cluster group.
The best way to get round this is to create the share on shared disk, and then set up that share as a clustered resource. That way, it will always be available.
John
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply