RDS 2012 to RDS 2012 R2 - RDVH cluster

So i am upgrading everything. Using this guide http://blogs.msdn.com/b/rds/archive/2014/01/29/remote-desktop-services-upgrade-and-migration-guidelines-for-windows-server-2012-r2.aspx everything seems pretty straight forward.
So i know there is no upgrade path for the cluster. I basically have to destroy it and rebuild it. But i guess this makes me wonder if people that have multiple RDVH, are they clustering? In addition is there any advantages or disadvantages to clustering
vs not in this type of setup?

Hi,
Thank you for your posting in Windows Server Forum.
In regards to multiple RDVH there is already specified in the article point 3 which you have specified. Also please go through below article for more information.
Microsoft VDI – High Availability Deployment Options
http://blogs.msdn.com/b/rds/archive/2010/03/01/microsoft-vdi-high-availability-deployment-options.aspx
Hope it helps!
Thanks,
Dharmesh

Similar Messages

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]

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

Should one use MPIO and/or CSV in a Windows 2012 R2 guest cluster?

Should one use MPIO and/or CSV in a Windows 2012 R2 guest cluster using VMware ESXi 5.5 presented Fiber LUN RDMs.
If MPIO were implemented is there a preference for HW manufacturer DISM vs. MS DISM in a guest cluster?
What partition size/offset is recommended for the MSR partition (currently set to 1000 MB) - unfortunately seeing storage validation error with failing block write at block 2048 (which in return may be related to VMware ESXi 5.5. disk partition layout)
The current setup works without using MPIO (question is would it help overcome the current failing persistent SCSI-3 reservation warning.)
What were the benefit of using CSV if any in a guest cluster? The Luns in scope would eventually hold SQL data and log files.
Thanks for your input already.
Sassan Karai

Hi,
Regardless of what type of the shared storage is failover cluster have to use the shared storage, the shared storage can redirect the failed node data to others node, accordingly
the failover cluster can get the high availability.
From you descripted error there must you choose the VMware® unsupported storage with failover cluster, please refer the following VMware® official KB then reconfirm your topology
design is supported.
Third party KB:
VMware vSphere support for Microsoft clustering solutions on VMware products
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1037959
The related KB:
Failover Clustering Hardware Requirements and Storage Options
http://technet.microsoft.com/zh-cn/library/jj612869.aspx
More information:
Validate Storage Spaces Persistent Reservation Test Results with Warning
http://blogs.msdn.com/b/clustering/archive/2013/05/24/10421247.aspx
Understanding Cluster Validation Tests: Storage
http://technet.microsoft.com/en-us/library/cc771259.aspx#PersistentReservation
Shared storage for Windows Failover Cluster with MPIO
http://blogs.technet.com/b/storageserver/archive/2011/05/31/shared-storage-for-windows-failover-cluster-with-mpio.aspx
Hope this helps.
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.

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.

Planning System Center Operation Manager 2012 R2 on SQL 2012 Active/Passive Cluster

Dears,
I'm planning to deploy System Center Operation Manager 2012 R2 on SQL 2012 Active/Passive Cluster which have other sql instances running for other applications. And i'm planning to create a new instance for SCOM, kindly provide me recommendation
whether i can install all sql databases for SCOM on same sql instance or does it require separate instances for opsmanger database , dw database and ACS database?
Thanks in advance..

Hi,
Yes, all SCOM SQL databases can run on the same instance of SQL server.
As well, look at some helpful posts for the topic:
http://technet.microsoft.com/library/dn281933.aspx
http://blogs.technet.com/b/kevinholman/archive/2013/10/18/opsmgr-2012-r2-quickstart-deployment-guide.aspx
Natalya
### If my post helped you, please take a moment to Vote as Helpful and\or Mark as an Answer

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.

What are the host network requirements for a 2012 R2 failover cluster using fiber channel?

I've seen comments on here regarding how the heartbeat signal isn't really required anymore - is that true? We started using Hyper-V in its infancy and have upgraded gleefully every step of the way. With 2012 R2, we also upgraded from 1gb iSCSI
to 8GB Fiber Channel. Currently, I have three NICs in use on each host. One for "No cluster communication" on it's own VLAN. Another for "Allow cluster network communication on this network" but NOT allowing clients, on
a different VLAN. And lastly the public network which allows cluster comms and clients on it (public VLAN).
Is it still necessary to have all three of these NICs in use? If the heartbeat isn't necessary any more, is there any reason to not have two public IPs and do away with the rest of the network? (two for fault tolerance) Does Live Migration
still use Ethernet if FC is available? I wasn't sure what all has changed with these requirements since Hyper-V first came out.
If it matters, we have 5 servers w/160GB RAM, 8 NICs, dual HBAs connected to redundant FC switches, going to two SANs. We're running around 30 VMs right now.
Can someone share their knowledge with me regarding the proper setup for my environment? Many Thanks!

Hi,
You can setup cluster with a single network but that leaves you with single point of failure on the Networking front, it is still recommended to have a heartbeat network.
Live migration would still happen though Ethernet, it has nothing to do with FC. Don't get confused, you had iSCSI for storage which used one of your VLAN and now you have FC for your storage.
Your hardware specs looks good. You can set up the following networks -
1. Public Network - Team two or more NICs (based on bandwidth aggregation)
2. Heartbeat Network - Don't use teamed Adaptor
3. Live Migration - Team two or more NICs (based on bandwidth aggregation)
Plan properly and draw guidelines to visualize and to remove single point of failure at all points.
Feel free to ask if you have some more queries.
Regards
Prabhash

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 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*

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.

Is it possible to Migrate Live VMs from a Windows 2012 Hyper-V Cluster to a different 2012 R2 Cluster?

At the moment I'm in a bit of dilemma because I know that Windows 2012 supports "Shared Nothing Live Migration" but recently I got to know that this feature is available for stand alone Hyper-V Servers. My Setup is that I have
3 Servers running Windows Server 2012 Hyper-v Failover Cluster and I need to migrate everything to a new cluster running on Windows Server 2012 R2 and offcourse some VMs can't be turned off during migration so I need to do this live during production hours.
Another note is that both clusters will be running on the different LUNs since each cluster has its own CSVs. I need to know if it is possible to migrate such VMs/Roles Live without have any downtime of the VMs/Roles?

Yes, but one exception - live migration works only on "compatible cpu's". There actually is a setting in CPU for forcing compatibility
mode. If that is not set, and you mvoe for example from AMD to Intel, then - this is not possible in live migration, cluster or not.

2012 R2 - First cluster, having issues creating Quorum witness disk

Its my first Server 2012 R2 Cluster and its based on a Dell VRTX server with shared storage.
I've created the cluster and I'm now trying to setup the Quorum witness disk.
In FCM Storage/Disks a 600mb disk is shown as online and I've called it Quorum.
In Win Disk Manager this disk shows as offline and reserved.
When I run the 'Configure Cluster Quorum Settings' wizard, pick 'Select the quorum witness', pick ' configure a disk witness' I get the error
No suitable disks exist in Available storage.
What am I missing?
Any help/advice/suggestions grateful appreciated :)

ok, figured it out:-
On Cluster 1 selected the Disk and put it in maintenance in Storage/Pools.
On Server 2 - selected Disk 1 and formatted it as NTFS and called it Quorum.
Then took the Disk 1 offline in Disk Management.
In Cluster 1 brought the Disk back on-line.
Ran the Quorum wizard and it works :)

Server 2012 File Server Cluster Shadow Copies Disappear Some Time After Failover

Hello,
I've seen similar questions posted on here before however I have yet to find a solution that worked for us so I'm adding my process in hopes someone can point out where I went wrong.
The problem: After failover, shadow copies are only available for a short time on the secondary server. Before the task to create new shadow copies happens the shadow copies are deleted. Failing back shows them missing on the primary server as
well when this happens.
We have a 2 node (hereafter server1 and server2) cluster with a quorum disk. There are 8 disk resources which are mapped to the cluster via iScsi. 4 of these disks are setup as storage and the other 4 are currently set up as shadow copy volumes
for their respective storage volume.
Previously we weren't using separate shadow copy volumes and seeing the same issue described in the topic title. I followed two other topics on here that seemed close and then setup the separate shadow copy volumes however it has yet to alleviate the
issue. These are the two other topics :
Topic 1: https://social.technet.microsoft.com/Forums/windowsserver/en-US/ba0d2568-53ac-4523-a49e-4e453d14627f/failover-cluster-server-file-server-role-is-clustered-shadow-copies-do-not-seem-to-travel-to?forum=winserverClustering
Topic 2: https://social.technet.microsoft.com/Forums/windowsserver/en-US/c884c31b-a50e-4c9d-96f3-119e347a61e8/shadow-copies-missing-after-failover-on-2008-r2-cluster
After reading both of those topics I did the following:
1) Add the 4 new volumes to the cluster for shadow copies
2) Made each storage volume dependent on it's shadow copy volume in FCM
3) Went to the currently active node directly and opened up "My Computer", I then went to the properties of each storage volume and set up shadow copies to go to the respective shadow copy volume drive letter with correct size for spacing, etc.
4) I then went back to FCM and right clicked on the corresponding storage volume and choose "Configure Shadow Copy" and set the schedule for 12:00 noon and 5:00 PM.
5) I noticed that on the nodes the task was created and that the task would failover between the nodes and appeared correct.
6) Everything appears to failover correctly, all volumes come up, drive letters are same, shadow copy storage settings are the same, and 4 scheduled tasks for shadow copy appear on the current node after failover.
Thinking everything was setup according to best practice I did some testing by changing file contents throughout the day making sure that previous versions were created as scheduled on server1. I then rebooted Server1 to simulate failure. Server2
picked up the role within about 10 seconds and files were avaiable. I checked and I could still see previous versions for the files after failover that were created on server1. Unfortunately that didn't last as the next day before noon I was going
to make more changes to files to ensure that not only could we see the shadow copies that were created when Server1 owned the file server role but also that the copies created on Server2 would be seen on failback. I was disappointed to discover that
the shadow copies were all gone and failing back didn't produce them either.
Does anyone have any insight into this issue? I must be missing a switch somewhere or perhaps this isn't even possible with our cluster type based on this: http://technet.microsoft.com/en-us/library/cc779378%28v=ws.10%29.aspx
Now here's an interesting part, shadow copies on 1 of our 4 volumes have been retained from both nodes through the testing, but I can't figure out what makes it different though I do suspect that perhaps the "Disk#s" in computer management / disk
management perhaps need to be the same between servers? For example, on server 1 the disk #s for cluster volume 1 might be "Disk4" but on server 2 the same volume might be called "Disk7", however I think that operations like this
and shadow copy are based on the disk GUID and perhaps this shouldn't matter.
Edit, checked on the disk numbers, I see no correlation between what I'm seeing in shadow copy and what is happening to the numbers. All other items, quotas, etc fail and work correctly despite these diffs:
Disk Numbers on Server 1:
Format: "shadow/storerelation volume = Disk Number"
aHome storage1 = 16
aShared storage2 = 09
sHome storage3 = 01
sShared storage4 = 04
aHome shadow1 = 10
aShared shadow2 = 11
sHome shadow3 = 02
sShared shadow4 = 05
Disk numbers on Server 2:
aHome storage1 = 16 (SAME)
aShared storage2 = 04 (DIFF)
sHome storage3 = 05 (DIFF)
sShared storage4 = 08 (DIFF)
aHome shadow1 = 10 (SAME)
aShared shadow2 = 11 (SAME)
sHome shadow3 = 06 (DIFF)
sShared shadow4 = 09 (DIFF)
Thanks in advance for your assistance/guidance on this matter!

Hello Alex,
Thank you for your reply. I will go through your questions in order as best I can, though I'm not the backup expert here.
1) "Did you see any event ID when the VSS fail?
please offer us more information about your environment, such as what type backup you are using the soft ware based or hard ware VSS device."
I saw a number of events on inspection. Interestingly enough, the event ID 60 issues did not occur on the drive where shadow copies did remain after the two reboots. I'm putting my event notes in a code block to try to preserve formatting/readability.
I've written down events from both server 1 and 2 in this code block, documenting the first reboot causing the role to move to server 2 and then the second reboot going back to server 1:
JANUARY 2
9:34:20 PM - Server 1 - Event ID: 1074 - INFO - Source: User 32 - Standard reboot request from explorer.exe (Initiated by me)
9:34:21 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Volume Shadow Copy service entered the running state."
9:34:21 PM - Server 1 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy49
F:
T:
The locale specific resource for the desired message is not present"
9:34:21 PM - Server 1 - Event ID 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy1
H:
V:
The locale specific resource for the desired message is not present"
***The above event repeats with only the number changing, drive letters stay same, citing VolumeShadowCopy# numbers 6, 13, 18, 22, 27, 32, 38, 41, 45, 51,
9:34:21 PM - Server 1 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy4
E:
S:
The locale specific resource for the desired message is not present"
***The above event repeats with only the number changing, drive letters stay same, citing VolumeShadowCopy# numbers 5, 10, 19, 21, 25, 29, 37, 40, 46, 48, 48
9:34:28 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The NetBackup Legacy Network Service service entered the stopped state."
9:34:28 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Volume Shadow Copy service entered the stopped state.""
9:34:29 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The NetBackup Client Service service entered the stopped state."
9:34:30 PM - Server 1 - Event ID: 7036 - INFO - Source: Service Control Manager - "The NetBackup Discovery Framework service entered the stopped state."
10:44:07 PM - Server 2 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Volume Shadow Copy service entered the running state."
10:44:08 PM - Server 2 - Event ID: 7036 - INFO - Source: Service Control Manager - "The Microsoft Software Shadow Copy Provider service entered the running state."
10:45:01 PM - Server 2 - Event ID: 48 - ERROR - Source: bxois - "Target failed to respond in time to a NOP request."
10:45:01 PM - Server 2 - Event ID: 20 - ERROR - Source: bxois - "Connection to the target was lost. The initiator will attempt to retry the connection."
10:45:01 PM - Server 2 - Event ID: 153 - WARN - Source: disk - "The IO operation at logical block address 0x146d2c580 for Disk 7 was retried."
10:45:03 PM - Server 2 - Event ID: 34 - INFO - Source: bxois - "A connection to the target was lost, but Initiator successfully reconnected to the target. Dump data contains the target name."
JANUARY 3
At around 2:30 I reboot Server 2, seeing that shadow copy was missing after previous failure. Here are the relevant events from the flip back to server 1.
2:30:34 PM - Server 2 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy24
F:
T:
The locale specific resource for the desired message is not present"
2:30:34 PM - Server 2 - Event ID: 60 - ERROR - Source: volsnap - "The description for Event ID 60 from source volsnap cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
\Device\HarddiskVolumeShadowCopy23
E:
S:
The locale specific resource for the desired message is not present"
We are using Symantec NetBackup. The client agent is installed on both server1 and 2. We're backing them up based on the complete drive letter for each storage volume (this makes recovery easier). I believe this is what you would call "software
based VSS". We don't have the infrastructure/setup to do hardware based snapshots. The drives reside on a compellent san mapped to the cluster via iScsi.
2) "Confirm the following registry is exist:
- HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VSS\Settings"
The key is there, however the DWORD value is not, would that mean that the
default value is being used at this point?

Guide to migrating a HV 2012 cluster managed by VMM to HV 2012 R2 + VMM R2

Hello everyone,
I have a task on hand and even after searching the ‘net for quite some time, I have not come across a solution listed on one page. I hope this thread becomes a “Guide to migrating a Hyper-V 2012 cluster managed by VMM 2012 to Hyper-V 2012 R2 + VMM 2012
R2”.
My searches did find these useful threads but they do not have all the information I need:
http://social.technet.microsoft.com/Forums/systemcenter/en-US/eb824c20-9632-4ec9-9a71-2d1717e44a81/migrate-from-2012-to-2012-r2-cluster-with-vmm-2012-r2?forum=virtualmachinemgrclustering
http://social.technet.microsoft.com/Forums/windowsserver/en-US/34412c47-3a37-4ead-aa67-f5119382ae9d/upgrade-from-server-2012-clusterhyperv-to-server-2012-r2-clusterhyperv?forum=winserverClustering
http://social.technet.microsoft.com/Forums/systemcenter/en-US/5d4103b5-6491-40d2-b52e-7fffde9580ff/vmm-2012-sp1-supported-to-manage-windows-server-2012-r2-hyperv-cluster?forum=virtualmachingmgrhyperv
So let me start by listing what I have right now:
I have a 4 node cluster running Hyper-V 2012 SP1 (the free, core edition).
It is currently being managed with SC VMM 2012 SP1.
99% of the VMs are running on CSVs cut off a Fiber Channel SAN. I have some VMs on local drives and they are not HA.
Everything is in production. I have around 90 VMs total.
I do have capacity to take up to two HV hosts out of the cluster and still survive just fine.
I also have two other spare servers which have no OS on them.
What I don’t have:
I do not have SCOM or DPM or any other SC component.
Well, I used to have SCOM 2012 but I uninstalled it and removed it. Long story, don’t ask! I do plan to install SCOM 2012 R2 at some point soon.
Here is what I want to do:
Upgrade both the cluster and VMM to 2012 R2 version.
This time, I want to use Server 2012 Datacenter edition (with GUI).
I plan to join the spare servers to the 2012 R2 cluster.
Here is what I have learnt up until now (and correct me if I am wrong):
The steps I need to take to accomplish all this are:
Upgrade VMM 2012 to VMM 2012 R2 version
Eject at least one host from the cluster
Install Server 2012 R2 on that server.
Configure a one server (or more, if possible) cluster running 2012 R2
Give that server the same old CSVs
Use the “Copy cluster roles Wizard” to copy VMs from old cluster to new cluster. However this will incur downtime.
I have not started doing all this because I am not 100% sure on some things.
Here is the list of my questions:
1. About step #1: Upgrade VMM to VMM R2 version
Is there any reliable / official guide out there for this? I have seen these on the net:
http://technet.microsoft.com/en-us/library/dn469607.aspx
http://www.systemcentercentral.com/migrating-from-vmm-2012-sp1-to-vmm-2012-r2-step-by-step-upgrading-to-2012-r2-series/
The problem I see is that none of them talk about upgrading a clustered scenario. Do I assume that the steps of upgrading VMM 2012 to 2012 R2 are the same with or without a cluster?
On the server I eject from the cluster, do I upgrade the OS or do a fresh install? I prefer doing a fresh install.
2. Is there a way of doing all this with no downtime?
I am worried about needing downtime for the last step “copy roles…”. I wish there was a way of migrating the roles (VMs) without any downtime.
3. Anything I need to worry about?
I wonder if I need to be careful about granting access to the CSVs to the new R2 Cluster. Will that cause any problem?
Any inputs on this topic are highly appreciated! I promise to update the first post so that it becomes a guide as I get corrections and inputs from everyone :-)
Thanks!
-Rajeev rajdude.com

Time to tackle the actual Hyper-V Cluster migration:
So by this time, I have two nodes in the old Hyper-V 2012 cluster managed by SC VMM 2012 R2. I wiped out the OS on the other 2 nodes and installed Windows 2012
Datacenter on them. This time I am not installing the Core edition for Hyper-V. After working with Core for a year or so, I feel Core gives way too much trouble for very little gain.
Now I plan to follow a technet document which describes how to
migrate virtual machines from a Hyper-V cluster using Cluster Shared Volumes (CSV). Although this document does not describe VMM I think VMM should be able to use those migrated VMs. Here is this migration strategy in a nutshell:
Create a new cluster using 2012 R2
Present the existing CSVs to the new cluster.
Leave the disk offline on the new cluster.
Use the copy cluster roles wizard in Failover Cluster Manager to copy VMs from old cluster to new cluster.
Virtual machines are created on the new cluster but are not turned on.
Turn off the virtual machines and take the disk offline on the old cluster and then on the new cluster you need to enable the disk and start the virtual machines.
Hmmm…sounds pretty involved to me. Well let’s get on with it. First things first…in order to use this migration strategy we need to create a new cluster.
Here are the steps I took to create a new cluster:
Install 2 Windows 2012 R2 on the same 2 servers I ejected from the old cluster.
Correct drive letters of local hard disk drives and optical drives, if needed.
Update them.
Setup networking. Take care of main network, heartbeat for cluster and iSCSI networks (if applicable). Here are some best practices:
http://blogs.technet.com/b/askcore/archive/2014/02/20/configuring-windows-failover-cluster-networks.aspx
http://blogs.msdn.com/b/clustering/archive/2011/06/17/10176338.aspx
https://social.technet.microsoft.com/wiki/contents/articles/9711.hyper-v-network-design-configuration-and-prioritization-guidance.aspx
http://technet.microsoft.com/en-us/library/dn550728.aspx
Make sure your bindings order is correct. I had to correct mine because by default, the heartbeat network was at the top!
I also followed this checklist of Hyper-v’s best practices.
http://blogs.technet.com/b/askpfeplat/archive/2013/03/10/windows-server-2012-hyper-v-best-practices-in-easy-checklist-form.aspx
Much of the stuff in there is very relevant.
Add the domain account used for host management and the SCVMM service account to the local admin group on the 2 new servers.
Use SC VMM manager to install Hyper-V role on the two new servers. VMM can do that as a part of the “Add Host process”.
In VMM, right click on “All Hosts” and click on “Add Hyper-V hosts and clusters”. Go through the wizard and add the two new servers.
When I did this, it failed. I got three errors, Error 10441, Warning 10444 and warning 26179.
I logged into one of the new servers locally and from Server Manager >> Dashboard >> Add roles and features.
On the “create virtual switch page, I selected the NIC connected to the main company network (as this time I have only one NIC for the company network, you should have at least two).
Unfortunately, even this time I get an error: Access is denied: 0x800700005
This is very strange because I am already logged on as an admin here.
Now I started checking for windows updates. I remembered that the checklist above also has a set of recommended updates. There was a huge 890MB), cumulative update available KB2919355. I installed and restarted after that.
I also installed the feature “Multipath I/O” since I was getting the “warning 26179”.
After this installation, I ran windows update again. No available updates.
Now I went back to VMM. I really want to enable the Hyper-V role using VMM. So I repeated step # 8. Interestingly, this time I did not get any error. VMM rebooted the host automatically. Yay!
Now I repeated steps 14 to 16 on the second server. Worked fine!
At this point we are ready to create a new cluster using the two nodes. I followed this document:
http://technet.microsoft.com/en-us/library/gg610576.aspx
At this point I ran into a problem. I talked about it on my thread: When I try to create a new HV cluster using the "Create HV Cluster" wizard in VMM, it comes to a screen titled "Storage" where it shows all the existing LUNs as disks and
it says "select the discs you want to cluster". That is all good but at the bottom it says "Any data on the disks will be overwritten”. Of course I want to keep my data intact so I can use the copy cluster roles wizard later on! How can I create a new cluster
which uses the same disks as the old cluster WITHOUT wiping out the disks?
Ok so I did not get an answer on the forum, so I decided NOT to take a risk and do a quick test. Here is what I did: I masked/unexported all CSVs. Then I created a test CSV, put some data on it and proceeded to create a cluster using that
CSV and a quorum/witness disk.
This time on the storage page, For the test volume I checked the checkbox under CSV. I left the format boxes unchecked << THIS IS WRONG read below for updates
The attempt failed. Somehow the test CSV got configured as a local disk on host #1, it was showing up as NTFS instead of CSVFS. The VMM cluster creation process stopped. I found out that both the CSV and the quorum disk were online on the
node #1. I made them offline.
Retried , got the same error as last time : Mounts storage disk on (servername).
FINALLY I realized that step # 21 bove is WRONG! You need to select “Do not format” under the file system column. This will leave the CSV untouched.
Unfortunately, even this did not work. So I just took away ALL CSVs and tried to recreate the Cluster. It STILL did not work! LOL! The error is 25303
I corrected the permissions as this:
ON the HV hosts, inside local administrators group add VMM service account, Host admin account and VMM server’s computer account
Inside “Virtual Machine Manager Servers” group add VMM server’s computer account
Unfortunately, it still did not work! The error is 25303 (same). I looked everywhere including all the logs (system and security) nothing there. I searched on the net but never found a solution. Eventually I accepted defeat and tried to
create a cluster from outside VMM…using “Failover cluster manager”
Even then I got an error! It seems to me that it failed on creating the computer name of the cluster in AD.
I tried it again with a different computer name in AD…something which had never been created earlier (I had mistakenly created a computer name for the cluster and then deleted it). This time it worked! However I got an error that the witness
disk was not created because it does not have an acceptable file system. Hmmmm.,….I had not formatted the witness disk since I thought the cluster wizard will do it. I created a Witness disk later, manually.)
Interestingly, when I opened VMM again, I see the cluster in there and I am able to manage the cluster from within VMM…interesting!
-Rajeev rajdude.com

RDS 2012 to RDS 2012 R2 - RDVH cluster

Similar Messages

Maybe you are looking for