Hello,

     I'm new to setting up Hyper-V replication and would like to first start by describing my environment.

Location A (Primary Site)

Two node Server 2012 Hyper-V host cluster. Fiber Attached storage. I have a CSV assigned to the cluster dedicated for replication. Network address = 172.24.110.xxx. All servers are assigned static IP addresses.

Location B (Secondary Site)

Two node Server 2012 Hyper-V host cluster. Fiber Attached storage. I have a CSV assigned to the cluster dedicated for replication. Network address = 172.24.60.xxx. All servers are assigned static IP addresses.

I have the Hyper-V Replica Broker setup on each cluster in both locations, both sites can replicate to each other and I pointed the default location to store the replica files to the C:\Clusterstorage\Hypervreplication volume that I created strictly for replicated VM's.  I've successfully tested replication from Location A to Location B. When I look at the volume that contains the newly replicate files, I have a folder called "Hyper-V Replica". Within this folder I have four other folders. They are as follows: Planned Virtual Machines, Snapshots, Virtual Hard Disks and Virtual Machines. One of my issues is that everything seems to be based off of the VM's GUID. It seems difficult to keep track of the name of each VM that would get replicated to this volume. Is there a way to easily identify which VM's files are in a particular folder? I ask because when you create a new VM on a volume, the folder is named whatever the VM is named which makes it easy when you have 300 or so VM's to deal with.

My other question has to do with the IP addresses. Location A and Location B are both on the same domain but each location uses a different network address. I join the VM to the domain at Location A (Primary Site) using a 110 network address and then plan on replicating it to Location B (Secondary Site) that uses a 60 Network address. Once I enable replication on a VM, I then can add the failover TCP/IP address for the .60 network. Once the VM has completely replicated, I'll turn the VM off and do a planned failover. I turn on the replicated VM at Location B but I'm unable to ping the VM by name or remote desktop to the VM. I'm sure this is because DNS does not have the IP address resolving to the name. Do I manually have to enter in the DNS records for the 60 network? Is there an easier more efficient way of bring the replicated VM online when using static addressing? If anyone see's anything I'm doing wrong please let me know or let me know if there is a better way of doing what I'm trying to accomplish. Hopefully I explained things clear enough. lol Thanks

Pat

Pat

People please help me!

Today at my enterprise I installed a new hard disk in my HyperV Server. When I tried to add this HD in one of the VM (File server - Windows Server 2003), the process failed and the HyperV froze. I restarted the service and tried to turn on the Virtual machine, but I couldn't. I had an error message. So I used the last snapshot I had, but I didn't see it was from 2014. The VM turned on, but I lost all files. Then I decided to use the 2015 snapshot again. The VM turned on again, but as if it was 2014 snapshot. I lost 8 months of files . I really don't know what to do. I tried recuva and many others recover software, but nothing. Please someone help me to restore this VM today's status. Is there any way to recover this replaced files?

Hello,

Let me start by saying I am a new Admin to this organization and have no real Hyper-V experience. I have figured most things out until now. 

We have 2 sites in different states that are Hyper-V 2012 servers (site A and site B).  They are set up for HA failover locally and replication between the sites.  The previous admin set all of this up.  Our website in location A was running on a 2008 R2 vm with SQL 2008 SP3. The replication between locations worked.

I recently created a vm running server 2012, ColdFusion 11 to host the site in location A. I set the 2008 up as just the database server still running the same as previously mentioned. 

Replication between locations has failed since the day I turned on the 2012 vm.  I have not changed anything about the vm other than its IP and name, which replication doesn't seem to care about (at least that I can find).

When I look at replication health I see the following:

When I try to start the VM at location B I get this:

An error occurred while attempting so start the selected virtual machine 'Production DB' failed to change state

When I try to resume replication at location A I see this:

What am I doing wrong?  How can I get this working?

Any assistance will be GREATLY APPRECIATED!!!

Thank you

RIC Admin

we have 2 nodes on a cluster,on one node we accidentally tried the Draining of Roles,but again paused it in between to revert back.This resulted in one of the roles on that cluster to fail.After checking i could see that the resources,instances to be offline,on trying to bring up they fail again.I could see that the Mount Point of one the folders was removed from share path and i cannot provide any share again to that folder,the network path cannot be detected. Under the share tab of failover cluster manager ,i could see that it shows File server role to be offline.Have tried doing flushdns but doesnot seem to work.Tried creating new folders and give them shared access but the network path is not detectable

Please help me out,i am new to Hyper-V 2012 and have searched every query,but cannot reach any conclusion.

Regards

Rohon

Dear reader,

We sometimes have a problem where our windows 2012 r2 RDS virtual servers, that reside on windows 2012r2 hyper-v hosts, loose their dynamic memory and only have their startup memory left to work with. Users start complaining that things are very slow etc.

If I check several screens (RDS Broker load balancing, hyper-v manager, cluster manager and the vm's task manager) it's clear that the vm only has its startup memory allocated. I'm not sure if this happens instantly or immidiatly after the nightly reboot. To resolve the problem we have to call all users on the vm where it happens and ask them to logoff (if they are even able to), and then we reboot the machine.

I have checked the logs from the machine where the VM resides on and the logs from the vm itself. But I cannot find anything. We also have alot of windows 2008r2 vm's with dynamivc memory, but none of those have ever had this problem.

Searched the internet, but so far it seems we are only.

Can anyone give me a lead to troubleshoot this?

Best regards,

Ruud Boersma

MCITP Enterprise administrator

Hello,

whenever I build new VM on our Server 2012 Hyper-V and add new SCSI disks, the VM becomes very slow while formatting those disks.

The "quick" formatting takes unusally long, for 20 GB disk it might take few minutes, for 200 GB it may take 30 minutes or more.

System Windows log is flooded with events:

Event ID: 129, Source: storvsc

Reset to device, \Device\RaidPort0, was issued.

It happens with either Integration tools versions: 6.2.9200.20873 or 6.2.9200.16384.

We are in the process off moving our 2008R2 VM's from the 2008R2 HyperV servers to new Server 2012R2 Hosts.

We shut down the VM's copy the files and VHD's to the new CSV's en import the VM in the Hyperv Manager. Then we make them high available in the Failover Cluster Manager (Configure role - Virtual machine). We mount the integration tools and update the VM to version 6.3.9600.16384

For a specific type of VM (mostly RDS Host servers) we always had Dynamic Memory configured (when they were hosted on de 2008R2 platform), so we are using the same settings on the 2012r2 platform. The memory settings were;

Startup memory: 1024 MB

Minimum memory: 1024 MB

Maximum memory: 12288 MB

These VM's reboot every morning, this is done for specific reasons. But now once in a while (once per week/2 weeks) we notice that the VM's are not using more memory then 1024 MB while the demand is much higher. Rebooting the server helps most of the times, live migrating to another host also helps. In the VM we see that memory usage in the taskmanager is 99-100%, and after the move it immediately starts using more than the minimum configured amount.

Until the failover the memory usage was 1024 MB and it did not get any higher.

This happened several times. Last week we changed the Memory configuration to:

Startup memory : 2048 MB

Minimum memory: 2048 MB

Maximum memory: 12288 MB

But this morning we had a call about the performance of one of the VM's, We saw that it was only using 2 GB memory while the demand was much higher. After live migrating it to another host it started using more memory immediately.

The 2012R2 hosts are not overcommited, there is a lot of memory still available for the VM's. Those VM's never had this problem on the 2008R2 Hyperv platform.

Any idea why this happens?

Peter Camps

Scenario

I have a 3 Windows 2012 R2 Hyper-V hosts which is participating in a cluster, all of the virtual machines are hosted on CSV's. We also use Dynamic Memory for most of the servers

We do regular reboots every week for our virtual machines, but we've found that sometimes, a virtual guest will suddenly stop requesting additional memory.  At the time of writing, I have identified 10 machines - on different hosts, and even different clusters which are exhibiting this behaviour.  They're also running OS's ranging from Windows 7 to Windows 2008 R2 and Windows 2012.

I have selected one to demonstrate below.

Here, you can see the virtual machine is configured to use Dynamic Memory

and here, you can see that it's not actually demanding more than the start memory, despite the fact that I've overloaded the servers virtual memory by using MSPAINT.

Workaround

Rebooting the virtual machine does not resolve the issue, but live migrating the virtual machine from the host it is on to another host suddenly allows it to demand more memory.  One can then live-migrate it back to the original host and the problem is no longer there.

Troubleshooting

We have performed the following troubleshooting steps:

• Verified that the Integration Services are up-to-date (currently running 6.3.9600.16384)
• Verified that the virtual server has up-to-date Windows Updates
• Checked the Hyper-V-Worker\Admin event log on the current host - no errors pertaining to this VM.
• Verified that the Hyper-V host has sufficient RAM (currently only using 542 out of 768 GB)
• Checked the System event log on the virtual machine - nothing out of the ordinary to report.
• Verified that all services which start with the word "Hyper-V" on the guest machine is running.

Using the following command, I can easily identify which machines are affected (this command applies to SCVMM only):

Get-SCVirtualMachine | where {$_.DynamicMemoryEnabled -eq $true -and $_.DynamicMemoryDemandMB -eq $_.Memory} | ft Name,HostName,OperatingSystem,Memory,DynamicMemoryDemandMB,DynamicMemoryMinimumMB,DynamicMemoryMaximumMB

I do not know any diagnostic program which can give me more information regarding the memory status of a server - specifically one which can tell me more information about Memory demand, and why it's not working. 

Considering that the problem is resolved when I live migrate the affected machine, it would suggest that the issue is with the host, but as live migrating it back no longer exhibits the issue - that seems to negate that theory.  Additionally, the other 103 virtual machines which run on this host seem to not show this issue.

It's almost as if the machine is being ran with static memory, and Hyper-V doesn't realise it's dynamic, but the moment it's live migrated, it suddenly realises this and enables dynamic memory.

Any thoughts?

HI,

We are in preparation in redoing our hyper V server because of bad blocks on our raid volume from a punctured array.

Dell informed us that we need to backup and restore data using data done on a file level and not a bit level or system image.

"CAUTION! Do not do a bare metal restore or bit-level backup of your Virtual Disks, this will copy the corrupted data and put it back on your VD continuing the issue."

My question is, when we shut down the VM's im Windows Server 2012 and perform a export of the vm's to a external disk,  is this ok to use to restore the VM's once after we reinstall and get the host running again?

I know we can just manually copy the VM files in windows explorer to a external disk which will be a file level copy for sure but we already did the export feature in hyper V.  FIle level copy in windows explorer of the vm files would take another 5-6 hours.

Thanks in Advance.

Hello, I just upgraded my machine to Windows 10 and now my Hyper-V Manager cannot connect to and manage our Server 2012R2 Hyper-V Hosts. I get the following error.

"An error occurred while attempting to connect to server xxxxx. Check that the Virtual Machine Management service is running and that you are authorized to connect to the server."

I've read in multiple places that Hyper-V Manager in Windows 10 and Server 10 will support managing Server 2012 and 2012R2 hosts. I'm not sure why it's not working though.

Any help would be appreciated.

Im seeing this warning in the Event Viewer for Hyper-V-Integration.
It's occuring for all my VMs (XP SP3). The Integration Services were installed and the VMs settings shows All Services enabled.

Ideas?

I have a client using a specific application that communicates with a MySql server that is installed on the same 2008 R2 virtual machine.

When using this application it seems to take a long time when querying the MySql database. The program will start not responding and could take up to 1-2 minutes to display in certain areas where it should take less than 10 seconds.

Here is what I know:

• The long pauses seem to be when it is querying the database.
• The long pause only occurs when it is running on a virtual machine in our environment
• CPU is not a problem. Take manager in the VM shows less than 10% CPU and VMM shows 0% CPU Average
• Memory is not the problem (tried dynamic and static) and shows less than 35% of the total amount of memory (8GB total currently)
• Disk does not show any performance issues and show about what I should see with 6Gbps SAS disks (500+)
• I've tried multiple hosts and even had it running on a host with no other VMs
• My hosts are BL685c G7 with 4x AMD 16-Core 6278 2.4Ghz processors and 512GB of DDR3-10600R RAM. Thats 64 total cores.
• My SAN is a HP 3PAR 7200 running 4GB fiber (four paths)
• I've tried fiber channel passthrough to the VM as well as a vhdx file for the database drive
• I've tried RAID5 64KiB, RAID1 64KiB, and RAID1 256KiB for the RAID
• My 3PAR reports show less than 80 IOPs per drive in my enclosure for READ/WRITE
• My 3PAR is using 380GB of adaptive flash cache

I have taken this VM and duplicated (system image) it on other hardware. When it is virtual the problem exist and when it is not virtual the performance is fine. 

The problem is related to being virtualized but I just can't figure out what is causing it! Has anyone had issues with applications communicating with MySql on Hyper-V? I really think this is something Hyper-V related but just can't pinpoint it.

Hello!

We've got Hyper-V 2012r2 and CentOS 6.6 running in VM.

We have web-server running on it. And in fact it uses space:

df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/vg_bitrix2-lv_root
                       50G  3,7G   43G   8% /
tmpfs                 1,9G     0  1,9G   0% /dev/shm
/dev/sda1             477M   46M  406M  11% /boot
/dev/mapper/vg_bitrix2-lv_home
                      439G  101G  316G  25% /home

But vmdk file in Hyper-V weights 300Gb.

I tried 

cd / ; cat /dev/zero > zero.fill ; sync ; sleep 1 ; sync ; rm -f zero.fill

And after that:

Mount-VHD 'D:\Hyper-V\bitrix2\Virtual Hard Disks\bitrix2.vhdx' -ReadOnly
Optimize-Vhd -path 'D:\Hyper-V\bitrix2\Virtual Hard Disks\bitrix2.vhdx' -Mode Full
Dismount-VHD 'D:\Hyper-V\bitrix2\Virtual Hard Disks\bitrix2.vhdx'

But it doesn't help..Can anyone help us with the problem?

Hi All,

Had some issues with virtual switch, it never worked. Tried to enable/disable hyper-v.

Pretty much does not install anymore. Maybe some of you have an idea.

Here output from CBS.log based on it seems the virtual switch part is failing, but no idea why exactly:

2014-12-26 01:32:15, Info                  CSI    000000c4 Begin executing advanced installer phase 38 (0x00000026) index 180 (0x00000000000000b4) (sequence 219)
    Old component: [l:0]""
    New component: [ml:318{159},l:316{158}]"Microsoft-Hyper-V-Drivers-VmSwitch, Culture=neutral, Version=6.3.9600.17401, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    Install mode: install
    Installer ID: {81a34a10-4256-436a-89d6-794b97ca407c}
    Installer name: [15]"Generic Command"
2014-12-26 01:32:15, Info                  CSI    000000c5 Performing 1 operations; 1 are not lock/unlock and follow:
  (0)  LockComponentPath (10): flags: 0 comp: {l:16 b:242611049b20d001720000009804c004} pathid: {l:16 b:242611049b20d001730000009804c004} path: [l:226{113}]"\SystemRoot\WinSxS\amd64_microsoft-hyper-v-drivers-vmswitch_31bf3856ad364e35_6.3.9600.17401_none_5a1d032e53d5da20" pid: 498 starttime: 130640239192515300 (0x01d0209afa7122e4)
2014-12-26 01:32:15, Info                  CSI    000000c6 Calling generic command executable (sequence 1): [30]"C:\WINDOWS\System32\netcfg.exe"
    CmdLine: [51]""C:\WINDOWS\System32\netcfg.exe" -e -c s -i VMS_VSF"
2014-12-26 01:32:15, Info                  CSI    000000c7 Done with generic command 1; CreateProcess returned 0, CPAW returned S_OK
    Process exit code 0 resulted in success? TRUE
    Process output is throttled for successful Generic Commands
2014-12-26 01:32:15, Info                  CSI    000000c8 Calling generic command executable (sequence 2): [30]"C:\WINDOWS\System32\netcfg.exe"
    CmdLine: [50]""C:\WINDOWS\System32\netcfg.exe" -e -c p -i VMS_PP"
2014-12-26 01:32:16, Info                  CBS    Progress: UI message updated. Operation type: Foundation. Stage: 1 out of 1. Percent progress: 95.
2014-12-26 01:32:16, Info                  CBS    Winlogon: TiCoreOnCreateSession has been called
2014-12-26 01:32:19, Info                  CSI    000000c9 Performing 1 operations; 1 are not lock/unlock and follow:
  (0)  LockComponentPath (10): flags: 0 comp: {l:16 b:4ef075069b20d001740000009804c004} pathid: {l:16 b:4ef075069b20d001750000009804c004} path: [l:234{117}]"\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_6.3.9600.16384_none_cd3183f2deb856d2" pid: 498 starttime: 130640239192515300 (0x01d0209afa7122e4)
2014-12-26 01:32:19, Info                  CSI    000000ca Creating NT transaction (seq 3), objectname [6]"(null)"
2014-12-26 01:32:19, Info                  CSI    000000cb Created NT transaction (seq 3) result 0x00000000, handle @0x320
2014-12-26 01:32:19, Info                  CSI    000000cc@2014/12/25:23:32:19.415 Beginning NT transaction commit...
2014-12-26 01:32:19, Info                  CSI    000000cd@2014/12/25:23:32:19.431 CSI perf trace:
CSIPERF:TXCOMMIT;15069
2014-12-26 01:32:19, Error                 CSI    000000ce (F) Done with generic command 2; CreateProcess returned 0, CPAW returned S_OK
    Process exit code 5 resulted in success? FALSE
    Process output: [l:73 [73]"Trying to install VMS_PP ...




... failed. Error code: 0x80070005.




"][gle=0x80004005]
2014-12-26 01:32:19, Info                  CSI    000000cf Calling generic command executable (sequence 3): [30]"C:\WINDOWS\System32\netcfg.exe"
    CmdLine: [51]""C:\WINDOWS\System32\netcfg.exe" -e -c p -i VMS_VSP"
2014-12-26 01:32:19, Info                  CSI    000000d0 Done with generic command 3; CreateProcess returned 0, CPAW returned S_OK
    Process exit code 0 resulted in success? TRUE

If you have some ideas please let me know.

Thanks,

jb

I'm trying to see if there is any way to cost-effectively build a 2 Server Hyper-V cluster that can run 100  high-performing Windows 7 virtual machines that will be all have somewhat different apps that users will install and uninstall regularly and have this configuration not cost much more than adding the VMs to existing workstations as client Hyper-V virtual machines.

We would need VMM 2012 R2 so we could delegate limited management ability of each VM to the end user.

The workstations will be doing relatively heavy software development work with many simultaneous applications running.  Users currently have i5 workstations with 16GB RAM and SSD drives.  They will need similar performance from the VMs.

We are not a candidate for thin clients because the users will need access to 2 systems. 

1.  Normal office system running as limited user for normal office apps that don't require admin rights, and these will have access to the Internet for email, web and IM.

2.  Developer and/or testing workstation requiring admins rights with frequent software installs and uninstalls and ability to run debugging tools.

If we had thin clients, that would double the amount of VDI clients since they would still need both an office workstation and a developer or testing workstation.  With a full Windows workstation, their office system can run on the host and the development and testing systems can run in Client Hyper-V.

What kind of hardware would we be looking at for an adequately performing setup with 2 Hyper-V 2012 R2 servers with enough RAM, networking, CPU and disk space and I/O for this load and with virtual SAN for live migration and redundancy?

I suspect that it will be shockingly expensive compared to deploying client Hyper-V or even VMWare Workstation to 100 workstations, but I'd like to see what people say first.

Even if it costs somewhat more, we will consider it if it add great benefits, but not if it drastically more expensive to implement and maintain.

I have one of server 2012, running on hyper V,  its only have C drive, (system drive), Its almost full now, please any one can advise me how I can increase my c drive, 

We have a windows 2012r2 hyper v host running 6 vm's.

the hyper v host has veeam backup and replication and  had an ip assigned to be on the network , so it could be replicating to another hyper v server via veeam.

After installing windows update last Friday night, I discovered that although the 6vm's are on the network, the byper v host itself is not.

I am not sure on which nic on he hyper v host the ipconfiguration was tied to.

the vm's are using ....#4

I briefly added the ip configuration to the nic called internal1-1 , but did not connect to the network (I did not reboot)

how can I re-enable network access for the hyper v host again.!!

regards

Leopold

I have a Win2012 hyper-v failover cluster running in our Dev lab. It is very simple with 2 nodes and shared SMB storage on the server running the failover cluster role. a few nights ago all of the VMs on one of the nodes failed to start giving the error message: failed to lock virtual machines configuration file (unspecified error 0X800040005).

I checked the path configured on the Hyper-V node (c:\program data\Microsoft\hyper-v\virtual machines) that points to the configurations files and VHDX files on the SMB share and it was correct. I also tested that the node could access the path listed in the symlink via explorer and it could. I disabled AV to no avail and also there is no back up software running in this node. I also tried re-adding the symlink using the mklink command but this still did not get the VM to start. It reports a lock on the config file however when I go on to the server with the storage I do not see any open handles on the files.

There were no changes as far as I am aware and the only way I have found to get each server back on-line is to delete the config file which causes the VM to dissapear from the inventory and recreate using the existing VHDX file, albeit that I have to re-add the additional configurations again and that the new config file is stored on the local disk rather than the shared storage. There were no permissions changes as this would have caused issues on the second node which is working fine. 

I would really like to find out what caused this and find out how I can get the rest f the VMs back on-line without having to rebuild them.

Hello,

     I'm new to setting up Hyper-V replication and would like to first start by describing my environment.

Location A (Primary Site)

Two node Server 2012 Hyper-V host cluster. Fiber Attached storage. I have a CSV assigned to the cluster dedicated for replication. Network address = 172.24.110.xxx. All servers are assigned static IP addresses.

Location B (Secondary Site)

Two node Server 2012 Hyper-V host cluster. Fiber Attached storage. I have a CSV assigned to the cluster dedicated for replication. Network address = 172.24.60.xxx. All servers are assigned static IP addresses.

I have the Hyper-V Replica Broker setup on each cluster in both locations, both sites can replicate to each other and I pointed the default location to store the replica files to the C:\Clusterstorage\Hypervreplication volume that I created strictly for replicated VM's.  I've successfully tested replication from Location A to Location B. When I look at the volume that contains the newly replicate files, I have a folder called "Hyper-V Replica". Within this folder I have four other folders. They are as follows: Planned Virtual Machines, Snapshots, Virtual Hard Disks and Virtual Machines. One of my issues is that everything seems to be based off of the VM's GUID. It seems difficult to keep track of the name of each VM that would get replicated to this volume. Is there a way to easily identify which VM's files are in a particular folder? I ask because when you create a new VM on a volume, the folder is named whatever the VM is named which makes it easy when you have 300 or so VM's to deal with.

My other question has to do with the IP addresses. Location A and Location B are both on the same domain but each location uses a different network address. I join the VM to the domain at Location A (Primary Site) using a 110 network address and then plan on replicating it to Location B (Secondary Site) that uses a 60 Network address. Once I enable replication on a VM, I then can add the failover TCP/IP address for the .60 network. Once the VM has completely replicated, I'll turn the VM off and do a planned failover. I turn on the replicated VM at Location B but I'm unable to ping the VM by name or remote desktop to the VM. I'm sure this is because DNS does not have the IP address resolving to the name. Do I manually have to enter in the DNS records for the 60 network? Is there an easier more efficient way of bring the replicated VM online when using static addressing? If anyone see's anything I'm doing wrong please let me know or let me know if there is a better way of doing what I'm trying to accomplish. Hopefully I explained things clear enough. lol Thanks

Pat

Pat