Multiple Hyper-V 2012 R2 servers to access a since ISCSI target

A couple years ago the community helped me configure a CentOS file server to connect to my VMWare and HyperV Servers for the purpose of backup. At the time I created 2 LVM devices, one to connect to Esxi via NFS, and one to connect to HV via ISCSI. This has worked GREAT!I have converted almost all my production environment to HV. I had to of course rebuild the arrays and make the larger one ISCSI rather than NFS. I just noticed that file the file structure of the connected HV drives is not the same. I have (3) HV Servers connected to the same ISCSI target which resides on the CentOS file server. When you view the connected drives, the same target has different files on it from different HV Hosts. Prior to rebuilding the arrays, the ISCSI target worked as intended. I suspect that I missed a step during the rebuild. The drives were...
This topic first appeared in the Spiceworks Community

Hello,
I have installed VMM 2012 R2, this is also not allowing me to add and manage Server 2012 R2 hosts. However it is perfectly able to manage Server 2008 host.
It gives following error when tried to add Server 2012 R2 hosts:
Error (2916)
VMM is unable to complete the request. The connection to the agent windows2012.test.com was lost.
WinRM: URL: [http://windows2012.test.com:5985], Verb: [INVOKE], Method: [Associate], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/AgentManagement]
Unknown error (0x80338012)
Recommended Action
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTPS traffic.
This problem can also be caused by WMI service crash. Ensure that KB 982293 (http://support.microsoft.com/kb/982293) is installed on the machine if it is running Windows Server 2008 R2.
If the error persists, reboot windows2012.test.com and then try the operation again.
Any suggestions please?

Similar Messages

Virtual Machine Manager to manage Hyper-V 2012 R2 Servers

Hi,
I am trying to create an environment wherein I have few Hyper-V 2012 R2 hosts, Windows Server 2012 hosts, and Windows Server 2008 hosts. All are registered to a AD server.
On Windows Server 2012 host, I have created a virtual machine on which System Center Virtual Machine Manager 2012 SP1 is running. This Virtual Machine Manager is perfectly able to manage Windows Server 2008 hosts.
However when tried to add Windows Server 2012 hosts and Hyper-V 2012 R2 hosts, it gives the following error:
Error (2916)
VMM is unable to complete the request. The connection to the agent windows2012.test.com was lost.
WinRM: URL: [http://windows2012.test.com:5985], Verb: [INVOKE], Method: [Associate], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/AgentManagement]
Unknown error (0x80338012)
Recommended Action
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTPS traffic.
This problem can also be caused by WMI service crash. Ensure that KB 982293 (http://support.microsoft.com/kb/982293) is installed on the machine if it is running Windows Server 2008 R2.
If the error persists, reboot windows2012.test.com and then try the operation again.
Checked:
> WS-Management service is running
> VMM agent got installed
Questions:
1. Whether System Center 2012 SP1 - Virtual Machine Manager is compatible to manage Hyper-V Sever 2012 and Windows 2012 R2 Server.
2. What is the latest version of VMM to manage Hyper-V Sever 2012 and Windows 2012 R2 Server.

Hello,
I have installed VMM 2012 R2, this is also not allowing me to add and manage Server 2012 R2 hosts. However it is perfectly able to manage Server 2008 host.
It gives following error when tried to add Server 2012 R2 hosts:
Error (2916)
VMM is unable to complete the request. The connection to the agent windows2012.test.com was lost.
WinRM: URL: [http://windows2012.test.com:5985], Verb: [INVOKE], Method: [Associate], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/AgentManagement]
Unknown error (0x80338012)
Recommended Action
Ensure that the WS-Management service and the agent are installed and running and that a firewall is not blocking HTTPS traffic.
This problem can also be caused by WMI service crash. Ensure that KB 982293 (http://support.microsoft.com/kb/982293) is installed on the machine if it is running Windows Server 2008 R2.
If the error persists, reboot windows2012.test.com and then try the operation again.
Any suggestions please?

Hyper-V 2012 R2 roles, access denied, failed to connect to service, AzMan....

Hi All,
I have followed dozens of tutorials to set up roles for Hyper-V, but I keep coming up short. I have no problem managing the five domain-joined 2012 R2 Core Hyper-V servers we have remotely from my Windows 8.1 PC, but I have a lab box I would like to grant
specific permissions to some Help Desk users on.
The key tutorial I have followed is from John Howard (http://blogs.technet.com/b/jhoward/archive/2008/04/01/part-4-domain-joined-environment-hyper-v-remote-management-you-do-not-have-the-requested-permission-to-complete-this-task-contact-the-administrator-of-the-authorization-policy-for-the-computer-computername.aspx),
but it still does not allow a non-admin account to use Hyper-V Manager remotely. Without his tutorial, I get access denied with my "TestUser" account. After following his steps, Hyper-V Manager appears to connect to the server, but says "The
Virtual Machine Management service is not available." Even using his HVRemote with the /show flag, everything shows as PASSED.
Digging deeper, I see dozens of failed audit Event Viewer logs saying "TestUser" is requesting READ to Service Control Manager. That sent me searching, and I found
http://arnoutboer.nl/weblog/?p=300 and http://msdn.microsoft.com/en-us/library/windows/desktop/aa374928(v=vs.85).aspx.
After granting "AU" (Authenticated Users) every permission resembling "read", Hyper-V Manager now shows "There are no virtual machines to show" (or something along those lines); even though I know there are about 30 VMs on this
host. I try to create a new VM (out of curiosity, and now that those options actually appear), and I get permission denied immediately after the create VM wizard pops up.
Why is this such a convoluted process? I would appreciate any help creating Roles for Hyper-V 2012.
Thank you in advance!

Hi Eric (cool name BTW!)
Putting them in Hyper-V Administrators is definitely not an option.
I absolutely believe Microsoft would do something to push you into buying their software; just as we had to purchase Windows 8.1 Pro to remotely manage our 2012 R2 servers. However, as far as I am seeing, AzMan is still in 2012 R2. Whether it works or not
is another story, but AzMan.msc is still there and I can run it on any of our 2012 R2 GUI installs.
Actually just found this:
http://technet.microsoft.com/en-us/library/dn303411.aspx. According to that, it has not yet been removed, but it has been deprecated. From what I am seeing, the Hyper-V portion of it is definitely broken.
I will look into the remote endpoints solution you mentioned. Thank you for the suggestion. I just recently took the plunge into learning C++, so maybe a Hyper-V manager of sorts will be an app to
attempt to write, haha.
Eric Christensen

Hyper-V 2012 R2, integration services issue on multiple VMs

Hello,
I came to you because we encounter a technical issue on one of our Hyper-V (2012 R2).
Our backup (Veeam backup in last version) are still failing with error :
Guest processing skipped (check guest OS VSS state and integration components version)
After checking integration service states of those VMs on the Hyper-V, we get this result :
Get-VM | ft Name, IntegrationServicesVersion
Name
IntegrationServicesVersion
xxx-3REP-01
6.3.9600.16384
xxx-ADMIN02
xxx-BAK02
6.3.9600.16384
xxx-MAIL-01
xxx-SCOM-01-1
6.3.9600.16384
xxx-SQL02
6.3.9600.16384
xxx-VC-01
6.3.9600.16384
xxx-VD01
xxx-VMM02
xxx-VMM03
xxx-WEB01
Get-VMIntegrationService xxx-vmm02 | Select Name,OperationalStatus
Name
OperationalStatus
Time Synchronization
{Ok}
Heartbeat
{Ok, Ok}
Key-Value Pair Exchange                                  {LostCommunication}
Shutdown
{LostCommunication}
VSS
{LostCommunication}
Guest Service Interface                                     {LostCommunication}
I already try to disable, then enable the operationalStatus :
Disable-VMIntegrationService -VMName MyVM -Name VSS,Shutdown,"Key-Value Pair Exchange"
Enable-VMIntegrationService -VMName MyVM -Name VSS,Shutdown,"Key-Value Pair Exchange"
The status is OK, but If I retry my backup I have the same error.
So, is there a way to reinstall integration service component without rebooting ?
Many thanks for your help.

On the Windows VMs that are not 2012 R2, insert the Integration media ISO, install it, and reboot.
When all is done, run this:
# Input:
$HVHost = "YourHostHere"
# Processing:
$VMInfo = @()
Get-VM -ComputerName $HVHost | where { $_.State -eq "Running" } | % {
$Info = New-Object -TypeName psobject
$Info | Add-Member "VMName" $_.Name
$Info | Add-Member "IntegrationServicesVersion" $_.IntegrationServicesVersion
$OS = Invoke-Command -ComputerName $_.Name { (Get-CimInstance Win32_OperatingSystem).version } -ErrorAction SilentlyContinue
$Info | Add-Member "OSVersion" $OS
$VMInfo += $Info
# Output:
$VMInfo | Out-GridView
$VMInfo | FT -AutoSize
$VMInfo | Export-Csv .\VMInfo.csv -NoTypeInformation
Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable) _________________________________________________________________________________
Powershell: Learn it before it's an emergency http://technet.microsoft.com/en-us/scriptcenter/powershell.aspx http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx

Can I assign several physical storage locations for each virtual machine when using the replication-feature from Hyper-V 2012 R2?

Hi everyone,
I have 2x physical servers running Hyper-V 2012 R2. Each hosts several virtual machines. The VHDs of the VMs are stored on several dedicated physical disks to have a performance boost. For exampe if VM A has two VHDs attached I made sure that the VHDs are
on different physical disks to have them not slow-down each other in case of intensive disk accesses.
So far so good. I was looking forward to the replication-feature. The idea is to have the two physical servers have their primary running VMs being replicated to the other physical server and vice-versa. I was hoping to have the chance to choose for each
individual VM where the replicated VHD will be stored. But instead I can only see the one location/path which is configured in Hyper-V Manager when I activate the replication-feature on the server.
Is there by any chance a way how to select the storage location for each VHD/VM if using the replication-feature of Hyper-V 2012 R2?
Thanks in advance.
Cheers,
Sebastian

Secondly, you could replicate different VMs to different storage locations to perform some of the disk balancing you are trying to perform. Lastly, you could copy the vhd file to a different location
before starting the VM.
.:|:.:|:. tim
Hi Tim,
thanks for the reply. Sorry, but I had some other tasks to take care of, so I wasn't paying enough attention to this thread.
The part I quoted from your reply sounds exactly like the action I'd like to perform, but as you pointed out before this should not be possible.
How can I perform the action (replicating each VM to a storage location) as you mentioned secondly? To sum it up again:
2x physical machines carrying severel HDDs
8+ VMs spread to run on the 2x servers
when setting up replication I can only set the storage-location from server A on B and vice versa B on A
Thanks again for your reply.
Cheers,
Sebastian

VMs on Hyper-V 2012 R2 are shutting down automatically

Hello Guys!
I'm having a huge problem in my Hyper-V 2012 R2 environment. Yesterday, 9 of 40 VMs were shutdown automatically, and so, caused a downtime problem to my customers in the business hours.
I checked in the Event Viewer (Application / System / Microsoft - Windows - Hyper) of the Host and VM but I couldn't locate any log related to this unexpected shutdown.
It occurred twice yesterday, the first in the morning and the second in the afternoon. I'm afraid that this issue can happen again. I've tried to locate some logs to identify this problem, but no luck here.
My question: Is there any other place where it can help me in this troubleshooting to find the root cause?
Obs: All the VMs are licensed / activated.
Obs2: The VMs are Win 2008 R2 Std
Leandro Soares - MCP/MCSA/MCTS

Hello Brian!
The customers doesn't have access using the RDP / ICA. The role machines is web servers.
In the VMs I can find only the following log:
Log Name: System
Source: Microsoft-Windows-Kernel-Power
Date: 24/06/2014 11:09:04
Event ID: 41
Task Category: (63)
Level: Critical
Keywords: (2)
User: SYSTEM
Computer: xxx
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
But on the Host Hyper-V I cannot find any error related to this failure as I described in this thread.
Leandro Soares - MCP/MCSA/MCTS

Can't connect to the Hyper-V manager after upgrading to Windows Hyper-V 2012 R2

I have some Hyper-V server based on the free version (Windows Hyper-V 2012). I want to upgrade to the new version (Windows Hyper-V 2012 R2). So I begin to test it with
an already working server (aka I was able to totally manager the server remotely without problem) and so upgrade it to the R2.
After the upgrade, remote management and Hyper-V manager does not work anymore. So I redo my usual configuration steps (enable remote management, open firewall, uses
latest hvremote.wsf, etc.). I was able to regain access to Computer Manager but not the Hyper-V manager which still can't connect at all. I can't access the Task Scheduler too without having a lot of XML error like "The task XML contains a value which
is incorrectly formatted or out of range" (see below for screenshot).
Is there a new step to do to be able to manage Hyper-V 2012 R2 from a Windows 7 computer?
It's not a network problem as I can access RDP and MMC Computer Manager.
To be sure the problem is coming from the R2, I have taken an old computer, install Windows Hyper-V 2012, do my usual configuration step, and
tada: it works perfectly. I can access the Hyper-V manager from my client.
Technical details:
- Client is a Windows 7 SP1 x64 English member of a domain with latest RSAT (Windows6.1-KB958830-x64-RefreshPkg.msu).
- Servers are in a workgroup (not a domain's member). And no, I can't add them to the same domain as the client.

HI,
Can we upgrade HyperV 2012 to hyper v 2012 R2.
Thanks
Atul

Server 2012 R2 iSCSI Target - Multiple targets per iSCSI Virtual Disk with CHAP

Scenario I am trying to achieve is this:
Windows Server 2012 R2 serves as iSCSI Target configured to have 1 iSCSI Virtual Disk
2 Hyper-V servers connecting to this target with iSCSI Inistator and have multiple targets for that iSCSI Virtual Disk using CHAP
**These 2 are nodes in fail over cluster, this iSCSI is added as a CSV.
Issue that I have, is that you can only have 1 target per iSCSI Virtual Disk
Both Hyper-V servers can connect to this LUN without issue when I add both initiator IDs to the target, but once I enable CHAP, you can only put one initiator ID in the "Name" field, so I can only connect from 1 Hyper-V server.
Do you know of a way around this?

From my understanding, "chaptest" is a single target, my goal was to make 2 targets to the same iSCSI virtual disk.
So if you were to right click the iSCSI virtual disk that "chaptest" is assigned to and click "Assign iSCSI Veritual Disk...", then select "New iSCSI Target, and proceed with the wizard it removes the "chaptest" target
and adds the new one just created.
My goal was to have 2 targets to 1 iSCSI VD, but seeing your screenshot, with 2 initiators connected, that goal doesn't seem needed anymore.
I was under the impression that the "User name" = the iscsi initiator IQN name, which had to be unique. That is why I thought I would need 2 targets.
Thanks

Add iSCSI LUN to Multiple Hyper-V Cluster Hosts?

Is there a way to connect multiple Hyper-V hosts to a CSV LUN without manually logging into each and opening the iSCSI Initiator GUI?

Is there a way to connect multiple Hyper-V hosts to a CSV LUN without manually logging into each and opening the iSCSI Initiator GUI?
Here's a good step-by-step guide on how to do everything you want using just PowerShell. Please see:
Configuring iSCSI storage for a Hyper-V Cluster
http://www.hypervrockstar.com/qs-buildingahypervcluster_part3/
This part is should be of a particular interest of yours. See:
Connect Nodes to iSCSI Target
Once the target is created and configured, we need to attach the iSCSI initiator in each node to the storage. We will use MPIO to
ensure best performance and availability of storage. When we enable the MS
DSM to claim all iSCSI LUNs we must reboot the node for the setting to take affect. MPIO is utilized by creating a persistent connection to the target for each data NIC on the target server and from all iSCSI initiator NICs on our hyper-v
server. Because our hyper-v servers are using converged networking, we only have 1 iSCSI NIC. In our example resiliency is provided by the LBFO team we created in the last video.
PowerShell Commands
1
2
3
4
5
6
7
8
9
Set-Service -Name
msiscsi -StartupType Automatic
Start-Service msiscsi
#reboot requres after claim
Enable-MSDSMAutomaticClaim -BusType
iSCSI
Set-MSDSMGlobalDefaultLoadBalancePolicy
-Policy RR
New-IscsiTargetPortal –TargetPortalAddress 192.168.1.107
$target = Get-IscsiTarget
-NodeAddress *HyperVCluster*
$target| Connect-IscsiTarget
-IsPersistent $true -IsMultipathEnabled
$true -InitiatorPortalAddress
192.168.1.21 -TargetPortalAddress 10.0.1.10
$target| Connect-IscsiTarget-IsPersistent$true-IsMultipathEnabled$
You'll find a reference to "Connect-IscsiTarget" PowerShell cmdlet here:
Connect-IscsiTarget
https://technet.microsoft.com/en-us/library/hh826098.aspx
Set of samples on how to control MSFT iSCSI initiator with PowerShell could be found here:
Managing iSCSI Initiator with PowerShell
http://blogs.msdn.com/b/san/archive/2012/07/31/managing-iscsi-initiator-connections-with-windows-powershell-on-windows-server-2012.aspx
Good luck and happy clustering :)
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.

Hyper-v 2012 r2 slow throughputs on network / live migrations

Hi, maybe someone can point me in the right direction, I have 10 servers 5 Dell r210s and 5 Dell R320's, I have basically converted these servers to standalone hyper-v 2012 servers, so there is no clustering on any at the moment.
Each server is configured with 2 1Gb nics teamed via a virtual switch, now when I copt files between server 1 and 2 for example I see 100MBs throughput, but if I copy a file to server 3 at the same time the file copy load splits the 100MBs throughput between
the 2 copy processes. I was under the impression if I copied 2 files to 2 totally different servers the load would basically be split across the 2 nics effectively giving me 2Gbs throughput but this does not seem to be the case. I have played around with tcpip
large send offloads, jumbo packets, disabled vmq on the cards, they are broadcoms. :-( but it doesn't really seem to make a difference with all of these settings.
The other issue is If I live migrate a 12Gb vm machine running only 2gb ram, effectively just an o/s it takes between 15 to 20 minutes to migrate, I have played around with the advanced settings, smb, compression, tcpip not real game changers, BUT if I shut
town the vm and migrate it, it takes, just under 3 and a half minutes to move across.
I am really stumped here, I am busy in a test phase of hyper-v but cant find any definitive documents relating to this stuff.

Hi Mark,
The servers (hyper-v 2012 r2) are all basically configured with ssvmm2012R2 where they all have teamed 1Gb pNics, into a virtual switch, then there are vNics for the Vmcloud, live migration etc. The physical network is 2 Netgear Gs724T switches which
are interlinked and each servers 1st nic is plugged into the switch1 and the second nic is plugged into the switch2.See Below Image) The hyper-v port is set to independent Hyper-v load balancing.
The R320 servers are running raid 5 sas drives, the R210s have 1Tb drives mirrored. The servers all are using DAS storage, we have not moved to looking at using iscsi and san is out the question at the moment.
I am currently testing between 2x 320s and 2x R210s, I am not copying data to the vm's yets, I am basically testing the transfer between the actual hosts at the moment by copying a 4Gb file manually, After testing the live migrations I decided to test to
see the transfer rates between the servers first, I have been playing around with the offload settings and rss, what I don't understand is yesterday, the copy between the servers was running up to 228Mbs ie (using both nics) when copying
the file between the servers, and then a few hours later it only was copying at 50/60Mbs, but its now back at 113Mbs seemingly to be only using one nic.
I was under the impression if you copy a file between 2 servers the nicks could use the 2gb bandwidth, but after reading many posts they say only one nic, so how did the copies get up to 2Gb yesterday. Then again if you copy files between 3 servers, then
each copy would use one nic, basically giving you 2Gbs, but this is again not being seen.
Regards Keith

Hyper-V 2012 R2 Remote Management with Windows 8.1 using Microsoft Account (Workgroup)

Hello,
I've set up a Hyper-V 2012 R2 Server and tried to manage it from a Windows 8.1 with a Microsoft Account. Everything is in the same workgroup. After many searches, the only way is set up the server for remote access, install RSAT and log on with an Administrator
account from the server in Server Manager console.
So, this situation generates a question: since it's impossible to set up a Microsoft Account in Hyper-V server as a local user, it's impossible to use "the same account and password" way to establish a link between server and desktop? I must use
a remote account for connection? Why Windows 8.1 local account and online account can't be merged as a single account?
By the way, there are some consoles that cmdkey doesn't work, so it's not an option.
Best regards.
Herleson Pontes MCT | MCITP | MCSA | MCTS | MCP | MOS http://www.herlesonpontes.com.br – [email protected]

I have not fully tried this myself but I know this:
A microsoft account can only be added to Server as a User, and only after Desktop Experience has been added. This is also how you enable the MSFT Store on Server.
This also requires a Full install of Server and is not possible on the free Hyper-V Server SKU.
But, the legacy Server Manager console that Hyper-V Manager is built on has no concept of this new user account type. And neither does Kerberos (the default security mechanism).
So, my guess is that the best you can do is treat it the same as any workgroup machines.
If you use Azure AD and sync your domain credentials, you have the password equivalent. But you still require some AD in the middle. This is simply the current state of affairs.
Brian Ehlert
http://ITProctology.blogspot.com
Learn. Apply. Repeat.

Moving VMs From One Hyper-v 2012 R2 to Another Hyper-v 2012 R2

Hi everyone, was hoping for some help in something I am confused about
Currently I have SERVER1 running hyper-v 2012 R2
I want to move all my VMs (around 20) to SERVER2 also running Hyper-v 2012 R2
But I am confused on the best way to do this
1) should I just click on "MOVE" on SERVER1 to move to SERVER2?
2) Should I do an export and then import
3) should I setup replication from Server1 to Server2 and then do a failover?
4) or should I shut the VM down, copy the VHDX file and then create a new VM and use that VHDX
I just want to be cautious and use the best method to ensure it goes smooth and not worry about any corruption. Can anyone offer some advice?
thanks

Hi everyone, was hoping for some help in something I am confused about
Currently I have SERVER1 running hyper-v 2012 R2
I want to move all my VMs (around 20) to SERVER2 also running Hyper-v 2012 R2
But I am confused on the best way to do this
1) should I just click on "MOVE" on SERVER1 to move to SERVER2?
2) Should I do an export and then import
3) should I setup replication from Server1 to Server2 and then do a failover?
4) or should I shut the VM down, copy the VHDX file and then create a new VM and use that VHDX
I just want to be cautious and use the best method to ensure it goes smooth and not worry about any corruption. Can anyone offer some advice?
thanks
It all depends on your environment and your current Hyper-V configuration.
I asume both servers are domain-member of the same domain and don't use SCVMM. If so, then make sure you do the following:
First enable the "Live Migration" feature in the Hyper-V settings on both Hyper-V Servers.
Make sure both Hyper-V Servers have a vSwitch configured with the same display name and connectivity. They must be somewhat identical, but not everything. As long as the connectivity is the same.
Make sure you have a location to store the VM files on SERVER2.
Then do a Live Migration from SERVER1 to SERVER2, follow the wizard. By using the Hyper-V Manager console on SERVER1.
NOTE1: Without computer certificates and Kerberos configuration on your Live Migration settings you cannot initiate a Live Migration from the Hyper-V Manager cconsole on SERVER2. With the default configuration, you have to login on (or connect
to) SERVER1 en then initiate the Live Migration.
NOTE2: If you can't configure the vSwitches the same. Then you have to shut down the VMs and do a Quick Migration. Then re-configure the VM network properties and power on the VMs.
I hope this information will help you goin on. If you need more detailed information use the following link:
Configure Live Migration and Migrating Virtual Machines without Failover Clustering
http://technet.microsoft.com/nl-nl/library/jj134199.aspx
Boudewijn Plomp | BPMi Infrastructure & Security
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember, if you see a post that helped you please click "Vote as Helpful", and if it answered your question, please click "Mark as Answer".

3 Node hyper-V 2012 R2 Failover Clustering with Storage spaces on one of the Hyper-V hosts

Hi,
We have 3x Dell R720s with 5x 600GB 3.5 15K SAS and 128 GB RAM each. Was wondering if I could setup a Fail-over Hyper-V 2012 R2 Clustering with these 3 with the shared storage for the CSV being provided by one of the Hyper-V hosts with storage spaces installed
(Is storage spaces supported on Hyper-V?) Or I can use a 2-Node Failover clustering and the third one as a standalone Hyper-V or Server 2012 R2 with Hyper-V and storage spaces.
Each Server comes with QP 1G and a DP10G nics so that I can dedicate the 10G nics for iSCSI
Dont have a SAN or a 10G switch so it would be a crossover cable connection between the servers.
Most of the VMs would be Non-HA. Exchange 2010, Sharepoint 2010 and SQL Server 2008 R2 would be the only VMS running as HA-VMs. CSV for the Hyper-V Failover cluster would be provided by the storage spaces.

I thought I was tying to do just that with 8x600 GB RAID-10 using the H/W RAID controller (on the 3rd Server) and creating CSVs out of that space so as to provide better storage performance for the HA-VMs.
1. Storage Server : 8x 600GB RAID-10 (For CSVs to house all HA-VMs running on the other 2 Servers) It may also run some local VMs that have very little disk I/O
2. Hyper-V-1 : Will act has primary HYPER-V hopst for 2x Exchange and Database Server HA-VMs (the VMDXs would be stored on the Storage Servers CSVs on top of the 8x600GB RAID-10). May also run some non-HA VMs using the local 2x600 GB in RAID-1
3. Hyper-V-2 : Will act as a Hyper-V host when the above HA-VMs fail-over to this one (when HYPER-V-1 is down for any reason). May also run some non-HA VMs using the local 2x600 GB in RAID-1
The single point of failure for the HA-VMs (non HA-VMs are non-HA so its OK if they are down for some time) is the Storage Server. The Exchange servers here are DAG peers to the Exchange Servers at the head office so in case the storage server mainboard
goes down (disk failure is mitigated using RAID, other components such as RAM, mainboard may still go but their % failure is relatively low) the local exchange servers would be down but exchange clients will still be able to do their email related tasks using
the HO Exchange servers.
Also they are under 4hr mission critical support including entire server replacement within the 4 hour period.
If you're OK with your shared storage being a single point of failure then sure you can proceed the way you've listed. However you'll still route all VM-related I/O over Ethernet which is obviously slower then running VMs from DAS (with or without virtual SAN
LUN-to-LUN replication layer) as DAS has higher bandwidth and smaller latency. Also with your scenario you exclude one host from your hypervisor cluster so running VMs on a pair of hosts instead of three would give you much worse performance and resilience:
with 1 from 3 physical hosts lost cluster would be still operable and with 1 from 2 lost all VMs booted on a single node could give you inadequate performance. So make sure your hosts would be insanely underprovisioned as every single node should be able to
handle ALL workload in case of disaster. Good luck and happy clustering :)
StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

Monitoring Hyper-V 2012 R2 - Performance Data/Graphs Equivalent to XenCenter/vSphere Client

Hello,
We've just moved away from Xenserver (hooray!) to Hyper-v 2012 R2, but I must admit the best thing about xenserver was xencenter. The ability to see the real time performance of a VM and see its network utlisation/CPU/Memory was very very useful. Also the
same for VMWare vsphere client.
Although Hyper-V 2012 R2 is a lot better than xenserver the realtime monitoring of VM's is awful!
We have SCVMM but that doesn't give you much either, only average CPU data..and only when it decides it will show the graph!
I've tried a few free tools, VMTurbo, Solarwinds VM Monitor (free - which doesn't support 2012 R2) plus some others...but none give us what we want.
I've seen all these other posts about monitoring reports etc which are all good and well but when you need real-time data how are people getting this? We don't want OM as we cannot afford it nor do we want the excess of managing it (not even sure if this
would give us what we want).
Can anyone give me ideas of what they are using for this or what products, I feel MS have messed up a bit here, if they had these features in Hyper-v Manager/Failover Cluster Manager then it would be on a par with VMWare for sure.
Many thanks
Matt

Update:
I've got a trail license of SCOM and installed it and connected to SCVMM (eventually...what a pain having to install extra packages etc!! good stuff MS! You'd think as SCVMM is part of the System Center family it would be easy to connect to SCOM)
I also got the free version of VeamOne as suggested by Leonardo.
SCOM is too complicated and requires far too much configuration just to get simple monitoring from Hyper-V and I really can't believe you need all this extra software just to get performance graphs from Hyper-V/VM's. Really don't want to install extra agents
on the hosts etc goes against Hyper-V best practice about keeping the servers light. Plus even trying to get simple data out of SCOM is tiresome.
VeamOne on the other hand...for a free product does exactly what SCVMM 'should' be doing.
Plus very useful extra info/alert that SCVMM doesn't even show up which I wasn't aware of, SCOM probably would show these alerts after you've spent days and days trying to figure out how to configure it and reading loads of articles.
So unless there is some hidden gem in SCVMM then it needs to be improved greatly on the monitoring side to fully compare with VMWare I believe as the idea of having to setup/configure SCOM just for monitoring is ridiculous.
I'm going to stick with VeamOne for now as its simple, gives me the info I require.

2008R2 Virtual machine shutting down unexpected on Hyper-V 2012 server

I have a problem where one of my 2008 R2 virtual servers are shutting down unexpected every Friday at more or less the same time. This has happen 2 Fridays in a row now and the time is 13:01:30 and 13:01:10. I did some investigation on the event viewer and
it tells me the following: (Error) The previous system shutdown at 01:01:10 PM on ‎2014/‎08/‎01 was unexpected. Event ID: 6008 which I have goggled and did not find much on this ID? I also found the following event more or less the same
time as the first one: (Critical) The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly. Event ID: 41. In most posts it looks like if it could
be hardware related? But how do I justify this on a virtual machine?
Some Infrastructure background: It is a 2008 R2 virtual server running on 2012 Hyper-V, 2012 server. SCVMM is not configured so all administration is done through Hyper-V manager. The virtual machine is backup up by Symantec backup exec and the Full backup
only start at 23:00pm night time. No scheduled shut-downs are configured and all servers are running on UPS power, the virtual server are also configured to boot up automatically after any failure. But in this case the server is completely shut-down and I
have to manually start the server up again.
I hope there are somebody who can give some guidance on my problem?
Regards
Juan Krynie

Hi Sam
Thanks for the reply!
Yes, all disk space is on the host, I have 2 hosts running Hyper V each with their own set of virtual servers, I am planning a cluster in the near future, but for now all disk space for all virtual server are on the host, there is more than enough disk space
left on all drives. Please below output from command, I only posted first few lines as there are to many lines.
Shadow Copy ID: {17e38390-dcb5-4ac4-9f43-62bc1a4c1dc2}
Original Volume: (C:)\\?\Volume{f7e4a444-a922-11e2-93e8-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy709
Originating Machine: ELAPNS02.AMentis.local
Service Machine: ELAPNS02.AMentis.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential
Contents of shadow copy set ID: {f938ba80-7641-457c-8297-863bf8419aba}
Contained 1 shadow copies at creation time: 29/08/2014 07:00:12
Shadow Copy ID: {44657104-c8bc-44ee-b8cb-b0469601531d}
Original Volume: (C:)\\?\Volume{f7e4a444-a922-11e2-93e8-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy713
Originating Machine: ELAPNS02.AMentis.local
Service Machine: ELAPNS02.AMentis.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential
Contents of shadow copy set ID: {e9cb6a0c-973d-4ff5-9877-0c81ab74dc80}
Contained 1 shadow copies at creation time: 29/08/2014 12:00:16
Shadow Copy ID: {4f824796-3dd1-498a-947c-5747e25d7ebc}
Original Volume: (C:)\\?\Volume{f7e4a444-a922-11e2-93e8-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy716
Originating Machine: ELAPNS02.AMentis.local
Service Machine: ELAPNS02.AMentis.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential
Contents of shadow copy set ID: {2f02b69b-1244-40bc-984b-f4488887d10d}
Contained 1 shadow copies at creation time: 01/09/2014 07:00:01
Shadow Copy ID: {8d039039-51ac-4cbf-be0a-4defb989a22c}
Original Volume: (C:)\\?\Volume{f7e4a444-a922-11e2-93e8-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy843
Originating Machine: ELAPNS02.AMentis.local
Service Machine: ELAPNS02.AMentis.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential
Contents of shadow copy set ID: {55b3d33e-a347-46cd-bf39-686acd7329ab}
Contained 1 shadow copies at creation time: 01/09/2014 12:00:01
Shadow Copy ID: {1239354e-3037-42b1-802c-27e1187c13b1}
Original Volume: (C:)\\?\Volume{f7e4a444-a922-11e2-93e8-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy846
Originating Machine: ELAPNS02.AMentis.local
Service Machine: ELAPNS02.AMentis.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential
Contents of shadow copy set ID: {813607c5-5d31-41b3-8b1c-5f89ef2e5b0b}
Contained 1 shadow copies at creation time: 02/09/2014 07:00:12
Shadow Copy ID: {0e1350a7-3fec-48fb-8fcb-d035dbfb001c}
Original Volume: (C:)\\?\Volume{f7e4a444-a922-11e2-93e8-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy850
Originating Machine: ELAPNS02.AMentis.local
Service Machine: ELAPNS02.AMentis.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential
Contents of shadow copy set ID: {ec206fef-a325-41c9-90b5-c4c6de3f94a8}
Contained 1 shadow copies at creation time: 02/09/2014 12:00:19
Shadow Copy ID: {aea06cae-f88f-4941-bc33-4ca62bf3380f}
Original Volume: (C:)\\?\Volume{f7e4a444-a922-11e2-93e8-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy853
Originating Machine: ELAPNS02.AMentis.local
Service Machine: ELAPNS02.AMentis.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential
Contents of shadow copy set ID: {45820935-e5c4-47a5-9979-0df9187194c8}
Contained 1 shadow copies at creation time: 03/09/2014 07:00:01
Shadow Copy ID: {8b14fdd6-2f2b-4cad-93b8-391c1d913cb3}
Original Volume: (C:)\\?\Volume{f7e4a444-a922-11e2-93e8-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy854
Originating Machine: ELAPNS02.AMentis.local
Service Machine: ELAPNS02.AMentis.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential
Contents of shadow copy set ID: {52277c29-ce5c-4c59-bfd4-9174b4870a02}
Contained 1 shadow copies at creation time: 03/09/2014 12:00:17
Shadow Copy ID: {199611ca-ec3f-435f-828e-bc1748b02bf9}
Original Volume: (C:)\\?\Volume{f7e4a444-a922-11e2-93e8-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy858
Originating Machine: ELAPNS02.AMentis.local
Service Machine: ELAPNS02.AMentis.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential
Contents of shadow copy set ID: {1dfaeb8b-3726-4f08-8582-5fec43bd6b37}
Contained 1 shadow copies at creation time: 04/09/2014 07:00:01
Shadow Copy ID: {d6ae9b1a-41ef-4db5-9c44-581ee7d7192d}
Original Volume: (C:)\\?\Volume{f7e4a444-a922-11e2-93e8-806e6f6e6963}\
Shadow Copy Volume: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy859
Originating Machine: ELAPNS02.AMentis.local
Service Machine: ELAPNS02.AMentis.local
Provider: 'Microsoft Software Shadow Copy provider 1.0'
Type: ClientAccessible
Attributes: Persistent, Client-accessible, No auto release, No writers,
Differential
Juan Krynie

Multiple Hyper-V 2012 R2 servers to access a since ISCSI target

Similar Messages

Maybe you are looking for