Quantcast
Channel: High Availability (Clustering) forum
Viewing all 3614 articles
Browse latest View live

Hyper-V 2012 R2 - Cannot bring CSV online

$
0
0

All -

Thanks for making this great forum available to us!

I have a 2-node Windows Server 2012 R2 Hyper-V Failover Cluster.  Node 2 of the cluster experienced an unexpected power outage.  After the outage, the two Cluster Shared Volumes that are part of the Failover Cluster will not come online.

After looking at the Event Logs and Cluster logs, I believe the issue is that the Cluster cannot locate the CNO since Active Directory is fully virtualized and (obviously) offline.

Is there a way to force these CSVs to come back online without an AD to talk to?  I read that the AD dependency was removed in 2012.  Or, based on the information given, could this be caused by something else?

I'll be glad to run any commands and provide output back to the thread.

Thanks for your help!


Syst3m32 https://www.sysadminsoup.com


Problem When Adding a Node in a Failover Cluster

$
0
0

Hello, we have a Failover Cluster, which so far only had Windows Server 2012 R2 Standard . We are trying to add another node, which is not R2, that is, it is Windows Server 2012 Standard, but we are not able to add the node in question in the cluster.
The errors that occur are attached.

Has anyone ever had this problem? Would they know how to solve it?

Thanks.

In "Cluster Events" only exist this error:

"Cluster node SEI-25 has been evicted from the failover cluster."

Change s2d cluster ip and subnet

$
0
0

Hi,

I need to migrate a few S2D 4-node clusters to another subnet.  Is there any good documentation or steps to best do this?

thx

Robert


Robert

Hyper V 2016 - Failover clustering - VMs not powering on

$
0
0

Hi,

I have two 2016 Hyper V servers configured in a failover cluster, Validation report is good, VMs live migrate between both nodes, file share witness configured, 

When we power off one host the VMs migrate to the other host however they never power on

If we manually power on they succeed. Can't figure out if this is a settings or misconfig 

Thanks

Rob


Create Failover Cluster is failing in Server 2016

$
0
0

hello 

I try to Create Failover Cluster  in Server 2016 datacenter, the validation test pass all , but i got error when i create the cluster 

Check whether the computer object cluster for node1.mydomain.org exists in the domain. Domain controller \\mydc.mydomain.org. More data is available.
Bind to domain controller . More data is available.
Operation failed, attempting cleanup.
An error occurred while creating the cluster and the nodes will be cleaned up. Please wait...
An error occurred while creating the cluster and the nodes will be cleaned up. Please wait...
There was an error cleaning up the cluster nodes. Use Clear-ClusterNode to manually clean up the nodes.
An error occurred while creating the cluster.
An error occurred creating cluster 'cluster'.

i try prestage CNO on AD  

but still same error,

my DC server is 2008

please any help?


Alternatives to Guest Clustering?

$
0
0

Hello,

We currently use Guest Clustering for a File Server and while its great when we don't have to do maintenance on it but when you have to perform maintenance such as Live Storage Migrations or expanding storage its not so great. Does anyone do anything differently for File Servers? currently this is being used to serve up a Share for IIS Shared Configuration and other applications. We thought SOFS might be able to help but it also depends on having the Shared Disks.

Test-Clusterhealth

$
0
0

We have setup a 6 Node Cluster using Iwarp configuration, QL41262 25GB Network Adapters. I have enabled RDMA everywhere I can see, i did this via the Dell setup guide.

Running the Test-clusterhealth command I get the below results. 

I'm really struggling with the RDMA failures and now I'm getting failures on SMB. Saying disconnects, I'm having multiple reports of lagging and performance issues in guest VMs

PS C:\Scripts> .\Test-Clusterhealth.ps1
Detected RDMA adapters: will require RDMA
******************** Basic Health Checks (3.6s)
All cluster nodes Up
Cluster node uptime:

PSComputerName Uptime
-------------- ------
S2D-NODE01     30d:00h:48m.50s
S2D-NODE02     0d:19h:47m.54s
S2D-NODE03     40d:16h:21m.24s
S2D-NODE04     0d:22h:14m.54s
S2D-NODE05     0d:02h:53m.07s
S2D-NODE06     2d:15h:45m.03s


Clustered storage subsystem Healthy
All pools Healthy
******************** Clusport Device Symmetry Check (2.1s)
********** Total
Pass with 72 per node
********** Disk Type
Pass with 60 per node
********** Solid/Non-Rotational Media
Pass with 12 per node
********** Enclosure Type
Pass with 6 per node
********** Virtual
Pass with none on any node
******************** Enclosure View Symmetry Check (4.1s)
********** Total
Pass with 6 per node
******************** Operational Issues and Storage Jobs (116.2s)
No storage rebuild or regeneration jobs are active
******************** Physical Disk Health (2.2s)
All physical disks are in normal auto-select or journal state
******************** Physical Disk View Symmetry Check (4.1s)
********** Total
Pass with 60 per node
******************** RDMA Adapter IP Check (8.9s)
*************** RDMA Adapter IP Check
********** Total
Pass with none on any node
*************** RDMA Adapter (Virtual) IP Check
********** Total
Fail

Count Name
----- ----
    6 S2D-NODE01
    4 S2D-NODE02
    4 S2D-NODE03
    6 S2D-NODE04
    6 S2D-NODE05
    7 S2D-NODE06


*************** RDMA Adapter (Physical) IP Check
********** Total
Pass with none on any node
******************** RDMA Adapters Symmetry Check (3.4s)
********** Total
Fail

Count Name
----- ----
    5 S2D-NODE01
    4 S2D-NODE02
    4 S2D-NODE03
    5 S2D-NODE04
    5 S2D-NODE05
    5 S2D-NODE06


********** Operational
Fail

Count Name
----- ----
    5 S2D-NODE01
    4 S2D-NODE02
    4 S2D-NODE03
    5 S2D-NODE04
    5 S2D-NODE05
    5 S2D-NODE06


********** Up
Fail

Count Name
----- ----
    5 S2D-NODE01
    4 S2D-NODE02
    4 S2D-NODE03
    5 S2D-NODE04
    5 S2D-NODE05
    5 S2D-NODE06


******************** SMB Connectivity Error Check - Connect Failures (2.4s)

PSComputerName RDMA Last5Min RDMA LastDay RDMA LastHour TCP Last5Min TCP LastDay TCP LastHour
-------------- ------------- ------------ ------------- ------------ ----------- ------------
S2D-NODE01                 0            0             0            0          20           0
S2D-NODE02                 0            0             0            0          10           0
S2D-NODE03                 0            0             0            0          13           0
S2D-NODE04                 0            0             0            0          12           0
S2D-NODE05                 0            0             0            0          10           0
S2D-NODE06                 0            0             0            0          14           0


******************** SMB Connectivity Error Check - Disconnect Failures (2.5s)
WARNING: the SMB Client is receiving RDMA disconnects. This is an error whose root"
         cause may be PFC/CoS misconfiguration (RoCE) on hosts or switches, physical"
         issues (ex: bad cable), switch or NIC firmware issues, and will lead to severely"
         degraded performance. Additional triage is included in other tests."

PSComputerName RDMA Last5Min RDMA LastDay RDMA LastHour TCP Last5Min TCP LastDay TCP LastHour
-------------- ------------- ------------ ------------- ------------ ----------- ------------
S2D-NODE01                 0           16             0            0           3           0
S2D-NODE02                 0           11             0            0          11           0
S2D-NODE03                 0           17             0            0           3           0
S2D-NODE04                 0            8             0            0           1           0
S2D-NODE05                 0           12             0            0          12           0
S2D-NODE06                 0           18             0            0           6           0


******************** SMB CSV Multichannel Symmetry Check (2.5s)
********** Total
Fail

Count Name
----- ----
   16 S2D-NODE01
   10 S2D-NODE02
   18 S2D-NODE03
   12 S2D-NODE04
    8 S2D-NODE05
   14 S2D-NODE06


********** RDMA Capable
Fail

Count Name
----- ----
   16 S2D-NODE01
   10 S2D-NODE02
   18 S2D-NODE03
   12 S2D-NODE04
    8 S2D-NODE05
   14 S2D-NODE06


********** Selected & Non-Failed
Fail

Count Name
----- ----
   16 S2D-NODE01
   10 S2D-NODE02
   18 S2D-NODE03
   12 S2D-NODE04
    8 S2D-NODE05
   14 S2D-NODE06


******************** SMB SBL Multichannel Symmetry Check (2.6s)
********** Total
Fail

Count Name
----- ----
   10 S2D-NODE01
   10 S2D-NODE02
   16 S2D-NODE03
   10 S2D-NODE04
   10 S2D-NODE05
   10 S2D-NODE06


********** RDMA Capable
Fail

Count Name
----- ----
   10 S2D-NODE01
   10 S2D-NODE02
   16 S2D-NODE03
   10 S2D-NODE04
   10 S2D-NODE05
   10 S2D-NODE06


********** Selected & Non-Failed
Fail

Count Name
----- ----
   10 S2D-NODE01
   10 S2D-NODE02
   16 S2D-NODE03
   10 S2D-NODE04
   10 S2D-NODE05
   10 S2D-NODE06


******************** Virtual Disk Health (2.1s)
All operational virtual disks Healthy
PS C:\Scripts>

votes on SQL Server AlwaysOn Availability groups based on WFCS

$
0
0

Hi,

In my lab environment I have 3 SQL Servers participating in Always On AG that based on WFCS,

I set a file share witness so i have 4 potential votes.

from what i understood, if there are 3 nodes and 1 file share, the file share's vote is not takes into account,
and only if 1 of the nodes fails, the cluster will reorgenize the vote system and give 1 vote to the file share and 2 to the other nodes that still alive...

my question is, when I've entered the Cluster Quorum Information in the AO AG Dashboard (in the ssms), I saw that there are 4 members, 3 nodes and 1 file share witness, but under the vote count I saw that all 4 members got 1 vote, so there is an even number of vote and it does not make any sense to me... how it is that there are odd number of nodes and the file share vote is taken into account?

illustration picture (imagine that there is a "file share witness" with 1 "vote count", additional to those 3 members):


Windows Server 2019 and Windows Server 2016 in Active-Passive approach (High Availability) or Fail-over Cluster

$
0
0
If Primary Server has Windows Server 2019 OS and Secondary Server has Windows Server 2016 OS, is it okay if they will be in a HA environment or they will be clustered? Since 2019 has the same functional level as 2016. What are the best practice for this situation? Thank you.

Always on Cluster Error

$
0
0

Hi;

I had 3 nodes Always on Cluster. The DRC node had a problem, so i had did evict node. After i added the DRC Cluster node to Domain again. After that i could add node to the windows cluster. As a result the cluster disk nodes can not online on the DRC server. The cluster disk resources can not online, too.

Thanks

Adding a third node to an existing cluster from a different subnet

$
0
0

Hi

We have an existing MS 2012R2 2 node cluster supporting a SQL Always On setup.    The existing two nodes sit in the same subnet as part of a standard cluster setup.  We want to add a third node to the cluster from a different network to provide HA.  I am trying to understand if it is possible to covert the existing cluster to a multi subnet cluster without an outage?

Thanks in advance 

ADAM (AD LDS) sync issue

$
0
0

Dear All

I am facing issue in syncing ADAM server. Syncing is started and has been running for 1 day now. In LDP.exe it also shows state "running". Log size is increase to around 12 GB now. My Question is that have you faced this issue and taking this much long time is normal with this size of log ? Another thing is using LDP i tried to find some users but no record found till now. I do not know will it give results when sync is complete or its not bringing anything at all that is why it is running and expanding the log while getting nothing from AD. 

SQL Cluster node not working

$
0
0

HI Team ,

My Server 2012 R2 SQL Cluster Servers Two Node ,

Problem : Server A D Drive unable online mode ( your reference below the screen short) quram Drive which server have D Drive Gone

Stuck on joining state

$
0
0

Hi guys i have 2 node and both went down due to some issue.

Before rebooting my node1 was the primary node and node2 was the secondary node.

My node1 was having issue rebooting but my node2 was fine upon rebooting.

However my node2 is not able to start up the cluster as i check the state is joining.

Please let me know if you need more information. 

Cluster shared storage issue

$
0
0

Hi

I have windows servers 2012 R2 cluster with 7 drive shared from SAN storage.

Now I am not able to open all 7 drives from each node as below error.

c:\ClusterStorage\Volume1 is not accessbile

the reference account is currently locked out and may not be logged on to.


windows server 2016 failover cluster virtual machine is in locked state

$
0
0

windows server 2016 failover cluster virtual machine is in locked state

please anyone provide solution:

Hyper-v Replication unfortunately stopped from that time onwards automatically checkpoint creating status showing 7%. i could not able to that VM.VM is showing in failover cluster status (locked). i could not able remove the checkpoint.   

Cluster IP keep switching

$
0
0

Dear All,

I have cluster node with 2 IPs, one active and the other one is passive. When i do NSLOOKUP i get the 2 IPs, when i ping the cluster name, then its pining the passive IP not the active IP, it should ping the active IP ( passive IP not pining - request time out). I did delete both A records in DNS then it worked fine, but after a while it went back to the passive IP again. What i need is when i ping the cluster note it must ping the active IP.

Thank you 

Not able to rebuild cluster, issue on disks ?

$
0
0

Hi all,

I have two Windows servers 2012 r2 (DB1A and DB1B) where a failover cluster + SQL Server Avalibility Groups used to work. But something went wrong (don't really know what, maybe an aggressive GPO) and the cluster was totally dead.

When I try to rebuild it, I get this kind of warning :

List Disks To Be Validated
Physical disk ab780ec8 is visible from only one node and will not be tested. Validation requires that the disk be visible from at least two nodes. The disk is reported as visible at node: DB1A
Physical disk ab780ec0 is visible from only one node and will not be tested. Validation requires that the disk be visible from at least two nodes. The disk is reported as visible at node: DB1A
No disks were found on which to perform cluster validation tests. To correct this, review the following possible causes:
* The disks are already clustered and currently Online in the cluster. When testing a working cluster, ensure that the disks that you want to test are Offline in the cluster.
* The disks are unsuitable for clustering. Boot volumes, system volumes, disks used for paging or dump files, etc., are examples of disks unsuitable for clustering.
* Review the "List Disks" test. Ensure that the disks you want to test are unmasked, that is, your masking or zoning does not prevent access to the disks. If the disks seem to be unmasked or zoned correctly but could not be tested, try restarting the servers before running the validation tests again.
* The cluster does not use shared storage. A cluster must use a hardware solution based either on shared storage or on replication between nodes. If your solution is based on replication between nodes, you do not need to rerun Storage tests. Instead, work with the provider of your replication solution to ensure that replicated copies of the cluster configuration database can be maintained across the nodes.
* The disks are Online in the cluster and are in maintenance mode.
No disks were found on which to perform cluster validation tests.

and when I open the Failover Cluster Manager, I can see the two nodes but can't see anything on the Roles folder, nor Disks.

Of course, SQL Server Availibility Groups is not possible :


The local node is not part of quorum and is therefore unable to process this operation. This may be due to one of the following reasons:
•   The local node is not able to communicate with the WSFC cluster.
•   No quorum set across the WSFC cluster.

I'm a bit lost. It would be great if someone could help.

Windows Server 2016 cluster system Failover Cluster Validation Report shows error on the CNO

$
0
0

Hi All,

I'm having an issue with my Windows Server 2016 cluster system.
it consists of 2 nodes, let say Node1 (showing as down) and Node2 (is up).

Node1 is ping-able to Node2 and vice versa, but not sure why it is showing as down.

The Fail-over Cluster Validation Report shows error only on the below CNO:

  • The cluster network name resource 'PRDSQL-CLUS01' has issues in the Active Directory. The account could have been disabled or deleted. It could also be because of a bad password. This might result in a degradation of functionality dependent on the cluster network name. Offline the cluster network name resource and run the repair action on it. 
    An error occurred while executing the test.
    The operation has failed. An error occurred while checking the state of the Active Directory object associated with the network name resource 'Cluster Name'.

    Access is denied
This is the error logged from the Failover Cluster Manager.

Event ID 1069

Cluster resource 'Cluster Name' of type 'Network Name' in clustered role 'Cluster Group' failed.Based on the failure policies for the resource and role, the cluster service may try to bring the resource online on this node or move the group to another node of the cluster and then restart it. Check the resource and group state using Failover Cluster Manager or the Get-ClusterResource Windows PowerShell cmdlet.

Event ID 1688
Cluster network name resource detected that the associated computer object in Active Directory was disabled and failed in its attempt to enable it. This may impact functionality that is dependent on Cluster network name authentication.Network Name: Cluster NameOrganizational Unit: Guidance:Enable the computer object for the network name in Active Directory.

The Virtual Cluster Frontend called PRDSQL-CLUS01is reporting it is disabled in Active Directory, as per the above error.
 
I have tried:

Taking the virtual endpoint offline and running a repair, but the errors state that “File not Found” and Error Displaying Cluster Information
Create a blank role, SQL and CAU are still working, it is only the front end failover cluster virtual network name AD account (CNO) that is having the issue.

Any help would be greatly appreciated.

Thanks,


/* Server Support Specialist */

windows HPC 2019 Pack Configuration

$
0
0

Hi,

We have plan to configure windows hpc pack in our lab with high end workstation installed. need help.  

Viewing all 3614 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>