The Usual Tech Ramblings

Cluster Services, and moving resources...

This week has been rather busy, finishing off the deployment of a bunch of SQL clusters for a major project the entire company is working on. Yesterday I spent the entire day fighting an install of a single instance of SQL with all kinds of errors1. But this one is a quick post on an easy error we stumbled upon this morning…

When we’d finished building one of the SQL instances, we needed to move the “Available Storage” group in Microsoft Failover Cluster Manager to the other node so we could build the next SQL instance. This is done using the cluster.exe command as such:

cluster *clustername* group "Available Storage" /MoveTo:*newnode*

Where clustername and newnode are the cluster name, and node you want to move the “Available Storage” group to. However we hit a snag, and it dumped the following error:

System error 5016 has occurred (0x00001398).
The operation failed because either the specified cluster node is not the owner of the group, or the node is not the possible owner of the group.

No matter what we specified in the command, this error kept coming up. Fortunately this is usually easy to fix, and is a case of a few mouse clicks. The problem is caused by a disk resource not marked for use on both nodes of the cluster, so the entire group will not migrate over. To fix this:

  1. Right click on a drive resource in “Available Storage”.
  2. Select Properties.
  3. Click “Advanced Policies”.
  4. Check all nodes are checked in the “Possible Owners” box.
  5. Repeat 1-4 on all disks in the “Available Storage” group.

Once completed, you should be able to use the cluster command above to move the resources over.

  1. A post will be forth coming on that day of hell