My storage appliance has no record of any problems at that time, and I can't find any other possible reasons apart from a problem within the cluster.Īll six nodes are running up to date Server 2012 R2, and are Managed by SCVMM 2012 R2 running off a virtual machine hosted by another cluster. I found some errors in a couple event logs that show it seems the CSV failed but I can't find any indication as Yesterday in the evening when no one was working it seems like a bunch of VMs went down. So, we've been having issues with one of our clusters. Can I change this?īinding order of interfaces is the same on both boxes but maybe I did that after I created the cluster, not sure. I would like for the cluster network to be using the management interface on both cluster node members so as not to interfere with iSCSI traffic. I have restricted the iSCSI traffic to only use the one interface on each cluster node but I noticed that one of the cluster networks is connecting the management interface on one cluster node member with the iSCSI interface on the other cluster node member. Basically if I segregate it I wouldn't be able access the shared storage itself for any kind of management or maintenance tasks. The iSCSI interfaces have to be on same subnet as management interfaces due to limitations in the shared storage. In addition to a couple network interfaces devoted to VM traffic each node has: There are two nodes, running Server 2012. This cluster has been up and working for maybe a year and a half the way it is. Please help on this as we are stuck with this issue. we have removed its A record from DNS and replaced with Cname of the same name, but theĬomputer object is still present in the AD". Please note: the "Alias2" which we are using was a computer added to domain earlier, which is shutdown now as the shares are migrated to the new server. Logon Failure: the target account name is incorrect." contact the administrator of this server to find out if you have access permissions. you might not have the permission to use this network resource. we get an error while trying to open the shares from windows 2003 server:
#Event id 1146 microsoft windows failover clustering tools plus#
My next step was to connect computer management to the cluster virtual server name (NOCFS4) and through the System Tools | Shared Folders | All Tasks | Configure Shadow Copies it shows me the correct number of shares on the SMB cluster disk plus
Now historically I've enabled shadow copies through computer management but I want to ensure the shadow copies are cluster aware so in the Failover Cluster Manager I open Storage | Disks and right click the SMB cluster disk and click the Shadow Copies tab.įrom the tab I can Enable shadow copies, this sounds like what I'm looking for, unfortunately it does not give me an option to choose a disk/volume to store my shadow copy data, so this can't be right. I created a second cluster disk, assigned it to the same resources as the SMB clustered disk. I'd like to enable shadow copies for this shared disk but want to store the shadow copy data on its own shared diskĪs per shadow copy best practices (at least on non-clustered file servers). I've inherited a two node physical 2012 R2 file server cluster that contains a few SMB shares on a single clustered disk.