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

Issue with adding a file share witness

January 9, 2017, 1:42 am
$
0
0

Hi,

I've a 2 SQL Servers clustered but no file share witness has been added to them, so I'm trying to add a file share witness now and I got the following error:

Configure Cluster Quorum Settings

Witness Type:
File Share Witness
Witness Resource:
\\nassrv\sql\Censusdbclusterwitness
Cluster Managed Voting:
Enabled

Errors

An error was encountered while modifying the quorum settings.
Your cluster quorum settings have not been changed.

There was an error configuring the file share witness '\\nassrv\sql'.

Unable to save property changes for 'File Share Witness'.

The user name or password is incorrect

Putting into considerations that the cluster hosts computer accounts have a full control permissions over the shared folder, also the Custer Virtual Object.

The shared folder on a separate host that can be accessed by the cluster hosts.

↧
Search

Stop and start cluster nodes on same time

January 25, 2017, 12:36 am
$
0
0
We have a cluster with 4 nodes and File Witness (5 votes) on same enclosure. We need turn off all nodes. Which is the best procedure to stop and start the cluster ??
↧
↧

High Availability Configuration is possible on Server 2016 Workstation

January 25, 2017, 12:56 am
$
0
0
We are planned to setup domain controller in hyper-v with High Availability. Is it possible to configure High Availability on Server 2016 Workstation. Is it necessary the nodes are in member server.  
↧

2016 S2D Cluster, SMB failover not working

January 9, 2017, 12:53 pm
$
0
0

Hi,

we have a 3-node 2016 S2D Cluster on Dell 730xd with 12x4TB SATA and 4x480GB SSD pools/tiers installed according to a guide by Lenovo. Everything clusterwise is working well, except if we have a SMB Share on a scale-out fileserver which is going offline when the node is rebooted.

Manual move works, it even works if we restart the node role again manually but if its online (pingable/open in explorer) and we reboot the owner node then its showing offline until the whole server is back. Shouldnt that be doing a failover that way ?

Its a 3 way mirror.

↧

server 2016 Rolling upgrade with regular file server roles

January 12, 2017, 3:48 am
$
0
0

I have a cluster with a rather important scale-out-file-server, consisting of just two nodes. Both nodes are running 2012 R2. Apart from the scale out, a couple of regular file server roles are hosted as well on this cluster (with MPIO on a SAS bus).

I'm trying to perform a rolling upgrade, which seems like an ideal feature to keep the SOFS running. At this point I've added a third node running server 2016 to the cluster. Going over to the server manager on srv-2016 and navigating to the "File and Storage Services" pane, I get a warning when I view the disks: 

Is there something else going wrong somewhere, or is this simply not supported by rolling upgrade?

Cheers,
Maarten

MaartenD

↧
↧

Can I configure fail-over cluster between 2012 R2 and 2016?

January 26, 2017, 2:05 am
$
0
0

Old Server install Windows Server 2012 R2. It is HyperV host.

I bought new server for HyperV high availability. I bought new Windows Server license too, it is Windows Server 2016 license.

So, Can I install Windows Server 2016 on new server and configure cluster with old server?

↧

NFS mounts

January 26, 2017, 12:30 pm
$
0
0

Does Microsoft support configuring 2012 R2 failover cluster using nfs mounts?

↧

Change Subnet mask in Windows 2012/SQL 2012 Always On Cluster

January 17, 2017, 7:08 am
$
0
0

Hello,

We have a three node Windows 2012 cluster and it has SQL 2012 Always on configured on it. Three nodes have incorrect subnet mask values and we would like to change it.

Can anyone please provide the steps to change the subnet mask values ? i saw some blogs and they mention to shutdown or take the cluster offline and change the values as below but the roles in the cluster will still have the old subnet mask value after changing the values using below steps ? I'm kind of confused on how to change and its affect on the whole cluster as this is production.

Any help would be appreciated. Thanks in advance. 

Steps to change IP address/Subnet mask:

  1. Go to Control Panel\All Control Panel Items\Network and Sharing Center\Change adapter settings\
  2. Right-click Local Area Connection, and then click Properties.
  3. In the Local Area Connection Properties dialog box, double-click Internet Protocol (TCP/IP).
  4. In the Internet Protocol (TCP/IP) Properties dialog box, in the IP address box, type the new address.
  5. In the Subnet mask box, type the subnet mask to 255.255.252.0

↧
Search

Storage spaces direct - STATUS_IO_TIMEOUT

December 26, 2016, 1:37 am
$
0
0

Hi Everyone,

I configured cluster of 4 Supermicro X10DRIservers to test storage spaces direct. Supermicro server configuration:

- 2 x Intel Xeon E5-2640v3 CPU
- 10 x 32GB 2133MHz DDR4 RAM
- 2 x SSD 400GB SATA Intel S3610
- 2 x HDD 2TB SATA Seagate ST2000NX0253
- 6 x SSD 800GB SATA Intel S3610
- Intel X520-DA2 E10G42BTDA Network adapter

All was fine, cluster and S2D were working without any problems. But after a month, I replaced Intel X520-DA2 E10G42BTDA Network adapter on Mellanox ConnectX-3 Pro Ethernet Adapter. After that, I started receiving Warnings in Cluster Events log:

"Cluster Shared Volume 'VD1' ('Cluster Virtual Disk (VD1)') has entered a paused state because of 'STATUS_IO_TIMEOUT(c00000b5)'. All I/O will temporarily be queued until a path to the volume is reestablished."

I checked health of physical disks - they fine, also I checked network and found I had about 500K Received Discarded Packets per server. Itlookspretty bad, but I'm not sure. Is it a problem? Orshould I continue my investigation?

↧
↧

How to Activate DR site when Preferredsite Goes Down

January 27, 2017, 11:21 am
$
0
0
We're testing the two site scenario where you have a primary and a DR site using the Site-aware FC. How do you bring up the DR site when the preferredsite goes down? I've tried using fq switch for the cluster service with no success. Is there another process to bring the cluster up on the DR site in 2016?
↧

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.


↧

Windows Hyper-V cluster goes down if one node is up

January 28, 2017, 10:15 am
$
0
0

Hi,We have a two node Hyper-V CSV Cluster, node 1 is down. As soon as this server comes up all cluster goes down. Currently all VMs are working on Node 2.

What possibly could be the issue?
 

↧

Windows 2012 R2 SQL Cluster Issue

January 21, 2017, 10:40 am
$
0
0

Hi,

I'm getting the below error in every 15 minutes on Windows 2012 R2 SQL cluster.

event id  1069

Cluster resource 'Cluster Disk 4' of type 'Physical Disk' 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 1558

The cluster service detected a problem with the witness resource. The witness resource will be failed over to another node within the cluster in an attempt to reestablish access to cluster configuration data

Server OS: Windows 2012 R2 Datacenter Edition

Cluster: SQL 2012 R2 failover Cluster

Platform: VMware

Cluster: Cluster across host.

Regards,

Hakim. B

Hakim.B Sr.System Administrator

↧
↧

Process to evict and replace node from windows failover cluster

January 23, 2017, 8:17 am
$
0
0

Hi Team,

We need to evict and remove 1 node from windows failover cluster , could anyone pls .point me or share any step by step article or document or steps to follow?

Basically we want to evict and introduce new node to the existing windows failover cluster. Its a 3 node cluster (2 nodes in primary and 1 node in DR site), we want to evict node 3 from DR site and replace it with new node. All nodes are VMWare VMs. Thanks.

↧

Cannot create checkpoint when shared vhdset (.vhds) is used by VM - 'not part of a checkpoint collection' error

December 9, 2016, 1:27 am
$
0
0

We are trying to deploy 'guest cluster' scenario over HyperV with shared disks set over SOFS. By design .vhds format should fully support backup feature.

All machines (HyperV, guest, SOFS) are installed with Windows Server 2016 Datacenter. Two HyperV virtual machines are configured to use shared disk in .vhds format (located on SOFS cluster formed of two nodes). SOFS cluster has a share configured for applications and HyperV uses \\sofs_server\share_name\disk.vhds path to SOFS remote storage). Guest cluster is configured with 'File server' role and 'Failover clustering' feature to form a guest cluster. There are two disks configured on each of guest cluster nodes: 1 - private system disk in .vhdx format (OS) and 2 - shared .vhds disk on SOFS.

While trying to make a checkpoint for guest machine, I get following error:

Cannot take checkpoint for 'guest-cluster-node0' because one or more sharable VHDX are attached and this is not part of a checkpoint collection.

Production checkpoints are enabled for VM + 'Create standard checkpoint if it's not possible to create a production checkpoint' option is set. All integration services (including backup) are enabled for VM.

When I delete .vhds disk of shared drive from SCSI controller of VM, checkpoints are created normally (for private OS disk).

It is not clear what is 'checkpoint collection' and how to add shared .vhds disk to this collection. Please advise.

Thanks.

↧
Search

Software Updates missing on Node B

January 31, 2017, 2:43 pm
$
0
0

Hello,

When running the cluster validation I have "Software Updates missing on Node B" Windows Server 2008 R2 Service Pack 1.

e.g.:

KB3087985 requested by the cluster validation but see below refused by the installation

KB3045645 seems to be only for Windows 7!!!

KB3020338 !!!

When trying to install  ie11-Windows6.1-kb3087985-  

it seems to be a conflict!!!

Any idea?

Thanks,Dom

Security / System Center Operations Manager 2012 / System Center Configuration Manager 2012 / SQL System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager





↧

Unable to configure server 2016 cluster aware updating.

February 1, 2017, 4:30 pm
$
0
0

Initially got a WinRM error when trying to set options in the CAU gui so ran test-causetup which reported the same errors after rule 11 below. It's also reporting several other failures though which are bogus. Rule 3 is giving an error saying PSRemoting is not enabled yet it is and I've even tried "enabling" it using -force. Rule 2 not positive about but know winrm is running and configured and firewall is off. Rule 11 is failing on the cluster name its not a server...

To test PSRemoting I ran this command on the other cluster node and it works BUT if you run it and target the same machine you are on it fails. This happens on both nodes and both nodes are giving all the same errors.

Invoke-Command -ComputerName 90vmhost5 -ScriptBlock { Get-ChildItem c:\ } -credential CM

PS C:\Windows\system32> Test-CauSetup


RuleId          : 1
Title           : The failover cluster must be available
State           : Started
Severity        : Info
FailedMachines  : {}
PercentComplete : 1

RuleId          : 1
Title           : The failover cluster must be available
State           : Succeeded
Severity        : Info
FailedMachines  : {}
PercentComplete : 5

RuleId          : 2
Title           : The failover cluster nodes must be enabled for remote management via WMIv2
State           : Started
Severity        : Info
FailedMachines  : {}
PercentComplete : 6

RuleId          : 2
Title           : The failover cluster nodes must be enabled for remote management via WMIv2
State           : Failed
Severity        : Error
FailedMachines  : {90VMHost5}
PercentComplete : 11

RuleId          : 3
Title           : Windows PowerShell remoting should be enabled on each failover cluster node
State           : Started
Severity        : Info
FailedMachines  : {}
PercentComplete : 12

RuleId          : 3
Title           : Windows PowerShell remoting should be enabled on each failover cluster node
State           : Failed
Severity        : Error
FailedMachines  : {90VMHost5}
PercentComplete : 16

RuleId          : 4
Title           : The failover cluster must be running Windows Server 2012
State           : Started
Severity        : Info
FailedMachines  : {}
PercentComplete : 17

RuleId          : 4
Title           : The failover cluster must be running Windows Server 2012
State           : Succeeded
Severity        : Info
FailedMachines  : {}
PercentComplete : 21

RuleId          : 5
Title           : The required versions of .NET Framework and Windows PowerShell must be installed on all
                  failover cluster nodes
State           : Started
Severity        : Info
FailedMachines  : {}
PercentComplete : 22

RuleId          : 5
Title           : The required versions of .NET Framework and Windows PowerShell must be installed on all
                  failover cluster nodes
State           : Succeeded
Severity        : Info
FailedMachines  : {}
PercentComplete : 45

RuleId          : 6
Title           : The Cluster service should be running on all cluster nodes
State           : Started
Severity        : Info
FailedMachines  : {}
PercentComplete : 46

RuleId          : 6
Title           : The Cluster service should be running on all cluster nodes
State           : Succeeded
Severity        : Info
FailedMachines  : {}
PercentComplete : 55

RuleId          : 7
Title           : Automatic Updates must not be configured to automatically install updates on any failover
                  cluster node
State           : Started
Severity        : Info
FailedMachines  : {}
PercentComplete : 56

RuleId          : 7
Title           : Automatic Updates must not be configured to automatically install updates on any failover
                  cluster node
State           : Succeeded
Severity        : Info
FailedMachines  : {}
PercentComplete : 64

RuleId          : 8
Title           : The failover cluster nodes should use the same update source
State           : Started
Severity        : Info
FailedMachines  : {}
PercentComplete : 65

RuleId          : 8
Title           : The failover cluster nodes should use the same update source
State           : Succeeded
Severity        : Info
FailedMachines  : {}
PercentComplete : 73

RuleId          : 9
Title           : A firewall rule that allows remote shutdown should be enabled on each node in the failover
                  cluster
State           : Started
Severity        : Info
FailedMachines  : {}
PercentComplete : 74

RuleId          : 9
Title           : A firewall rule that allows remote shutdown should be enabled on each node in the failover
                  cluster
State           : Succeeded
Severity        : Info
FailedMachines  : {}
PercentComplete : 82

RuleId          : 10
Title           : The machine proxy on each failover cluster node should be set to a local proxy server
State           : Started
Severity        : Info
FailedMachines  : {}
PercentComplete : 83

RuleId          : 10
Title           : The machine proxy on each failover cluster node should be set to a local proxy server
State           : Failed
Severity        : Warning
FailedMachines  : {90VMHost5, 90VMHost6}
PercentComplete : 91

RuleId          : 11
Title           : The CAU clustered role should be installed on the failover cluster to enable self-updating
                  mode
State           : Started
Severity        : Info
FailedMachines  : {}
PercentComplete : 92

RuleId          : 11
Title           : The CAU clustered role should be installed on the failover cluster to enable self-updating
                  mode
State           : Failed
Severity        : Warning
FailedMachines  : {VMCluster}
PercentComplete : 100

WARNING: <f:WSManFault xmlns:f="http://schemas.microsoft.com/wbem/wsman/1/wsmanfault" Code="2150859027" Machin
e="90VMHost5.pacific.local"><f:Message>The WinRM client sent a request to an HTTP server and got a response sa
ying the requested HTTP URL was not available. This is usually returned by a HTTP server that does not support
 the WS-Management protocol. </f:Message></f:WSManFault>
WARNING: Connecting to remote server 90VMHost5 failed with the following error message : The WinRM client sent
 a request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usual
ly returned by a HTTP server that does not support the WS-Management protocol. For more information, see the a
bout_Remote_Troubleshooting Help topic.
WARNING: The WinRM client sent a request to an HTTP server and got a response saying the requested HTTP URL wa
s not available. This is usually returned by a HTTP server that does not support the WS-Management protocol.
ModelId           : Microsoft/Windows/ClusterAwareUpdating
SubModelId        :
Success           : True
ScanTime          : 2/1/2017 4:10:32 PM
ScanTimeUtcOffset : -08:00:00
Detail            : {90VMHOST5, 90VMHOST5}

↧
↧

Access denied in Failover Cluster manager for non-domain admin with read-only or full control on cluster

February 2, 2017, 1:05 am
$
0
0

Hello all,

I observe the following:

When giving a user explicitely permissions to the cluster with  Grant-ClusterAccess <domain>/<user>

The user cannot connect to the cluster in the failover cluster manager. 

Managing the cluster via PowerShell commandlets does work, no messages about administrative privileges is shown. Only FOCM cannot connect for this user. What can I do to fix this?

You know you're an engineer when you have no life and can prove it mathematically

↧

Stop and start cluster nodes on same time

January 25, 2017, 12:36 am
$
0
0
We have a cluster with 4 nodes and File Witness (5 votes) on same enclosure. We need turn off all nodes. Which is the best procedure to stop and start the cluster ??
↧

2 node failover clustering

February 2, 2017, 11:18 am
$
0
0

please explain , how to make 2 node failover cluster , both nodes are directly connected to 5nos 60 bay HGST JBODs .

Thanks

Muhammed Rashid

↧
Viewing all 4519 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>