Server 2012 R2 failover cluster

Hi Guys,
I created a 2 node cluster using server 2012 R2 ..I have VMM 2012 R2 running on both nodes with SQL 2012 SP1
VMM is configured for High availability and SQL always-on feature is also enabled.
Now when I stop cluster service on one of the node, the roles and quorum disk failover to the other node but the quorum disk does not come back online and as a result the cluster fails until I bring back the cluster service on the current owner (owner of
the quorum disk)
I'm at a loss for what to do, any help will be greatly appreciated.
Richard

Hi Guys,
when i run the said commands on both nodes I get the same result ..see below
Validation report shows no warning on the quorum disk
VMM and SQL are not on hyper-v hosts. I have 2 physical machines, each running VMM 2012 R2 (HA) and SQL 2012 SP1 (Always On). Do you believe hosting both on the same server could be the issue? I will look that up too.
The cluster is fine when Node2 owns the quorum disk.
Roles on Node1 successfully fail over to Node2 when I stop cluster service on Node1
When I stop Cluster service on Node2 roles on Node2 move to Node1 (including the quorum disk) but the Disk fails to come online and as a result quorum is lost and the cluster fails until I resume cluster service on Node2.
It looks to me like Node2 owns the quorum Disk explicitly ..
..forever is just a minute away*

Similar Messages

Install SQL Server 2012 SP1 on a Windows Server 2012 R2 Failover Cluster - hangs at "Running discovery on remote machine" on VMWare VSphere 5.5 Update 1

Hi,I'm trying to install SQL Server 2012 SP1 on the first node of a Windows Server 2012 R2 failover cluster.The install hangs whilst displaying the "Please wait while Microsoft SQL Server 2012 Servce
Pack 1 Setup processes the current operation." message.The detail.txt log file shows as follows:(01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : Use cached PID (01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider
: NormalizePid is normalizing input pid (01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid (01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : Use cached
PID (01) 2014-07-17 15:36:35 Slp: Completed Action: FinalCalculateSettings, returned True (01) 2014-07-17 15:36:35 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True (01) 2014-07-17 15:36:35 Slp: ---------------------------------------------------------------------- (01) 2014-07-17 15:36:35 Slp: Running Action: RunRemoteDiscoveryAction (01) 2014-07-17 15:36:36 Slp: Running discovery on local machine (01) 2014-07-17 15:36:36 Slp: Discovery on local machine is complete (01) 2014-07-17
15:36:36 Slp: Running discovery on remote machine: XXX-XXX-01After about 4 hours and 10 minutes, the step seems to time out and move on, however it doesn't seem to have discovered what it needs to and the setup subsuently fails

Hi,
Sorry Information you provided did not helped can you post content of both summary file and details,txt file on shared location for analysis.
Can you download Service pack again and try once more
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Mounted Volume not shwoing up with Windows 2012 R2 failover cluster

Hi
We configured some drives as mounted volumes and configured it with Failover cluster. But it's not showing up the mounted volume details with Cluster Manager, it's showing the details as seen below
Expect support from someone to correct this issue
Thanks in advance
LMS

Hi LMS,
Are you doubt about the disk shown as GUID? Cluster Mount point Disk is showing as a Volume GUID in server 2012 R2 Failover Cluster I creating a mountpoint inside the cluster
and had the same behavior, instead of mount point name we had the volume GUI after volume label, that must by design.
How to configure volume mount points on a Microsoft Cluster Server
http://support.microsoft.com/kb/280297
I’m glad to be of help to you!
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

CSV V/s Pass through disks with HV 2012 R2 failover cluster

Hi
We are using HV 2012 R2 failover cluster with CSV. We found some articles saying pass through disks outperforms CSV. Is this correct?
Regards
LMS

Hi
We are using HV 2012 R2 failover cluster with CSV. We found some articles saying pass through disks outperforms CSV. Is this correct?
"The juice isn't worth the squeeze" (c) ...
Tim is 200% correct here: any performance gains (if any...) you'll get will fade in darkness compared to management burden you'll have with pass-thru disks (issues with failover, VM migration and no
real support with a major VM backup vendors). Making long story short: don't do it.
StarWind Virtual SAN clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

MS DTC not coming online on SQL Server 2008 R2 failover cluster

Dear Experts,
On a SQL Server 2008 R2 failover cluster, MS DTC cluster service is not coming online. It fails with below error message.
"The DTC cluster resource's log file path was originally configured at: E:. Attempting to change that to: M:. This indicates a change in the path of the DTC cluster resource's dependent disk resource. This is not supported. The error code
returned: 0x8000FFFF".
From the Component Services, we can see under the clustered DTCs, in the properties of the log file that it is configured for E drive. The 'Transaction list' and 'Transaction Statistics' are empty. When I try to change the log file path to
point to M drive I get this warning message.
"An MSDTC log file already exists in the selected directory. Resetting an existing MS DTC log file may cause your databases and other transactional resource managers to become inconistent. Please review the MSDTC Administrator's manual before
proceeding. Do you wish to reset the existing MS DTC log"
Could you please advise if this is safe to proceed with this warning as the 'Transaction list' and 'Transaction Statistics' are empty or would it cause any other issue.
Thanks,
MM

Tauseef
Did you tried using wmi....win32_share
$path = "location where to create the folder"
$share = $Shares=[WMICLASS]'WIN32_Share' # class in wmi for share
$Sharename = 'Sharename'
New-Item -type directory -Path $Path
$Shares.Create($Path,$Sharename,0,255,$Sharename)
$Acl = Get-Acl $Path # cmdlet for getting access control list
$Access = New-Object system.security.accesscontrol.filesystemaccessrule("Username","FullControl","ContainerInherit, ObjectInherit", "None", "Allow")
$Acl.AddAccessRule($Access)
Set-Acl $Path $Acl
Thanks Azam When you see answers please Mark as Answer if Helpful..vote as helpful.

Change Hyper-V 2012 R2 failover cluster management subnet

Hi,
We have an existing Hyper-V 2012 R2 Failover cluster. Virtual machines are live on this cluster. The networking team has decided to reorganise the network subnets. As a consequence we need to change the management IPs of our Hyper-V failover
clusters.
What are the possibilities?
Evect 1 node from the cluster, set correct management IP on the evicted cluster. Create a single-node cluster. Mask a new LUN to the single-host cluster. Execute a shared nothing live migration of the VMs which are hosted on old cluster.
Kr,

Hi Kr,
You can refer the following similar scenario article:
Changing Hyper-V Cluster Virtual IP Address (VIP) After Layer 3 Changes
http://blogs.technet.com/b/chrad/archive/2011/09/16/changing-hyper-v-cluster-virtual-ip-address-vip-after-layer-3-changes.aspx
Change IP address Hyper-V Cluster
http://bartvanvugt.blogspot.com/2012/01/change-ip-address-hyper-v-cluster.html
More related third party article:
Change IP address Hyper-V Cluster
http://bartvanvugt.blogspot.com/2012/01/change-ip-address-hyper-v-cluster.html
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Witness Server in a failover cluster

Hi.
I was reading about this witness server in a failover cluster but always thought that the switch between active and passive would be automatic, never thought of a "vote" and a "quorum" to reach.
Under what circumstances do I need this quorum (and therefore a witness server) and what happens if I am even?
Does a witness server have necessarily to be a third one or can be set up as either the active or the passive one?
Cheers

Hi,
In addition to Jared's suggestion, I would like to clarify the following things:
1. The witness server and its directory are used only for quorum purposes where there's an even number of members in the DAG.
2. The witness server should be in the same Active Directory forest as the DAG.
3. It is recommended to specify a Client Access server as the witness server for Exchange 2013 DAG.
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Upgrading from SQL Server 2012 Standard to SQL Server 2014 Standard Failover Cluster

Goal: To upgrade my default instance from SQL Server 2012 to SQL Server 2014 in a failover cluster.
Given:
1) Operating System Windows 2012 R2
2) 2 Virtual Machines in a cluster with SQL Server as a Guest Cluster resource. The two VMS are called APPS08 and APPS09. They are our development environment that is setup similar to our production environment.
Problem: When running the SQL Server 2014 upgrade, I started on the VM that was not running the instance. I then moved onto upgrading on the node that was running the instance. As soon as the install attempt to failover the running instance
an install error occurred that it could not failover. After many install attempts I consistently received the error
The SQL Server Failover cluster instance name 'Dev01'
already exists as a cluster resource. Opening Failover cluster manager there is no record of a DEV01.
New Strategy: Create a SQLCluster called DEV07. At the end of the Install I get 'Resource for instance 'MSSQLSERVER' should not exists. Neither I nor my Windows 2012 guy understand what Resource the install may be referring to.
We do not see anything out of the ordinary.
Any suggestions as to what Resource may be seeing the default instance would be greatly appreciated.

Hi PSCSQLDBA,
As your description, you want to upgrade the default instance in SQL Server cluster.
>> 'SQL Server failover cluster instance name 'Dev01' already exists as cluster resource'
This error could occur when there is a previously used instance name which may not be removed completely.
To work around the issue, please use one of the ways below.
1. At command prompt, type Cluster res. This command will list you all the resources including orphan resources. To delete the orphan resource, type Cluster res <resource name>/delete.
For more information about the process, please refer to the article:
http://gemanjyothisqlserver.blogspot.in/2012/12/sql-2008r22012-cluster-installation.html
2. Delete DNS entries, and force a replication of DNS to the other DNS servers.
For more information about the process, please refer to the article:
http://jon.netdork.net/2011/06/07/failed-cluster-install-and-name-already-exists/#solution
>> 'Resource for instance 'MSSQLSERVER' should not exist'
This error could occur when you already have MSSQLSERVER as a resource in the cluster, which may not be removed completely. To work around the issue, you could rebuild the SQL Server cluster node.
Regards,
Michelle Li

HyperV 2012 R2 Failover cluster, HV problem, all VMs restart

Hello, I have 2 node Failover cluster with two nodes, Hyperv 2012, multipath SAS storage MSA2000. But hardware problem with one node (node2). It shutdown unexpectly. When It hapens NODE1 restar all VMs it is normal? It was configured by cluster validation
tool. There is no witness. I don't clearly understand what happens if one node crash. KR.

As Eric has said it will start the VM's in a crash consistent state on the non crashed host.
But from your example I take your seeing your guests on the non crashed host restart. If this is the case I would say yes! I have seen this happen before. It can happen if your not using quorum because only one node has a vote. I would recommend you create
a witness, on your MSA 2000 carve out 1 GB and do a disk witness. Or if you have a server not in the VM cluster you could do a file share witness, file share is my preferred. Once you have a witness in play you will see all of your hosts having a vote. Look
in the cluster manager at the nodes section. You should see a vote column. Currently it will say 1/0, once the witness is created it will show 1/1.

Unable to create a clustered VM using Remote Server Administration Tools - Failover Cluster Manager

Hi
I am using two Hyper-V Server 2012 R2 and a single WS2012 Datacenter Edition with GUI Interface for management purpose.
I have installed Failover Clustering feature on these two Hyper-V servers and remote server administration tools for Failover Clustering on WS2012 DC Edition with GUI.
I have created cluster using powershell cmdlets on Hyper-V server because I was unable to create a cluster using RSAT-Failover Clustering (May be some privileges issues).
The problem is " I am still not able to create a Hyper-VM using Failover Cluster Manager on WS2012 DC Edition server". It gives me an error "Invalid operation"
Any Help regarding this issue will be very appreciated.
Thanks in Advance.....
Abhinav | MCTS-Server Virtualization

Thanks Tim for your response but atleast I should be able to create and configure VMs for high availability.
I think this is not the issue which I am facing. It gives me an error "invalid class". There is something missing.
Please check and let me know if it can be solved. Any help will be really appreciated.
Thanks in advance.
Abhinav | MCTS-Server Virtualization

Windows Server 2012 - Hyper-V - Cluster Sharded Storage - VHDX unexpectedly gets copied to System Volume Information by "System", Virtual Machines stops respondig

We have a problem with one of our deployments of Windows Server 2012 Hyper-V with a 2 node cluster connected to a iSCSI SAN.
Our setup:
Hosts - Both run Windows Server 2012 Standard and are clustered.
HP ProLiant G7, 24 GB RAM. This is the primary host and normaly all VMs run on this host.
HP ProLiant G5, 20 GB RAM. This is the secondary host that and is intended to be used in case of failure of the primary host.
We have no antivirus on the hosts and the scheduled ShadowCopy (previous version of files) is switched off.
iSCSI SAN:
QNAP NAS TS-869 Pro, 8 INTEL SSDSA2CW160G3 160 GB i a RAID 5 with a Host Spare. 2 Teamed NIC.
Switch:
DLINK DGS-1210-16 - Both the network cards of the Hosts that are dedicated to the Storage and the Storage itself are connected to the same switch and nothing else is connected to this switch.
Virtual Machines:
3 Windows Server 2012 Standard - 1 DC, 1 FileServer, 1 Application Server.
1 Windows Server 2008 Standard Exchange Server.
All VMs are using dynamic disks (as recommended by Microsoft).
Updates
We have applied the most resent updates to the Hosts, VMs and iSCSI SAN about 3 weeks ago with no change in our problem and we continually update the setup.
Normal operation:
Normally this setup works just fine and we see no real difference in speed in startup, file copy and processing speed in LoB applications of this setup compared to a single host with two 10000 RPM Disks. Normal network speed is 10-200 Mbit, but occasionally
we see speeds up to 400 Mbit/s of combined read/write for instance during file repair.
Our Problem:
Our problem is that for some reason a random VHDX gets copied to System Volume Information by "System" of the Clusterd Shared Storage (i.e. C:\ClusterStorage\Volume1\System Volume Information).
All VMs stops responding or responds very slowly during this copy process and you can for instance not send CTRL-ALT-DEL to a VM in the Hyper-V console, or for instance start task manager when already logged in.
This happens at random and not every day and different VHDX files from different VMs gets copied each time. Some time it happens during daytime wich causes a lot of problems, especially when a 200 GB file gets copied (which take a lot of time).
What it is not:
We thought that this was connected to the backup, but the backup had finished 3 hours before the last time this happended and the backup never uses any of the files in System Volume Information so it is not the backup.
An observation:
When this happend today I switched on ShadowCopy (previous files) and set it to only to use 320 MB of storage and then the Copy Process stopped and the virtual Machines started responding again. This could be unrelated since there is no way to see
how much of the VHDX that is left to be copied, so it might have been finished at the same time as I enabled ShadowCopy (previos files).
Our question:
Why is a VHDX copied to System Volume Information when scheduled ShadowCopy (previous version of files) is switched off? As far as I know, nothing should be copied to this folder when this functionis switched off?
List of VSS Writers:
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
 Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
 Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
 State: [1] Stable
 Last error: No error
Writer name: 'VSS Metadata Store Writer'
 Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
 Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
 State: [1] Stable
 Last error: No error
Writer name: 'Performance Counters Writer'
 Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
 Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
 State: [1] Stable
 Last error: No error
Writer name: 'System Writer'
 Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
 Writer Instance Id: {7848396d-00b1-47cd-8ba9-769b7ce402d2}
 State: [1] Stable
 Last error: No error
Writer name: 'Microsoft Hyper-V VSS Writer'
 Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
 Writer Instance Id: {8b6c534a-18dd-4fff-b14e-1d4aebd1db74}
 State: [5] Waiting for completion
 Last error: No error
Writer name: 'Cluster Shared Volume VSS Writer'
 Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}
 Writer Instance Id: {d46c6a69-8b4a-4307-afcf-ca3611c7f680}
 State: [1] Stable
 Last error: No error
Writer name: 'ASR Writer'
 Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
 Writer Instance Id: {fc530484-71db-48c3-af5f-ef398070373e}
 State: [1] Stable
 Last error: No error
Writer name: 'WMI Writer'
 Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
 Writer Instance Id: {3792e26e-c0d0-4901-b799-2e8d9ffe2085}
 State: [1] Stable
 Last error: No error
Writer name: 'Registry Writer'
 Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
 Writer Instance Id: {6ea65f92-e3fd-4a23-9e5f-b23de43bc756}
 State: [1] Stable
 Last error: No error
Writer name: 'BITS Writer'
 Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
 Writer Instance Id: {71dc7876-2089-472c-8fed-4b8862037528}
 State: [1] Stable
 Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
 Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
 Writer Instance Id: {cb0c7fd8-1f5c-41bb-b2cc-82fabbdc466e}
 State: [1] Stable
 Last error: No error
Writer name: 'Cluster Database'
 Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
 Writer Instance Id: {23320f7e-f165-409d-8456-5d7d8fbaefed}
 State: [1] Stable
 Last error: No error
Writer name: 'COM+ REGDB Writer'
 Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
 Writer Instance Id: {f23d0208-e569-48b0-ad30-1addb1a044af}
 State: [1] Stable
 Last error: No error
Please note:
Please only answer our question and do not offer any general optimization tips that do not directly adress the issue! We want the problem to go away, not to finish a bit faster!

Hallo Lawrence!
Thankyou for youre reply, some comments to help you and others who read this thread:
First of all, we use Windows Server 2012 and the VHDX as I wrote in the headline and in the text in my post. We have not had this problem in similar setups with Windows Server 2008 R2, so the problem seem to be introduced in Windows Server 2012.
These posts that you refer to seem to be outdated and/or do not apply to our configuration:
The post about Dynamic Disks:
http://technet.microsoft.com/en-us/library/ee941151(v=WS.10).aspx is only a recommendation for Windows Server 2008 R2 and the VHD format. Dynamic VHDX is indeed recommended by Microsoft when using Windows Server 2012 (please look in the optimization guide
for Windows Server 2012).
Infact, if we use fixed VHDX then we would have a bigger problem since fixed VHDX are generaly larger then Dynamic Disks, i.e. more data would be copied and that would take longer time = the VMs would be unresponsive for a longer time.
The post "What's the deal with the System Volume Information folder"
http://blogs.msdn.com/b/oldnewthing/archive/2003/11/20/55764.aspx is for Windows XP / Windows Server 2003 and some things has changed since then. for instance In Windows Server 2012, Shadow Copies cannot be controlled by going to Control panel -> System.
Instead you right-click on a Drive (i.e. a Volume, for instance the C drive/Volume) in Computer and then click "Configure Shadow Copies".
Windows Server 2008 R2 Backup problem
http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/0fc53adb-477d-425b-8c99-ad006e132336 - This post is about the Antivirus software trying to scan files used during backup that exists in the System Volume Information folder and we do not
have any antivirus software installed on our hosts as I stated in my post.
Comment that might help us:
So according to “System Volume Information” definition, the operation you mentioned is Volume Shadow Copy. Check event viewer to find Volume Shadow Copy related event logs and post them.
Why?
Furhter investigation suggests that a volume shadow copy is somehow created even though the Schedule for Shadows Copies is turned off for all drives. This happens at random and we have not found any pattern. Yesterday this operation took almost all available
disk space (over 200 GB), but all the disk space was released when I turned on scheduled Shadow Copies for the CSV.
I therefore draw these conclusions:
The CSV Volume has about 600 GB of disk space and since Volume Shadows Copy used 200 GB, or about 33% of the disk space, and the default limit is 10% then I conclude that for some reason the unscheduled Volume Shadow Copy did not have any limit (or ignored
the limit).
When I turned on the Schedule I also change the limit to the minimum amount which is 320 MB and this is probably what released the disk space. That is, the unscheduled Volume Shadow Copy operation was aborted and it adhered to the limit and deleted the
Volume Shadow Copy it had taken.
I have also set the limit for Volume Shadow Copies for all other volumes to 320 MB by using the "Configure Shadow Copies" Window that you open by right clicking on a drive (volume) in Computer and then selecting "Configure Shadow Copies...".
It is important to note that setting a limit for Shadow Copy Storage, and disabaling the Schedule are two different things! It is possible to have unlimited storage for Shadow Copies when the Schedule is disabled, however I do not know if this was the case
Before I enabled Shadow Copies on the CSV since I did not look for this.
I now have defined a limit for Shadow Copy Storage to 320 MB on all drives and then no VHDX should be copied to System Volume Information since they are all larger than 320 MB.
Does this sound about right or am I drawing the wrong conclusions?
Limits for Shadow Copies:
Below we list the limits for our two hosts:
"Primary Host":
C:\>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
Shadow Copy Storage association
 For volume: (\\?\Volume{e3ad7feb-178b-11e2-93e8-806e6f6e6963}\)\\?\Volume{e3ad7feb-178b-11e2-93e8-806e6f6e6963}\
 Shadow Copy Storage volume: (\\?\Volume{e3ad7feb-178b-11e2-93e8-806e6f6e6963}\)\\?\Volume{e3ad7feb-178b-11e2-93e8-806e6f6e6963}\
 Used Shadow Copy Storage space: 0 bytes (0%)
 Allocated Shadow Copy Storage space: 0 bytes (0%)
 Maximum Shadow Copy Storage space: 320 MB (91%)
Shadow Copy Storage association
 For volume: (E:)\\?\Volume{dc0a177b-ab03-44c2-8ff6-499b29c3d5cc}\
 Shadow Copy Storage volume: (E:)\\?\Volume{dc0a177b-ab03-44c2-8ff6-499b29c3d5cc}\
 Used Shadow Copy Storage space: 0 bytes (0%)
 Allocated Shadow Copy Storage space: 0 bytes (0%)
 Maximum Shadow Copy Storage space: 320 MB (0%)
Shadow Copy Storage association
 For volume: (G:)\\?\Volume{f58dc334-17be-11e2-93ee-9c8e991b7c20}\
 Shadow Copy Storage volume: (G:)\\?\Volume{f58dc334-17be-11e2-93ee-9c8e991b7c20}\
 Used Shadow Copy Storage space: 0 bytes (0%)
 Allocated Shadow Copy Storage space: 0 bytes (0%)
 Maximum Shadow Copy Storage space: 320 MB (3%)
Shadow Copy Storage association
 For volume: (C:)\\?\Volume{e3ad7fec-178b-11e2-93e8-806e6f6e6963}\
 Shadow Copy Storage volume: (C:)\\?\Volume{e3ad7fec-178b-11e2-93e8-806e6f6e6963}\
 Used Shadow Copy Storage space: 0 bytes (0%)
 Allocated Shadow Copy Storage space: 0 bytes (0%)
 Maximum Shadow Copy Storage space: 320 MB (0%)
C:\>cd \ClusterStorage\Volume1
Secondary host:
C:\>vssadmin list shadowstorage
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2012 Microsoft Corp.
Shadow Copy Storage association
 For volume: (\\?\Volume{b2951138-f01e-11e1-93e8-806e6f6e6963}\)\\?\Volume{b2951138-f01e-11e1-93e8-806e6f6e6963}\
 Shadow Copy Storage volume: (\\?\Volume{b2951138-f01e-11e1-93e8-806e6f6e6963}\)\\?\Volume{b2951138-f01e-11e1-93e8-806e6f6e6963}\
 Used Shadow Copy Storage space: 0 bytes (0%)
 Allocated Shadow Copy Storage space: 0 bytes (0%)
 Maximum Shadow Copy Storage space: 35,0 MB (10%)
Shadow Copy Storage association
 For volume: (D:)\\?\Volume{5228437e-9a01-4690-bc40-1df85a0e6736}\
 Shadow Copy Storage volume: (D:)\\?\Volume{5228437e-9a01-4690-bc40-1df85a0e6736}\
 Used Shadow Copy Storage space: 0 bytes (0%)
 Allocated Shadow Copy Storage space: 0 bytes (0%)
 Maximum Shadow Copy Storage space: 27,3 GB (10%)
Shadow Copy Storage association
 For volume: (C:)\\?\Volume{b2951139-f01e-11e1-93e8-806e6f6e6963}\
 Shadow Copy Storage volume: (C:)\\?\Volume{b2951139-f01e-11e1-93e8-806e6f6e6963}\
 Used Shadow Copy Storage space: 0 bytes (0%)
 Allocated Shadow Copy Storage space: 0 bytes (0%)
 Maximum Shadow Copy Storage space: 6,80 GB (10%)
C:\>
There is something strange about the limits on the Secondary host!
I have not in any way changed the settings on the Secondary host and as you can see, the Secondary host has a maximum limit of only 35 MB storage on the CSV, but it also shows that this is 10% of the Volume. This is clearly not the case since 10% if 600
GB = 60 GB!
The question is, why does it by default set a too small limit (i.e. < 320 MB) on the CSV and is this the cause of the problem? I.e. is the limit ignored since it is smaller than the smallest amount you can provide using the GUI?
Is the default 35 MB maximum Shadow Copy limit a bug, or is there any logical reason for setting a limit that according to the GUI is too small?

Server 2008 R2 Failover cluster network configuration

Hi
We have a customer with a Server 2008 R2 Hyper-V failover cluster. They have 2 cluster networks, "Cluster Network 1" and "Cluster Network 2".
"Cluster Network 1": NIC team on 172.16.1.0/24 for private cluster network communication
"Cluster Network 2": NIC team on 192.168.1.0/24 for production network communication
I can see that "Cluster Network 1" is configured to "Allow cluster network communication on this network" and "Allow clients to connect through this network".
If "Cluster Network 1" is ONLY for communication between the to cluster nodes then I assume the selection in "Allow clients to connect through this network" should be removed?
/Lasse

It will cause a lost network connection for any client that is accessing through that network. Those clients would need to reconnect.
Did you configure both IPs on the cluster resource name that clients are accessing? If you only configured the one you want, there should be no issue. If you configured both, then it is possible some clients might be connected via the private
network.
Another thing you should, and if you have already done this you will most likely not have issues at all, is that you should disable DNS registration on any network you do not want client access coming through. If the clients can only find the resource
through the DNS name registered, that is the way they will be coming in. In my clusters, which often have 7 or more NICs, there is only one with a published DNS record.
. : | : . : | : . tim

Server 2008 R2 failover cluster for DFS servers

A new client currently has a couple Server 2008 R2 failover clusters (one at each of their two primary sites) as their two hub DFS locations. I'm confused, and can't see much of a reason for this implementation, which only seems to introduce added complexity
with no real benefits. Here are my reasons:
- At each site, the servers in the failover clusters are on the same server VM farms, hosted on the same SAN's.
- The data hosted on each node of the clusters are not identical. For example, server1 has 25 DFS replicated folders and server2 has 20 replicated folders. In fact, the ~25 folders on server1 are all named <site>-user, and the ~20 folders on server
2 are <site>-data. There appears to be no crossover.
So if the SAN fails, they're screwed. If the VM host fails, they're screwed. Why not just have two DFS servers at each site for redundancy within each site, and replicating with other site DFS servers as needed? I'm not super strong with failover clustering
at all though, so I may easily be missing something.

Hi Steve,
From the description, as you said it seems create more factors which may cause a failure.
Using DFS on cluster could eliminate the possible of a single failing VM. However if the VM host is down, which will still leads to a failure. So actually the risk is still them same as just creating DFS namespace on these 2 VM hosts or any other file server.
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Adding a server into a failover cluster

Hi all, i have the following question:
i have a Failover Cluster with 3 servers and now i have to add another server. The cluster is in a pruction environment and the service cant be cut off during working hours. Adding this new server will cut off this service?. And which are the steps i should follow to complete this task?.
Thanks in advance
Dj

Thanks for the reply. I have installed the latest VMWare tools and it hasn't fixed my issue. It's just weird. I've set this up multiple times using Sun Fire Servers or IBM Servers (non virtualized) and it's worked flawlessly. But using ESXi each one has had the same issue. Four instances each with differing hardware. I will try to look at netstat and see what I find. I'm pretty sure if the switch port was shutting down due to errors that just rebooting the server wouldn't clear it. I think you have to manually reset the switch port after something like that occurs. Anyways I will check the switch logs and see if I see something there also.
In my test environment I use VMWare Server 2.0 and I've never had this issue using that platform. I'm currently doing an install where they are using ESX servers and it's ran perfectly so far, albeit with a small load compared to what it will be. Almost wondering if it could be something with ESXi. I didn't think there was much of a difference at the base level between ESXi and ESX. I will check out the link you sent and proceed with Oracle tech support. They want me to run ut_gather, etc. on the server right after it fails. Problem is they are all running live production in a hospital environment so it's difficult to schedule a time when I can enable the second server and wait for it to fail. Again, thank you very much for your input and please let me know if you think of something else to check.

Mac10.x client can't connect to File Server on Windows2008 Failover Cluster

Installation of a cluster was made according to the document "Failover Cluster Step-by-Step Guide: Configuring a Two-Node File Server Failover Cluster " http://technet.microsoft.com/en-us/library/cc731844.aspx.
My Mac OS X 10.5.2 and Mac OS X 10.4.11 clients be able to connect to a non-cluster file server on a Windows 2008 (the File Services role) and also to old file cluster on a Windows 2003.
Why Mac clients can't connect to Windows 2008 Failover Cluster?

Are you running a firewall on the Macs. If yes does it work with out the firewall? If it works with out the firewall that means you will have to create a custom ipf rule which includes the both the physical an virtual IP addresses of your cluster.

Server 2012 R2 failover cluster

Similar Messages

Maybe you are looking for