Building a Hyper-V Cluster with Server 2012 R2

I'm building a 3 node Hyper-V cluster with Server 2012 R2. I create the cluster but the report is telling me I should configure a disk witness as a best practice. Do I need that with a 3 node cluster. In 2008 R2, 3 nodes give me node majority
and I'm good to go.
Thanks
SMaximus7

True, but Windows Server 2012 introduced a dynamic quorum capability. When you have an odd number of nodes in the cluster, you really don't need to have a witness to ensure availabilty. But with the witness what happens is that if you lose a
node a witness comes in, so there are three quorum votes - one for each surviving node and the witness. Then, if another node fails, the cluster will continue to be operational because now you have the witness and the surviving node to maintain quorum.
Not absolutely needed, but a real nice to have. And, since it just takes such a small disk for a disk witness, or a file share for a file share witness, there is no really reason not to include it.
. : | : . : | : . tim

Similar Messages

Add Node to Hyper-V Cluster running Server 2012 R2

Hi All,
I am in the process to upgrade our Hyper-V Cluster to Server 2012 R2 but I am not sure about the required Validation test.
The Situation at the Moment-> 1 Node Cluster running Server 2012 R2 with 2 CSVs and Quorum. Addtional Server prepared to add to the Cluster. One CSV is empty and could be used for the Validation Test. On the Other CSV are running 10 VMs in production.
So when I start the Validation wizard I can select specific CSVs to test, which makes sense;-) But the Warning message is not clear for me "TO AVOID ROLE FAILURES, IT IS RECOMMENDED THAT ALL ROLES USING CLUSTER SHARED VOLUMES BE STOPPED BEFORE THE STORAGE
IS VALIDATED". Does it mean that ALL CSVs will be testest and Switched offline during the test or just the CSV that i have selected in the Options? I have to avoid definitly that the CSV where all the VMs are running will be switched offline and also
that the configuration will be corputed after loosing the CSV where the VMs are running.
Can someone confirm that ONLY the selected CSV will be used for the Validation test ???
Many thanks
Markus

Hi,
The validation will test the select the CSV storage, if you have guest vm running this CSV it must shutdown or saved before you validate the CSV.
Several tests will actually trigger failovers and move the disks and groups to different cluster nodes which will cause downtime, and these include Validating Disk Arbitration,
Disk Failover, Multiple Arbitration, SCSI-3 Persistent Reservation, and Simultaneous Failover.
So if you want to test a majority of the functionality of your cluster without impacting availability, exclude these tests.
The related information:
Validating a Cluster with Zero Downtime
http://blogs.msdn.com/b/clustering/archive/2011/06/28/10180803.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.

How do I do a Windows 7 restore as a Hyper-V clent with Server 2012 Essentials R2?

How do I do a Windows 7 restore as a Hyper-V client with Server 2012 Essentials R2? There is no client restore CD available as an ISO to mount as the CD.
Scott

Hi,
As we know, to simplify the bare metal restore scenario, we implemented the Client Restore Service in Windows Server 2012 R2 Essentials, which will enable WDS on the Windows Server Essentials
server and configure the client restore image as a boot image. With the Client Restore Service turned on, the administrator can initiate a PXE boot on a client computer by using a network interface to launch the Client Restore Wizard and restore the client
computer. There’s no need to prepare a client restore DVD, or a client restore USB bootable key. For details about how to perform the client restore, please refer to the following article.
Set Up Client Restore on Server 2012 R2 Essentials
http://www.mcbsys.com/techblog/2014/01/set-up-client-restore-on-server-2012-r2-essentials/
Hope this helps.
Best Regards,
Andy Qi
Andy Qi
TechNet Community Support

I can't find failover cluster management after creating hyper-v cluster on SCVMM 2012 R2

I've created a hyper-v cluster on scvmm 2012 r2 but I can't find the failover cluster manager to move storage resources. all hosts are showing to have hyperv role and failover clustering feature installed. disk Witness in Quorum is good, same as for the
other CSV lun. Please help me Microsoft. Thank you.

The management consoles are not getting installed while building the cluster through SCVMM. However, its not mandatory to have the management tools on the server. You can have it on a different machine with this management tools installed and connect to
this cluster remotely.
Optimism is the faith that leads to achievement. Nothing can be done without hope and confidence.
InsideVirtualization.com

How can I Create a Client Configuration File for RemoteApp and Desktop Connection with Server 2012?

I have a working RDS RemoteApp site and looking to test out the feature in Windows 7 Control Panel\All Control Panel Items\RemoteApp and Desktop Connections
I came across this link: Create a Client Configuration File for RemoteApp and Desktop Connection and I believe this is what I need to do first, but these instructions are for
Server 2008, and I'm running 2012.
Any suggestions or tips on how I can begin testing this with Server 2012?

Hi,
You can manually enter the path to the 2012 feed and it will connect and download the RemoteApps and Desktop connections.
If you need a sample .wcx file I have posted one here a couple of times. If you want I will look for it and post a link.
-TP
I tried adding my URL's below, these are sample links that work for me right now for when I log into the web page, but neither of these work. And I'm not sure what I would need to do with or how to create a .wcx file.
When I type in my URL of: https://connect.mydomain.org/RDWeb, I get redirected to:
https://connect.mydomain.org/RDWeb/Pages/en-US/login.aspx?ReturnUrl=/RDWeb/Pages/en-US/Default.aspx

Run hyper-v on physical machine with server 2012

I currently am running windows 8.1 with several 8.1 hyper-v clients. I am about to have to do a new install of the host os because i am getting a new faster drive. The convenience and speed of backing up and moving hyper-v clients to different systems is
so easy i was hoping i could take advantage of it for the future. i would also like to use some of the functions of windows only available in the server edition of windows. as a dreamspark student you can get a free copy of windows server 2012. I have not
set up a windows server, but i have run a Linux and bsd one. I only have 1 physical machine. Does it make sense at all to install windows server 2012 and then have all of my working systems be hyper-v clients? i play games and have a nice graphics card. the
clients i don't think use them directly, but would use it via the host i think. I also use visual studio for app dev and i beliebe VS installs a Virtual like machine for windows phone. Can i do this? what would it prevent me from doing that i currently
do? is there a better way to go about this? maybe do the reverse and run the server in hyper-v? thanks

Personally I'd say it depends mainly on what you want to do with the desktop side of your machine. You certainly could install Server 2012 onto your desktop, and from reviews I've seen it's far more suited to being used on a desktop setup than previous server
versions. You still have to do some additional work to enable some of the functionality you'd normally have on a desktop, but which would never be found on a server, but it is more plausible now. There's a bit of a discussion here of the possible issues and
gotchas
http://www.eightforums.com/general-support/7520-windows-r8-windows-2012-server-makes-great-laptop-os.html which cover some of the main things you'd need to do.
If you're just looking to play with Windows Server and the functionality you're looking to use isn't Hyper-V related then I'd probably go with simply making the Windows Server 2012 another instance on your existing setup, eg within Hyper-V on your 8.1 desktop.
There's no real difference between hyper-v on windows 8 and server 2012 so that side of things doesn't make a difference, and windows 8 is quite capable of handling server vm's (I've got 12 VM's running on my windows 8 desktop, and none of them are client
OS's).
The main thing which would dissuade me from installing Server 2012 on a desktop is support for other desktop applications. If you're planning to continue using the machine as a desktop, and especially if you play games on it, you're bound to hit issues
with compatibility at some point. Not legitimate compatibility, more situations where some apps will try to detect the OS you're running, and either not recognise the server OS and refuse to install, or recognise it and refuse to install as they're only designed
/ licenced to be install on a client OS. Some apps which are free to use on a client installation for instance require a licence for use on a server (since it's assumed to be commercial installation).

Failover Cluster on Server 2012 R2

Hi
I`m trying to deploy a Failover Cluster with two servers, both Virtual machines on Vmware, OS- server 2012 r2.
Both servers can see all disks from storage.
For some reason, I keep getting these messages(for all disks) when I run "Validate Configuration" before creating the cluster:
1. Persistent Reservation Registration key 0x1000100b2 for Test Disk X reservation holder node "Servername" was not removed by the call to REGISTER using RESERVATION KEY 0x1000100b2 and SERVICE ACTION RESERVATION KEY 0x1000100c2.
2. Test DiskX does not support SCSI-3 Persistent Reservations commands needed by clustered storage pools that use the Storage Spaces subsystem. Some storage devices require specific firmware versions or
settings to function properly with failover clusters. Contact your storage administrator or storage vendor for help with configuring the storage to function properly with failover clusters that use Storage Spaces.
all other steps come sout with no errors.
I have already deployed another cluster, the same way, and didn`t get any of those messages..
Can anyone give me a hand here?
Thank you!
I

Hi Moriyas,
The VMware has some specific supported scenario when we use failover cluster, please refer the following VMware KB to realize the detail requirement on your current platform.
Microsoft Clustering on VMware vSphere: Guidelines for supported configurations (1037959)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1037959
Microsoft Cluster Service (MSCS) support on ESXi/ESX (1004617)
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004617
I’m glad to be of help to you!
*** This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these
sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use
of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet. ***
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]

The dreaded: The network address is invalid error - SQL 2014 Cluster on Server 2012 R2

Trying to setup an SQL 2014 Failover cluster on Windows Server 2012 R2 (two nodes). Every time I get to the assign a SQL server Network Name piece of the setup I get the following error message:
The given network name is unusable because there was a failure trying to determine if the network name is valid for use by the clustered SQL instance due to the following error: 'The network address is invalid.'
This happens whether I use the Advanced cluster installation procedures or the normal installation. I have tried the following based on anything I can find on the web:
1) Removed the clustered MTDTC role.
2) Deleted the NIC Team (4 1GB NICs). Deleted all but 1 NIC from the server device manager.
3) Shutdown the second node.
4) Lanman Server registry change posted someplace on this forum that does not stick on reboot
None of the above, separately or in combination, has worked to allow SQL 2014 to be installed as a cluster role.
There is no virtual machines added to the cluster. This is not a VMware installation. It is straight Windows 2012 R2 with a two node cluster (setup identically).
Any ideas, suggestions, comments?
Thanks,
-Andrew

Hi Alberto and Lydia,
The cluster was verified, there are only warnings related to a lack of redundant network paths as the cluster verification doesn't recognize a team of 4 nics are redundant. I updated AD to include the permissions detailed in the link Lydia provided,
still no go.
I'm not sure how to attach the installation logs to this message forum other than as text in the message, so here you go:
Summary:
Overall summary:
Final result:                  User cancelled
Exit code (Decimal):           -2068380094
Exit facility code:            1207
Exit error code:               1602
Exit message:                  User has cancelled.
Start time:                    2015-03-24 09:55:25
End time:                      2015-03-24 10:01:04
Requested action:              CompleteFailoverCluster
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine:       SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Replication:     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for FullText:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for DQ:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for RS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for IS:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Conn:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Adv_SSMS:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BC:              SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SSMS:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for ComponentUpdate: SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC:            SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for SNAC_SDK:        SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Writer:          SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for BOL:             SQL Server Setup was canceled before completing the operation. Try the setup process again.
Next step for Browser:         SQL Server Setup was canceled before completing the operation. Try the setup process again.
Cluster properties:
Machine name: SUN-PIE-CS-01
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Machine name: SUN-PIE-CS-02
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Data Quality Client                      1033                 Standard
Edition     12.0.2000.8     No         Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Machine Properties:
Machine name:                  SUN-PIE-CS-01
Machine processor count:       16
OS version:                    Windows Server 2012
OS service pack:
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  Yes
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered Configured
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Database Engine Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            SQL Server Replication
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Full-Text and Semantic Extractions for Search 1033
Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSSQL12.MSSQLSERVER            Data Quality Services
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014      MSSQLSERVER          MSRS12.MSSQLSERVER             Reporting Services - Native
1033                 Standard Edition     12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Basic                 1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Management Tools - Complete              1033                 Standard Edition     12.0.2000.8
No         Yes
SQL Server 2014
Client Tools Connectivity                1033                 Standard Edition
12.0.2000.8     No         Yes
SQL Server 2014
Client Tools Backwards Compatibility     1033                 Standard Edition     12.0.2000.8     No
Yes
SQL Server 2014
Integration Services                     1033                 Standard Edition
12.0.2000.8     No         Yes
Package properties:
Description:                   Microsoft SQL Server 2014
ProductName:                   SQL Server 2014
Type:                          RTM
Version:                       12
SPLevel:                       0
Installation location:         \\sun-server2\data\Software\Microsoft\SQL 2014\x64\setup\
Installation edition:          Standard
User Input Settings:
ACTION:                        CompleteFailoverCluster
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASLOGDIR:                      Log
ASSERVERMODE:                  MULTIDIMENSIONAL
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
CONFIGURATIONFILE:
CONFIRMIPDEPENDENCYCHANGE:     false
ENU:                           true
FAILOVERCLUSTERDISKS:          <empty>
FAILOVERCLUSTERGROUP:          SQL Server (MSSQLSERVER)
FAILOVERCLUSTERIPADDRESSES:    <empty>
FAILOVERCLUSTERNETWORKNAME:    sun-pie-mt-01
HELP:                          false
IACCEPTSQLSERVERLICENSETERMS: false
INDICATEPROGRESS:              false
INSTALLSQLDATADIR:             <empty>
INSTANCENAME:                  MSSQLSERVER
QUIET:                         false
QUIETSIMPLE:                   false
SAPWD:                         <empty>
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSYSADMINACCOUNTS:           <empty>
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
UIMODE:                        Normal
X86:                           false
Configuration file:            C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150324_095524\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Server Replication
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Full-Text and Semantic Extractions for Search
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Data Quality Services
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Reporting Services - Native
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Integration Services
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools Connectivity
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Management Tools - Complete
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Client Tools Backwards Compatibility
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Management Tools - Basic
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Setup Support Files
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Client Connectivity
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Client Connectivity SDK
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Writer
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       Documentation Components
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Feature:                       SQL Browser
Status:                        Failed: see logs for details
Reason for failure:            Setup was canceled for the feature.
Next Step:                     SQL Server Setup was canceled before completing the operation. Try the setup process again.
Rules with failures:
Global rules:
There are no scenario-specific rules.
Rules report file:               C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log\20150324_095524\SystemConfigurationCheck_Report.htm
Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException
    Message:
        User has cancelled.
    HResult : 0x84b70642
        FacilityCode : 1207 (4b7)
        ErrorCode : 1602 (0642)
    Stack:
        at Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
        at Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
        at Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
        at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.<>c__DisplayClasse.<ExecuteActionWithRetryHelper>b__b()
        at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(ActionWorker workerDelegate)

Hyper V on Win Server 2012 throwing false out of space alerts and then intermittently pausing VM's (When Veeam runs)

I have a Windows Server 2012 R2 machine running Hyper V with 6 virtual machines on it. My issue is each of the machines have a status saying they are running out of disk space. Neither of the hard drives on my host are low and none of the VHD's are
low...which as long as they work, not a big deal. The issue that we're running into is when Veeam runs backup jobs some of my VMs will pause. The odd part is we might have 2 to 5 of the 6 machines pause maybe once a month, so it's not happening consistently.
We've contacted Veeam support and they've been useless, they advised we upgrade to Veeam 8 which made no change. We have a number of other virtual hosts with virtual machines being backed up by Veeam that never have this issue... Is this a Hyper V issue or
a Veeam issue? Any advise would be appreciated!

My boss had worked with Veeam on this issue and they tried an upgrade to resolve this, however, it's happened again a number of times in the last week. I went through my logs and I also looked at my storage (Posted below). The servers that paused today are (App4,
FS3, FS4, FS5). App3 and FS1 have also paused before, however, not this time. Phone1 has not paused. So our total usage is 2.2 TB of a 2.45 TB drive. All the VHD files are stored on the virtual host D drive. I'm not understanding the status warnings, some
say they are running out of space when there is indeed enough space on both the VHD files for C’s and D’s.
I reached out to a vendor/contactor we use for complex issues and I posted his advise below, however, it's not making sense to me... We do not use snap shots and as of this moment we're not at a low space threshold. Is the issue as simple
as we have too much on this server and the Veeam backups are triggering the host's D drive to go below the low space threshold?
"When I setup virtual servers, I setup fixed disk and fixed memory usage, this keeps the memory cache from fluctuating and I limit the disks to only what the server needs and then expand them as needed. Fixed disk perform
better and it is a good way to avoid fragmentation and out-of-control dynamic disks. At this point, your issue is going to be freeing up space on the D: drive of the Hyper-V server – your snapshot logs (and possibly someday replication change logs) are going
to continue reach the disk space limit. There are some registry changes that some suggest to disable the safeguard, but remember, this is a safeguard as the server need free space on the Hyper-V server host to operate."
Server Specs
App3 - Dynamic - C: 47.36 GB used of 50 - D: 250 GB used of 250 - No status warning
App4 - Dynamic - C: 193.12 used of 200 - D: - Disk running out of space
FS1 - Dynamic - C: 55.4 used of 100 - D: 1000 used of 1000 - No status warning, however, the D drive is out of space?
FS3 - Dynamic - C: 55.62 used of 60 - D: - No status warning
FS4 - Dynamic - C: 19.1 used of 60 - D: 32.19 used of 100 - Disk running out of space
FS5 - Dynamic - C: 18.44 used of 127 - D: 74.04 used of 127 - Disk running out of space
Phone1 - Fixed - C: 127 - No status warning
Event Errors...
'FS5' has been paused because it has run out of disk space on 'D:\VM Drives\FS5\'. (Virtual machine ID 15D4F67C-562A-4AB6-AB72-47E8722CCB85)
'FS1' has been paused because it has run out of disk space on 'D:\vm drives\FS1\Virtual Hard Disks\'. (Virtual machine ID 304B2CAE-C9D2-401E-970B-F75874F6CF08)
^FS1 was not paused when I went in to start them this morning...

Isolated Lab on Hyper-V (Prod) with SCVMM 2012 R2

Hello,
I currently would like to make littla test lab on my Hyper-V 2012 R2 with SCVMM 2012 R2 at work.
Knowing that there is DC in prod on this Hyper-V, I would like to isolate the lab from the prod without loosing internet access.
I did try with a server gateway but no connectivity and a lot of errors.
It is so easy to do witout VMM that I can't understand why it is so difficult now.
Please let me know.
Ollie

You should create a new virtual switch of the type "internal" where the VMs can communicate with the hosts through this switch, and vice versa. Then it will be isolated from the production DC.
-kn
Kristian (Virtualization and some coffee: http://kristiannese.blogspot.com )

Having trouble switching from Core to GUI with Server 2012...

Hello,
I am currently in the early stages of studying for the MCSA - Windows Server 2012 R2 and I'm playing around with an Eval copy of Windows Server 2012 R2 DataCenter. I have two separate installs where one is the Full - GUI install and the other is Server
Core. I've learned in my studies that it is possible to switch back and forth between Core and GUI through Powershell cmdlets.
Right now I'm trying to switch from Server Core to GUI and I'm using the following Powershell command:
       Install-WindowsFeature Server-Gui-Mgmt-Infra, Server-Gui-Shell
It starts off like it's going to work but then after about 68% of the way through, I get this:
     Install-WindowsFeature : The request to add or remove features on the specified server failed.
     Installation of one or more roles, role services, or features failed.
     The source files could not be downloaded.
     Use the "source" option to specify the location of the files that are required to restore the feature. For more
     information on specifying a source location, see XXXXXX. Error: 0x800f0906
     At line:1 char:1
     + Install-WindowsFeature Server-Gui-Mgmt-Infra, Server-Gui-Shell
     + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature],
          Exception
         + FullyQualifiedErrorId :       DISMAPI_Error__Cbs_Download_Failure,Microsoft.Windows.ServerManager.Commands.AddWindowsF
   eatureCommand
Any ideas? I installed this Server Core image on a Hyper-V Virtual Machine (using Generation 2), allocating 4GB RAM and 65GB HDD space. I haven't done anything with .Net Framework and I haven't configured the network at all.
Any advice would be greatly appreciated.

Hi SLONER,
You need use the -source option on a non-Internet connected machine.
PLease try the script below:
Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart –Source c:\mountdir\windows\winsxs
And follow this thread:
PowerShell to Add GUI to Server Core (ServerCore-FullServer)
I hope this helps.

SQL Server 2012 DB Engine does not start (clean install with server 2012 and 2008 R2)

I'm trying to do clean installation of SQL server 2012 on Server 2012 (which is runnning as a VM on ESX server) and getting this "wait on the DB engine recovery failed" message. Initially, I though this issue was related to some permission issues
but changing the permission or service accounts didn't help. I'm not seeing any "denied" messages in the log files either. Even with Server 2008 R2 (clean built VM), the installation gives the exactly the same error messages.
My setup is purely for test purpose; so, the security is not a concern. Can someone help or give me a clue where to look?
(Summary)
Overall summary:
Final result: Failed: see details below
Exit code (Decimal): -2061893606
Start time: 2014-05-28 17:12:12
End time: 2014-05-28 17:19:47
Requested action: Install
Setup completed with required actions for features.
Troubleshooting information for those features:
Next step for SQLEngine: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Machine Properties:
Machine name: WIN-1V3VKPV5Q19
Machine processor count: 1
OS version: Future Windows Version
OS service pack:
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No
Product features discovered:
Product Instance Instance ID Feature
Language Edition Version Clustered
Package properties:
Description: Microsoft SQL Server 2012 Service Pack 1
ProductName: SQL Server 2012
Type: RTM
Version: 11
Installation location: E:\x64\setup\
Installation edition: Evaluation
Slipstream: True
SP Level 1
Patch Level: 11.1.3128.0
Product Update Status:
Success: KB 2674319, KB 2793634
Product Updates Selected for Installation:
Title: Service Pack 1
Knowledge Based Article: KB 2674319
Version: 11.1.3000.0
Architecture: x64
Language: 1033
Title: SQL Server 2012 SP1 GDR Product Update
Knowledge Based Article: KB 2793634
Version: 11.1.3128.0
Architecture: x64
Language: All
Update Source: MU
User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: false
AGTSVCACCOUNT: NT Service\SQLAgent$TESTDB
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSERVERMODE: MULTIDIMENSIONAL
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: <empty>
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Automatic
CLTCTLRNAME: <empty>
CLTRESULTDIR: <empty>
CLTSTARTUPTYPE: 0
CLTSVCACCOUNT: <empty>
CLTSVCPASSWORD: <empty>
CLTWORKINGDIR: <empty>
COMMFABRICENCRYPTION: 0
COMMFABRICNETWORKLEVEL: 0
COMMFABRICPORT: 0
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140528_170909\ConfigurationFile.ini
CTLRSTARTUPTYPE: 0
CTLRSVCACCOUNT: <empty>
CTLRSVCPASSWORD: <empty>
CTLRUSERS: <empty>
ENABLERANU: false
ENU: true
ERRORREPORTING: false
FEATURES: SQLENGINE
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: <empty>
HELP: false
IACCEPTSQLSERVERLICENSETERMS: true
INDICATEPROGRESS: false
INSTALLSHAREDDIR: C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: C:\Program Files\Microsoft SQL Server\
INSTANCEID: TESTDB
INSTANCENAME: TESTDB
ISSVCACCOUNT: NT AUTHORITY\Network Service
ISSVCPASSWORD: <empty>
ISSVCSTARTUPTYPE: Automatic
MATRIXCMBRICKCOMMPORT: 0
MATRIXCMSERVERNAME: <empty>
MATRIXNAME: <empty>
NPENABLED: 0
PID: *****
QUIET: false
QUIETSIMPLE: false
ROLE: <empty>
RSINSTALLMODE: DefaultNativeMode
RSSHPINSTALLMODE: DefaultSharePointMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: <empty>
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: SQL
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: NT Service\MSSQL$TESTDB
SQLSVCPASSWORD: <empty>
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: WIN-1V3VKPV5Q19\Administrator
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: false
TCPENABLED: 1
UIMODE: Normal
UpdateEnabled: true
UpdateSource: MU
X86: false
Configuration file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140528_170909\ConfigurationFile.ini
Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
Reason for failure: An error occurred during the setup process of the feature.
Next Step: Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
Component name: SQL Server Database Engine Services Instance Features
Component error code: 0x851A001A
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
Error help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3128.0&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026&EvtType=0xD15B4EB2%400x4BDAF9BA%401306%4026
Feature: SQL Browser
Status: Passed
Feature: SQL Writer
Status: Passed
Feature: SQL Client Connectivity
Status: Passed
Feature: SQL Client Connectivity SDK
Status: Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20140528_170909\SystemConfigurationCheck_Report.htm
(Error Log)
2014-05-28 17:17:26.64 spid8s 0 transactions rolled back in database 'msdb' (4:0). This is an informational message only. No user action is required.
2014-05-28 17:17:26.73 spid9s Starting up database 'model'.
2014-05-28 17:17:28.24 spid9s Error: 9004, Severity: 23, State: 6.
2014-05-28 17:17:28.24 spid9s An error occurred while processing the log for database 'model'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.
2014-05-28 17:17:28.24 spid9s SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.
(Details)
(01) 2014-05-28 17:17:28 Slp: Exception type: Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException
(01) 2014-05-28 17:17:28 Slp: Message:
(01) 2014-05-28 17:17:28 Slp: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
(01) 2014-05-28 17:17:28 Slp: HResult : 0x851a001a
(01) 2014-05-28 17:17:28 Slp: FacilityCode : 1306 (51a)
(01) 2014-05-28 17:17:28 Slp: ErrorCode : 26 (001a)
(01) 2014-05-28 17:17:28 Slp: Data:
(01) 2014-05-28 17:17:28 Slp: SQL.Setup.FailureCategory = ConfigurationFailure
(01) 2014-05-28 17:17:28 Slp: WatsonConfigActionData = INSTALL@CONFIGRC@SQL_ENGINE_CORE_INST
(01) 2014-05-28 17:17:28 Slp: WatsonExceptionFeatureIdsActionData = System.String[]
(01) 2014-05-28 17:17:28 Slp: Stack:
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart(Process processSql)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceSCM.StartSqlServer(String[] parameters)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.ConfigSQLServerSystemDatabases(EffectiveProperties properties, Boolean isConfiguringTemplateDBs, Boolean useInstallInputs)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineDBStartConfig.DoCommonDBStartConfig(ConfigActionTiming timing)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
(01) 2014-05-28 17:17:28 Slp: at Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
(01) 2014-05-28 17:17:28 Slp: Watson Bucket 1
Original Parameter Values
(01) 2014-05-28 17:17:28 Slp: Parameter 0 : SQL Server 2012@RTM@
(01) 2014-05-28 17:17:28 Slp: Parameter 1 : Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart
(01) 2014-05-28 17:17:28 Slp: Parameter 2 : Microsoft.SqlServer.Configuration.SqlEngine.SqlServerServiceBase.WaitSqlServerStart
(01) 2014-05-28 17:17:28 Slp: Parameter 3 : Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 4 : Microsoft.SqlServer.Configuration.SqlEngine.SqlEngineConfigException@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
(01) 2014-05-28 17:17:28 Slp: Parameter 6 : INSTALL@CONFIGRC@SQL_ENGINE_CORE_INST
(01) 2014-05-28 17:17:28 Slp:
Final Parameter Values
(01) 2014-05-28 17:17:28 Slp: Parameter 0 : SQL Server 2012@RTM@
(01) 2014-05-28 17:17:28 Slp: Parameter 1 : 0xD15B4EB2
(01) 2014-05-28 17:17:28 Slp: Parameter 2 : 0xD15B4EB2
(01) 2014-05-28 17:17:28 Slp: Parameter 3 : 0x4BDAF9BA@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 4 : 0x4BDAF9BA@1306@26
(01) 2014-05-28 17:17:28 Slp: Parameter 5 : SqlEngineDBStartConfigAction_install_configrc
(01) 2014-05-28 17:17:28 Slp: Parameter 6 : 0x9C5770A6

Hi Nababoya:
As you are telling this is a test installation process...
In the logs i m seeing the error message "An error occurred while processing the log for database 'model'. If possible, restore from backup. If a backup is not available, it might be necessary to rebuild the log.".
1) If the SQL Services was installed successfully and SQL Service was not able to start because of model database issue...
    1.1) If you have model database SQL back file, start the SQL Server in single user mode with minimum configuration and try to restore MODEL database
http://blogs.msdn.com/b/sqlserverfaq/archive/2011/05/11/inf-hey-my-sql-server-service-is-not-starting-what-do-i-do.aspx
    1.2) If you don't have backups., try to rebuild the system databases but make sure that you are not losing any data critical data on master and SQL Jobs on MSDB
http://msdn.microsoft.com/en-us/library/dd207003%28v=sql.110%29.aspx#RebuildProcedure
2) As if this is a new installation try to repair the instance with the help of setup media file
3) If the repair option fails., the last option wipe out the complete SQL Server components from Services.msc and Registries and start new installation.
4) Make sure when you are doing un-installation all the required SQL Server components on services.msc should be in stop state.
Hope this helps and let me know any questions...
Thanks,
Thanks, Satish Kumar. Please mark as this post as answered if my anser helps you to resolves your issue :)

Hyper-v cluster with core switch downtime... what to do?

Is there a way to essentially "pause" the hyper-v cluster and keep things running but do NOT attempt to failover anything for any reason?
We have one Procurve 5412zl switch with two c7000 enclosures. In each c7000 enclosure there are two switches that connect all the blade servers within the enclosure. Those two switches are interconnected internally so they can communicate within the enclosure.
So if the core switch goes down the hyper-v servers in the same c7000 enclosure can still communicate but they will be seperated from the others in the other enclosure.
So we have 4 hyper-v servers in one enclosure and 3 in another. If i disconnect the core switch i'm wondering what will happen (if I reboot the switch which is what I need to do).
How can I avoid having to shut down everything for this and just tell hyper-v cluster to not do anything when the network is lost?

Hi Quadrantids,
" to essentially "pause" the hyper-v cluster and keep things running but
do NOT attempt to failover anything for any reason"
Based on my understanding you need to keep cluster running on the same C7000 enclosure , in another words before you cut the connection between the C7000 enclosures you may migrate VMs to same enclosure to keep running (I assume that the
storage will not be affected by the restart ).
Best Regards
Elton Ji
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.

SSIS error working with Server 2012

Hi,
I have a class library that creates, delete, update ssis packages programatically.
What could be the reason for an error message that I get in front of the server 2012. Against a server 2008 It works good.
Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSExecutables100'. This operation failed because the QueryInterface call on the COM component
for the interface with IID '{0FAC005E-5ABD-4D1E-9B21-18F3DE622B24}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).
thanks

It looks like your references need to be updated for 2012.
David
David http://blogs.msdn.com/b/dbrowne/

Requirement to have 3 hyper-v in Windows Server 2012 R2 Std

Hi,
I want to configure three Hyper-V in my Windows Server 2012 R2 Standard.
1. ERP System
2. Mail Server
3. AD
What requirement or license do I need to have?
Thank You.

as per my knowledge if you want to use 3 Application you can run one application on Host and other 2 Application on virtual instances.
that is not accurate.
As per MS documentation, if you run two virtual instances, the host (hypervisor) may only be used for hypervisor functions, it may not be used for applications.
http://www.microsoft.com/licensing/about-licensing/briefs/virtual-licensing.aspx
Windows Server 2012 R2 Standard
All physical processors need to be licensed. Each license covers up to two physical processors.
You may run the server software in one physical OSE and in up to two virtual OSEs for each license you assign. If you run all of the permitted instances the instance in the physical OSE can only be used to manage the virtual OSEs.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Building a Hyper-V Cluster with Server 2012 R2

Similar Messages

Maybe you are looking for