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

Windows 2012 R2 rolling upgrade to 2016 file server

$
0
0

Hi Folks,

    I am not even sure is this fully supported by Microsoft .  I am doing  POC for this one. Sharing with the rest of you of what I have out found also to spare you some time of troubleshooting.

1. Adding 2016 node must be done in Windows 2016 Failover clustering manager.  Failing to do so cause the cluster to go offline.

2.In mixed mode ironically, configuring the file server role in Windows 2016 Failover clustering manager will not work .  I need to do it in Windows 2012 node for it to work.

3. At this point everything seems ok. Both Cluster  and Client Access Point are up.

4. Problem arises when I want that 2016 node to take ownership of the File server role (need to do this as I want to evict 2012 node one by one). The File server role immediately gone down when I do  this.

Troubleshooting steps taken:

1. Delete the Virtual name computer object and create the new one.

Any help and tips will be appreciated. Thank you.



Multiple SQL Cluster (2008, 2012, 2016) on a Single Windows Cluster

$
0
0

Hi Experts,

Can I have multiple SQL Cluster configured on a single environment (Windows Cluster?

For example - I have a 5 Node Windows 2012 R2 Windows Failover Cluster on which I want to configure 2 nodes to run as SQL 2008 Cluster, 4 nodes as SQL 2012 Cluster & 2 Nodes with 2016 Cluster. 

The combination of nodes can be in any number (2 - SQL 2012, 4 -  SQL 2008 or 5 - SQL 2016) but underlying I have only 5 nodes that will form the cluster. So, a single CNO (of 5 nodes) under which there will be multiple SQL Clusters (of 2, 3, 4 or 5 Nodes).

Is that possible? Above all, is that a recommended & supported scenario?

Thanks!

Setting up Storage for Clustering

$
0
0

We have 3 Dell servers we are trying to put into a cluster, and a 4th machine will be added later (VM). My issue now is I do not know how to set up the storage on the machines PRIOR to creating the Cluster so that the disks will be recognized as usable by the cluster. Currently when I use Cluster Manager and hit storage>right click disks>add disk, I get an error saying "No disks suitable for cluster disks were found. For diagnostic info about disks available to the cluster, use the Validate a Configuration Wizard to run Storage Tests." 

So I checked the validation test and this is what I see (copy and pasted from validation test):

    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.

Microsoft Cluster issues

$
0
0

Hi All,

I am trying to move a node from one node to another using Move-ClusterGroup, it moves cluster group from active node to passive node but after few seconds it is coming back to the previous node.

$cg=(Get-ClusterGRoup).Name|Select-First1

Move-ClusterGroup "$cg" -Node $onode

Are there any reasons for this behavior? and how it can be fixed.

Thanks in advance

Roger

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

$
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.


Set-ClusterLog Powershell Problem

$
0
0

I'm working on my first Hyper-V cluster on Server 2016. Going through the validation, I have a warning about cluster log size less than 1536.  So I search how to increase that and find: https://docs.microsoft.com/en-us/powershell/module/failoverclusters/set-clusterlog?view=win10-ps

However, when running powershell on the hosts, either as admin or not, and running:

Set-ClusterLog -Size 2048

All I get is:

PS C:\Windows\system32> Set-ClusterLog -Size 2048
Set-ClusterLog : Unable to save property changes for 'HV-Cluster1'.
    The data is invalid
At line:1 char:1
+ Set-ClusterLog -Size 2048
+ ~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Set-ClusterLog], ClusterCmdletException
    + FullyQualifiedErrorId : Set-ClusterLog,Microsoft.FailoverClusters.PowerShell.SetClusterLogCommand

Any ideas why am I unable to set this?

Thank you.

SQL Server Virtual Machine Live Migration Too Slow

$
0
0

Hi, I have a two node, Hyper-V Cluster with about a dozen VMs. As time went by migrating between nodes have slowed. Specifically a SQL Server with about 300 GB disk takes about four minutes to move from one node two the other, and during the process I see it's status as "shutting down" making it offline for a noticeable while.

The servers are Dell PowerEdge 530s with a Compellent (Dell) SC2020 with low latency. I recently connect to 10 GB NIS together peer to peer as a cluster only network in hopes to reduce migration time. It did not seem to make any difference.

Anyone have ideas on why the migration is slow and how to speed it up?

Thanks,

Ken


Ken

Storage Space Direct - Storage Jobs taking too long

$
0
0

Hi,

I have four node S2D cluster with 2019 OS. This is lab environment with SSD+HDD disks and 10Gbps network. Cluster is working fine, I have great performances but there is one issue that bothers me.

Every time I patch nodes, and I restart one of the nodes I have to wait for Storage Jobs to finish (so that data is synced). I know that I have to wait this out and I monitor this with get-storagejob command. When jobs finish, I continue updating other server nodes. What bothers me is time I have to wait for these jobs to finish. They can take more than 60-80min. 

Is there any way to speed this process up? I see that network and disks are not utilized fully when storage jobs are being done. I found online that this is intentionally throttled by Microsoft not to mess with VM performances. However, since this is Lab environment, I would love to speed this process up if possible, because in this way, patching takes to much time...

BR,

Soko


Windows 2016 GPO settings

$
0
0
I've been searching and just can't come up with much. Is there a site with what group policies need to be set? I'm by far an expert in knowing all these settings. I use the IRS SCSEM for Windows Server 2016 and it blocks failover clustering. I was hoping to get pointed in the right direction to fix this problem. Thx

SMB Signing breaks CSV access cross-node

$
0
0

Hey all, couldn't find an article that answers my problem, so starting my own :).
Hopefully I put in enough detail.

Server 2012 R2 Hyper-V Failover Cluster environment.
2 nodes. 1 SAN via SAS.
Disks added as CSV. Hyper-V config and vhds on CSVs.
Each node has 12 NICs.
NIC 1 - Mgmt - Gateway IP, DNS IP - 192.168.0.X/24
NIC 2 - Live Migration - IP only, no Gateway, no DNS - 10.20.30.X/24
NIC 3 to 10 - Windows Teamed Interface - LACP on Switch, added as Virtual Switch, External network, does not share mgmt
NIC 12 - DMZ - added as Virtual Switch, External network, does not share mgmt

Everything is fine. Cluster works, live migration works.

Recently we're going through a security exercise, operating Tenable.io, and remediating results found.
One of them is SMB Signing. I have been enabing the Group Policy "Microsoft network server: Digitally sign communications (always)" across various servers, testing along the way.

Until I apply this to my nodes. My CSVs don't appear to like it. After a few days, when trying to access a CSV in C:\ClusterStorage that is owned by another node, I can't see the Space used, and when trying to access it, I get "you have been denied permission to access this folder".
Removing "Microsoft network server: Digitally sign communications (always)" on both instantly restores this communication.

After googling around, I have been witnessing a few Event Log errors in SMBClient, Event 30803 and 31010, but I'm not yet sure if it's related. I am still trying to monitor it without the policy change. This is an example:

[Event ID 30803]

The network connection failed.

Error: {Device Timeout}
The specified I/O operation on %hs was not completed before the time-out period expired.

Server name: fe80::e0a9:e45:5b2b:f594%25
Server address: 10.20.30.2:445
Connection type: Wsk

Guidance:
This indicates a problem with the underlying network or transport, such as with TCP/IP, and not with SMB. A firewall that blocks port 445 or 5445 can also cause this issue.

[Event ID 31010]

The SMB client failed to connect to the share.

Error: {Access Denied}
A process has requested access to an object, but has not been granted those access rights.

Path: \fe80::e0a9:e45:5b2b:f594%25\454b7f2d-4e6c-4332-ae29-5e4befc5ce5b-135266304$

So what am I missing? Is it something to do with SMB Signing trying to verify an identity, and CSVs are using SMB across the Live Migration network, 10.20.30.2, but these errors are showing IPv6 address as a server name?

Adding node to cluster that is on different vlan

$
0
0
I am trying to add a node to my cluster that is located in a different vlan. I have created some firewall rules to allow communication, they are: UDP 3343, 137, random port between 1024-65535 and Random port between 49152-65535 AND TCP 3343, 135. Am I missing any ports, as I am still unable to add the node to the cluster with message saying, "The node cannot be contacted. Ensure that the node is powered on and is connected to the network." I can confirm the server is up and running and connected to the network.

Move-ClusterSetVM command in Server 2019

$
0
0

Hi there,

I am currently setting up a lab to test out cluster sets in Server 2019 by following https://docs.microsoft.com/en-us/windows-server/storage/storage-spaces/Cluster-Sets

Right now I am stuck on the step for testing out live migrate between cluster sets by running the command Move-ClusterSetVM. The example command shown was -

Move-ClusterSetVM -CimSession CSMASTER -VMName CSVM1 -ClusterName CLUSTER3

But -ClusterName is not even a valid parameter. There is another parameter called -Node, but when I tried to specify a node on a different cluster set, all I got was an error saying the move encountered a terminal failure.

So has anyone managed to get live migration working for cluster sets?

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

$
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

Microsoft Network Load Balancing not working as expected

$
0
0
I wish to have a failover cluster for an IIS site in my domain.
I have configured the cluster on port 80, however only once the network of that specific node is down will the cluster detect that node is down.
If I stop the site through IIS manager that node is still considered healthy.
What am I doing wrong? Is this what do the product supposed to do? If not what other product can help me?

Microsoft Server 2008 Failover Cluster Error Event ID 1230

$
0
0
We are getting the following error, Event ID 1230. Cluster resource 'FileServer-(xxxx)(Cluster Disk 3)' (resource type", DLL "clusres.dll') either crashed or deadlocked. The Resource Hosting Subsystem (RHS) process will now attempt to terminate, and the resource will be marked to run in a separate monitor.

No RESRCMON.DMP was created, so I can't troubleshoot to find the dll causing the problem.

Suggestions anyone.

It seems to me once RHS blows up the cluster resouces also blow up; theses include a FSRM report, TSM (Tivoli Storage Manager) Client Acceptor, and TSM Scheduler Services.

New-Volume cmdlet does not create requested size volume.

$
0
0

Hello,

I don't know if this is the best forum for this as it is powershell, but it is a cluster volume I am creating with 2 VM's in Azure.

When I create a volume for DTC of 500MB, the volume actually gets created as 8GB. I would like to know why and what to do to fix this behavior.

Command I ran:

New-Volume -StoragePoolFriendlyName S2D* -FriendlyName VDiskDBDTC -FileSystem CSVFS_REFS -Size 500MB

Result:

DriveLetter FileSystemLabel FileSystem DriveType HealthStatus OperationalStatus SizeRemaining    Size
----------- --------------- ---------- --------- ------------ ----------------- -------------    ----
            VDiskDBDTC      CSVFS      Fixed     Healthy      OK                      7.21 GB 7.94 GB

Also, I tried to create it as 1GB and got the following:

PS C:\windows\system32> New-Volume -StoragePoolFriendlyName S2D* -FriendlyName VDiskDBDTC -FileSystem CSVFS_REFS -Size 1GB


DriveLetter FileSystemLabel FileSystem DriveType HealthStatus OperationalStatus SizeRemaining    Size
----------- --------------- ---------- --------- ------------ ----------------- -------------    ----
            VDiskDBDTC      CSVFS      Fixed     Healthy      OK                      7.21 GB 7.94 GB

The other volumes I created, of various sizes in GB, are the correct sizes. The help page for this command states that you can use MB when specifying size, so I don't know why it won't work correctly.

https://docs.microsoft.com/en-us/powershell/module/storage/new-volume?view=win10-ps

I also attempted this through the GUI, and got slightly different, but still incorrect, results. See screenshots below.

The attempt to create a 500MB virtual disk.

What Get-disk showed after the creation:

What the cluster GUI showed. Note the disk number, and the fact that I already have a disk 10. Wonder what problems THAT will cause. Also note that Powershell does not show a disk number. What's up with that?

Perhaps I have made mistakes in this creation. I only hope someone can point them out for me and help me correct the problem.

Thanks,
Chris




Failover Cluster Manager bug on Server 2019 after .NET 4.8 installed - unable to type more than two characters in to the IP fields

$
0
0

We ran into a nasty bug on Windows Server 2019 and I can't find any KB articles on it. It's really easy to replicate. 

1. Install Windows Server 2019 Standard with Desktop Experience from an ISO. 

2. Install Failover Cluster Services.

3. Create new cluster, on the 4th screen, add the current server name. This is what it shows:

cluster services working correctly before .NET 4.8 is installed

4. Install .NET 4.8 from an offline installer. (KB4486153) and reboot.

5. After the reboot, go back to the same screen of the same Create Cluster Wizard and now it looks different:

cluster services broken afte.NET 4.8 is installed - unable to put in a 3-digit IP

Now we are unable to type in a 3 digit IP in any of the octet fields. It accepts a maximum of two characters. 

Has anyone else encountered this? It should be really easy to reproduce. 

VMs located on one of CSV volumes stopped migrating on one of cluster nodes

$
0
0
We have a 3 node cluster Windows 2016 with many VMs on 3 CSV volumes. At one moment (I'm not sure when) VMs located on first CSV volume stoped to migrate (live and quick) to fist node (only to first node). 1st volume is still visible from 1st node. Cluster validation didn't show any problem.
In event log Microsoft-Windows-Hyper-V-VMMS/Admin on 1st node:
EventID:16300 
Cannot load a virtual machine configuration: The system cannot find file specified. (0x80070002) (Virtual machine ID ....)
EventID:21002
'VM name' Failed to create Planned Virtual Machine at migration destination:The system cannot find file specified. (0x80070002) (Virtual machine ID ....)

Any ideas how to fix this problem?

I would appreciate any help.  

Thanks.

How to expand vhdx disk VM on failover cluster

$
0
0

Hi,

I want to know the right way in order to expand a VHDX disk of a VM running on a failover cluster of 2 nodes. The nodes and the guest OS are running Windows Server 2012 R2. 

I know that is posible to expand it online (with the VM running) but when I open the VM settings configuration page from Hyper-V manager, it says "some settings cannot bemodified because the virtual machine wasrunning".

Thanks in advance.


Cristian L Ruiz

Error Code: 0x8007054f when rename a SQL Server client access point of a SQL Server cluster

$
0
0

I am getting  error 0x8007054f when renaming a Serve Name property of role 'SQL Server' using  Windows Fail over Cluster Manager tool.

Details below :

I have a Windows 2008 R2 Enterprise Edition 2-node cluster running SQL Sever 2008 R2; Lets call it as  SQLA (Node 1 and Node 2).

I built  a new Windows 2012 R2 Standard Edition 2-node cluster running SQL Sever 2012 ; Lets call it as  SQLB (Node 3 and Node 4).

My goal is to rename SQLA as SQLOLD and SQLB as SQLA.

I made sure I have necessary permissions to rename the cluster by first renaming SQLB asSQLBNew and renamed it back to SQLB.


For the intended change  I performed the below steps in that order-

  • I first renamed SQLA as SQLOLD and assigned a different IP; verified I was able to connect as SQLOLD and execute SQL queries against SQLOLD
  • As an additional precaution, I brought the SQL Services on SQLOLD offline
  • I RDPed into active node of SQL B( Node 3) , using Failover Cluster Manger attempted to rename  the 'Server Name' (Client Access point)  of role 'SQL Server' to SQLA.

The renaming failed with  error 0x8007054f. Please see the attached screenshots of the error. Where can I look for the root cause of this error ?





ARASKAS

Viewing all 5654 articles
Browse latest View live


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