• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 333
  • Last Modified:

SQL 2008 Cluster Sharepoint backend

We have a SQL 2008 cluster that appears to be broken.  There is a virtual instance (vsqlspntdb1) and 2 physcial nodes (sqlspnt01, sqlspnt02) Sqlspnt02 is the "owner" of the cluster but it should be the vsqlspntdb1.  
When I right click on a node, I don't see any option to move the resource to another node.  I'm unable to create a new maintenance plan or modify an existing plan - BUT the existing maintenance plan appeared to have run.  Haven't been able to verify because I can't remember where we're backing up to and I can't open the maintenance plan to verify/modify it.
  • 2
1 Solution
Are you able to connect to the SQL Server Instance from management studio?

What is the errors you see when you mentioned - the sql cluster appears broken and unable to edit maintenance plan?

skbarnardAuthor Commented:
Yes, I can connect but normaily one would see a green right facing arrow on both the instance and the agent, I see only a white circle.
When I right click the existing maintenance plan and choose "modify", a window should open.  No window opens, no error shows up.
A real funny thing, I can log into one physical server and the virtual but if I try to log into the last server in the cluster, I get kicked off of the virutual.  
I don't know if that information is helpful, it's quite a curiosity for me.
skbarnardAuthor Commented:
Turns out we called Microsoft for this issue and found if we used the "run as" administrator option, we could alter existing or create new maintenance plans.  It appears we may still have to rebuild our SQL cluster but for now, this issue was resolved.

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now