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

Error validating cluster computer resource name (Server 2016 Datacenter Cluster)

January 27, 2017, 11:44 am
$
0
0

    An error occurred while executing the test.
    The operation has failed. An error occurred while checking the Active Directory organizational unit for the cluster name resource.

    The parameter is incorrect

    Interesting enough the cluster name was created successfully in the Computers OU and the cluster can be taken offline and brought back online with no problem. The DNS entry is correct and the cluster name pings to the correct IP.  Changing the name of the cluster will update the cluster computer name in AD with no errors.


↧
Search

S2D quorum question

October 16, 2019, 3:58 am
$
0
0

Hi All

I´d truly appreciate your help to clarify the quorum operative in an S2D environment. I´ve read a bunch about Cluster and pool quorum, I know how these two quorum works, but I dont clearly see which one applies for Storage spaces Direct.

Quorum scheme should apply , so every disk should have a vote, and the owner should have another.

But I see a failover cluster supporing this S2d cluster, and this leevrages a File Witness (for example)  

Which one takes effect?

Best Regards

↧
↧

Error validating cluster computer resource name (Server 2016 Datacenter Cluster)

January 27, 2017, 11:44 am
$
0
0

    An error occurred while executing the test.
    The operation has failed. An error occurred while checking the Active Directory organizational unit for the cluster name resource.

    The parameter is incorrect

    Interesting enough the cluster name was created successfully in the Computers OU and the cluster can be taken offline and brought back online with no problem. The DNS entry is correct and the cluster name pings to the correct IP.  Changing the name of the cluster will update the cluster computer name in AD with no errors.


↧

When we fail-over from Node1 to Node2. fail-over cluster manager shows Node2 as down. but SQL cluster services are running fine

October 13, 2019, 10:31 pm
$
0
0

When we  fail-over from Node1 to Node2. fail-over cluster manager shows Node2 as down.

but SQL cluster services are running fine. It is happening on windows server 2012 R2 operating system.

Once I restart the cluster services in services.msc. It will up and join in the cluster.

Please check and help on this


↧

Precarious Situtaion Hyper-V Guest O/S

October 15, 2019, 11:47 am
$
0
0

I have 22 Virtual Machines each have their own LUN and are clustered amongst 4 nodes

Recently there was a power failure and we had to reboot the hosts

Now the VMs couldn't start because the DRIVE LETTER was not assigned and the VM was sitting on the DRIVE which went down

I had to manually go and assign a drive letter from diskmgmt.msc to make it all work

Figuring it which drive letter was assigned to which VM was a challenge since the config was a UNICODE file

How can I prevent this situation in future????

Thanks

SV

↧
↧

Can we configure Windows Failover Clustering without Central Storage(iSCSI)

October 16, 2019, 3:50 am
$
0
0

Hi,

I am completely new to Windows Server Failover Clustering subject, i have few doubts please clarify me.

I setup a Virtual lab with a DC+iSCSI installed and 2 File Server Nodes, configured Failover Clustering at both the nodes and verified the working.

When i shutdown the 1st Node dynamically the 2nd Node takes place, here my question is cant we create a Failover Cluster for the Existing File Server share folder??? instead have to configure SAN(iSCSI) for storage here both the nodes HDD space goes unused when all the data gets save in that SAN storage.

The same for SQL Failover too, when we have SQL DB server running in a server when i install Failover Clustering again on the same server for data storage have to select SAN, here the failover clustering only helps in keeping the Server Roles up and running, what will happen when Storage SAN device goes down??

I can understand SAN(iSCSI) is required such that both the Nodes get access to the storage device only then when one goes down 2nd one act behalf of that and takes the request to SAN server.

Any help please.

Mohammed...

↧

Unable to migrate machines within Failover Cluster Manager

August 10, 2017, 3:07 am
$
0
0

We have 4 physical servers which are all clustered. When I try to migrate a VM from one host to another I get the following error:

event id 1069 - Microsoft windows failover clustering
the error code was 0x775 the reference account is currently locked out and may not be logged onto.

The virtual machine then either goes directly into a failed state or tries to move to another server before going into a failed state. The only way to get it back online is to migrate it back to the original host.

I have noticed that the hosts do not all have access to the all of the volumes within cluster storage and it is only when I migrate the disk to a different host am I then able to access it from that host. If I try to access a volume hosted on host 1 from host 1 I can access it fine but if I try to access that same volume from host 2 I get an error stating that the account is locked out.

This has only stated causing problems in the last week and no permissions have changed to any of the volumes nor have any updates been applied to the system.

Thanks

↧

Switch Embedded Teaming

October 20, 2019, 7:38 pm
$
0
0
I am creating a new storage spaces direct cluster on server 2019 to replace an existing 2016 cluster.  I am using dual port Mellanox x-5 cards after adding the physical NICs to the SET switch I create the virtual NICs for hyper-v after adding the vnics the server reports their connection speed as 10 gigabits which is the speed of the physical links but on my 2016 storage spaces direct cluster the virtual NICs report a connection speed of 20 gigabits per second which would be the aggregate speed of the two 10 gigabit links.  What I am trying to find out is what the virtual NICs are supposed to report their connection speed as the single physical links or the total of all the links in the virtual switch set.  I can’t seems to find an answer of what the correct answer is in my searching.  I want to make sure I am not missing a set somewhere.  Can anyone shed some light on what should the virtual network cards report their speed as?
↧
Search

Error applying Replication Configuration Windows Server 2019 Hyper-V Replica Broker

August 9, 2019, 2:48 am
$
0
0

Hello,

Recently we started replacing our Windows Server 2016 Hyper-V Clusters for Server 2019. On each cluster we have a Hyper-V Replica broker that allows replication from any authenticated server and stores the Replica Files to a default location of one of the Cluster Shared Volumes.

With WS2019 we run into the issue where we get an error applying the Replication Configuration settings. The error is as follows:
Error applying Replication Configuration changes. Unable to open specified location for replication storage. Failed to add authorization entry. Unable to open specified location to store Replica files 'C:\ClusterStorage\volume1\'. Error: 0x80070057 (One or more arguments are invalid).

When we target the default location to a CSV where the owner node is the same as the owner node for the Broker role we don't get this error. However I don't expect this to work in production (moving roles to other nodes).

Did anyone ran into the same issue, and what might be a solution for this? Did anything changed between WS2016 & WS2019 what might cause this?

Kind regards,

Malcolm

↧
↧

Howto get a clustered MSDCT in Azure on Windows Server 2019 with S2D to function

March 26, 2019, 1:02 am
$
0
0

I've been pulling my hair for the last few days trying to get a FCI working with SQL Server and MSDTC, no matter what I try I can't get the MSDTC role to get online.

I've followed the instructions here: https://www.ryanjadams.com/2018/07/sql-server-failover-cluster-instance-azure-msdtc/

Current setup:
- Domain joined servers (ADDS)
- Two CSV (one for SQL, one for DTC) running on S2D (2 data disks per server = 4 disks in total)
- Windows Server 2019 Datacenter with latest updates applied
- SQL Server 2016 SP2 and latest CU
- Standard IP's (one NIC per server) and a Standard load balancer for the VM's
- Cloud witness for quorum
- Static ip addresses for all servers and FCI (cluster and roles)
- Pre-staged DNS records allowing authenticated users to update the records
- Running install/configuration with domain admin account
- Created the FC using the ManagementPointNetworkType = Singleton
- Allowed DTC, COM+ Network Access, Network Discovery, File and Printer Sharing plus the SQL port in Firewall
- Configured DTC to allow all options and tested different auth levels

All other settings are made according to the video Ryan posted but as soon as I set the static ip for the DTC role the resource fails and I can't get it started.

Anyone know what I'm missing? Has anyone else successfully configured a similar setup in Azure?

regards
/andreas

↧

Cluster Aware Update

October 2, 2019, 5:29 am
$
0
0

Hi,

I have Windows Server 2012 R2 Cluster having 3 nodes and 15 to 15 VMs over Hyper-V Cluster, Normally for Windows update we use local WSUS. Firstly we download update on each cluster machine, install updates and reboot if required and repeat same procedure step by step for each cluster node.

Can i use CLUSTER AWARE UPDATE mechanism to update my Cluster Nodes, please note that i install security updates, update roll-ups and etc.



Please comments  



↧

2012 R2 Scale-Out File Server Performance Issue

August 9, 2019, 11:27 am
$
0
0

I'm implementing a product called AppLayering by Citrix in a VMware environment. It creates a unique .vhd for each piece of software you install and want to deploy to end users. We created a Scale-Out File Server for the share so that we could have 100% up time from crashes and updates/reboots. The end user machines mount the .vhds at login; usually anywhere from 5-15 of these .vhds which range from 1Gb to 12GB in size.


Now that I'm increasing the amount of machines accessing this share, sometimes I experience a very long delay, as much as 6 minutes, before the layers are mounted. They usually mount within seconds. However, it's not consistently worse the more machines that are logged in, rarely it's still instant, but it does seem to get worse in general the more machines are mounting these layers.


The only performance settings I've tried to tinker with is the MaxThreadsPerQueue from 20 to 64. This reg entry was not in the registry by default, I had to make it myself, so I'm not sure if that means anything. Also not sure if 64 is even a good number to change it to either, just shooting in the dark here, any help would be much appreciated!


Darin

↧

AlwaysOn WSFC 2016 CNO was moved

October 29, 2019, 7:35 am
$
0
0

Hi All,
I have SQL Server 2016 (EE) with AlwaysOn configured in my environment. During a recent maintenance window I was updating IP Addresses/Names of resources in my WSFC and as a result the CNO was moved from under the Cluster Core Resources to being listed as a resource under AG Name as if it was the listener. This caused this one particular AG to then use the CNO as if it were the listener and made the AG failover to the Synchronous replica as the primary. Not sure how to get the CNO back listed under the Cluster Core Resources and removed from AG w/o breaking my WSFC along with the other AG's. CNO is circled in red below. Any help would be greatly appreciated

Listed under the Roles is the name of each AG. The bottom of screen provides more details on each AG. However this one particular AG has 2 resources listed under the Server Name. 1 is the AG Listener and the other resource is the (CNO) cluster named object. Not sure how the cno got included as AG Server Name Resource but i need to remove CNO from AG and get it back listed under Cluster Core resources

Listed under Roles is the name of each AG. The bottom half of screen provides additional details for each AG Role. This particular role has 2 resources listed under Server Name 1 is the AG Listener and the other is the (CNO) Cluster Named Object

KrisT_SQL


↧
↧

NLB Cluser add host | Error: The RPC is unavailable on the specified computer

October 22, 2019, 10:03 pm
$
0
0

Hi,

I have facing problem adding host in NLB Cluster. it shows error: The RPC is unavailable on the specified computer.

1. account is administrator.

2. File and printer sharing is enabled.

3. DNS record resolving and ping each other.

4. 2 NIC card.

5. cluster method "Multicast".

Please give suggestion, how to solve the problem.



↧

Drain role Failed

March 10, 2019, 4:01 am
$
0
0

We have three Node N-1, N-2, N-3. I drain role from N-2 and there10 VM's Moved out of 14. 4 VM are not moving getting error . Tried to move manually but the error same. Please assists All the Node in are WIN-2012 R2

Error Message : "operation did not complete on resource virtual machine live migration"

↧
Search

Failover cluster quorum problem

October 24, 2019, 1:07 pm
$
0
0

Hi all. I´v gato a Win server 2016 failover cluser with a File Witness reporting no error or warning on "test failover cluster Wizard"

However, when testing one node failure, Clsuter Stopped (And S2D running upon this also with this error:

event 1564,  File Share Witness Resource failed to arbitrate for the share \\xxx\xxx. Pleasse ensure its accesible.

I´ve checked and I can access with no proble to this share from both hosts. REplacing the File Witness solves the problem, But i Got no trust in this quorum anymore. Is there a way to check Witness access from a faioover cluster?  somehow like a "ping"

Regards 

↧

Hyper-V Cluster 2016

October 28, 2019, 8:34 am
$
0
0

Hello,

I'm installing new 2 node Hyper-V Cluster 2016 all up and running 

1. I have few VMs running under Hyper-V manager.

2. Trying to make the VMs highly available.

3. I'm able to perform the following task

Under the Hyper-V Cluster Manger I select Roles, Configure Role, Select Virtual Michine, I select the VM and it runs without any problem the VM is now High Availability.

Now The problem is when I do a second VM  

I repeat the same steps and it doesn't created an new VM it creates a group that I can't manage 

can't do live migrate I'm attaching 2 images 

fist image showing first VM and second showing to VMs on my don't know if this is a 2016 setting


↧
↧

S2D verification

October 28, 2019, 8:30 pm
$
0
0

quick overview. 

I have had a 4 node cluster working on 2016 for a couple years as a learning project. during that time my friends also played with it adding around 40 vms. the whole thing slowed to a crawl with even clicking on a start menu taking around 2 minutes to respond. I decided at add some SSD's as it was all 15K disks before but was told if I enabled s2d with no cache there is no supported method for adding cache.

I destroyed the disk and pool and upgraded all 4 nodes to 2019. disabled and re-enabled S2d and built a pool. tried to add a disk but the Gui is useless. power-shell'd a small disk then expand to proper size but I cant tell if I am properly caching to SSDs or not. is there any way to know? my SSDs are showing as journaling which is a good sign but I don't want to move any VMs back till I know my storage is good.

setup:

4 x dell r710s with dual e5-2697's

1 146gb 15k OS drive

5 146gb 15K storage drives

2 200GB industrail SSDs for cache

future setup

I have 2 more nodes with same hardrive/ssd setup but I want to make  nodes work before adding 2 more.


↧

Cluster name pointing to Passive node instead of active node

October 30, 2019, 5:40 am
$
0
0

Hi!

I have a Windows Server 2008 R2 two node cluster.

Cluster name:   CLUSM00

Active node:      CLUSM001

Passive node:   CLUSM002

There are a number of SQL instances on the Active node. When I rdp to the clustername it logs onto the passive node... This is causing havoc with the SQL backups (As they point to the clustername).

Any Idea how to make the clustername point to the active node?

Thanks,

Zoe

↧

Migrate Failover cluster role SQL server to new cluster shared volume (server 2019 - MSSQL 2017)

November 4, 2019, 11:54 pm
$
0
0

We have a 2-node failover cluster (windows server 2019) with iscsi cluster shared volume and on the cluster a SQL server 2017 role is running. We now have to migrate to our new storage. A new cluster shared volume is already configured on the failover cluster.

Searching the Internet for a migration guide the only thing I can find is rename the driveletter, but in our configuration we have no driveletters. 

Can I just copy the data to the new CSV and rename the volume name in de ClusterStorage folder?



↧
Viewing all 2306 articles
Browse latest View live
Search