Hi,

I have a server 2016 where the windows backup kept creating recovery points.  We noticed to late and now we are stuck with 50 recovery points which we cannot delete.

It looks like this and the tree just goes deeper.

When trying to delete them from the GUI or powershell we get the following error on every checkpoint:

Cannot delete checkpoint: Catastrophic failure (0x8000FFFF). Checkpoint ID C5403A69-C9E9-4EDC-A441-46BFCBDF8CA8.
Virtual machine failed to generate VHD tree: 'Catastrophic failure'('0x8000FFFF').

I'm unable to create a new recovery point and export from there as I hit the limit of 50 recovery points.

I'm unable to merge because it are recovery checkpoints and I heard you should not merge this.

What are my options to fix this, could anybody shed some light on this?

Thank you!
Chris

Hey,

The goal of the project that I am working on is to create a subnet, with DHCP and NAT, of virtual adapters on the management OS.

(Please do not question why I would do such a thing)

To accomplish this I created a hyper-v Internal Virtual Switch with the command

New-VMSwitch -SwitchName "V Switch" -SwitchType Internal

and I also created multiple virtual adapters connected to that switch.

Add-VMNetworkAdapter –ManagementOS -Name "V Adapter1" –SwitchName "V Switch”

Add-VMNetworkAdapter –ManagementOS -Name "V Adapter2" –SwitchName "V Switch”

Add-VMNetworkAdapter –ManagementOS -Name "V Adapter3" –SwitchName "V Switch”

Then connected a physical adapter (connected to the internet) to the internal virtual switch using Internet connection sharing (ICS). Which turned the internal virtual switch's adapter into a gateway with Ip address 192.168.137.1. The other adapters, V Adapter1 ect..., should be apart of the subnet and get an Ip address in the range 192.168.137.xxx but they do not get responses from Internet connection sharing's DHCP server and have APIPA addresses.

I tested to see if I could get an Ip address from a VM attached to the internal virtual switch and the VM was able to get the Ip address 192.168.137.142 from the DHCP server just fine.

I also tested to see if I could get an Ip address using the ManagementOs virtual adapter "V Adapter1" by using a custom protocol driver that spoofed the source mac address (send DHCP discover with different MAC) and set the adapter in promiscuous mode(Receive messages with MACs other than the adapters own MAC). It was also able to get an Ip address.

Does anyone have any idea why the ManagementOs virtual adapters are not able to get an Ip address from ICS's DHCP server?

Also forgot to mention that if I set a static Ip address for the ManagementOs virtual adapters they work all perfectly fine. It just seems like the DHCP discover message is ignored by ICS if it is from the ManagementOs virtual adapters.

Any ideas of why this happens or a way to get Ip address for ManagementOs virtual adapters from the ICS DHCP server would be a great help.

Thanks!

Hi,

I have Hyper-v Cluster and Standalone Hyper-V server.I want to move all the VM in Standalone environment to Cluster environment.

01.Standalone server have two VM.

02.Cluster have 3 physical node and 4 VM

03.Standalone Hyper-v server and Hyper-v cluster servers connected to HP Storage

Please share the step for how to move VM from Standalone Hyper-V to Hyper-v Cluster

Thanks,

Gayan

Hi all,

I have 2 Hyper-V Servers, one running Server Core 2016 and one running Server 2019 Datacenter w/ GUI.

On the 2019 server, all 5 of the VMs are Server 2019 Datacenter w/ GUI.  I back them all up with Task Scheduler running Powershell scripts to a network share on a dedicated backup server (running 2019 Datacenter w/ GUI).  They all work perfectly, with a variety of schedules and other options including different destinations, etc.  NO problems.

On the 2016 server, there are 10 VMs, 8 of which run Server 2016 Datacenter w/ GUI or Server 2019 Datacenter w/ GUI.  All 8 of these work beautifully with the powershell scripts with wbadmin and task scheduler.  (Same idea as the 2019 server.)

But on that 2016 host server, there are 2 VMs running Server 2012 R2 Standard w/ GUI.  They are not domain controllers, exchange servers, or have any other SQL based applications.  One hosts an encrypted file cabinet program and the other hosts nothing more than an old version of Quickbooks 2008 as a Remote Desktop web application.  Both of them act the same way with the exact same wbadmin powershell command as the working ones.  They both do the same thing whether it's run as a scheduled task or as a direct elevated Command Prompt command or an elevated Powershell command.  They both do the exact same thing whether the command is run as a "Domain Admin" or the dedicated "Backup User" that is used to initiate all the other scheduled tasks.  They both act the same with different target servers and different shares.  They both act the same whether they are online or offline.

Here is a sample powershell command like what I'm using (it works for all my 2016 and 2019 VMs):

wbadmin start backup -backupTarget:\\BackupServer\BackupShare -hyperv:"ServerName" -vssfull -quiet

(I know the -vssfull is redundant when going to a network share but I don't want to have to remember to change this part if I temporarily send it to a local destination.)

What happens when it runs on the 2012 R2 servers:

It does the usual "Creating a shadow copy of the volumes specified for backup..." for a few minutes.  Then it says "Enumerating files for <ServerName>(Online)... 10 found" (ALL the ones that work have exactly 18 files, and never say this 'enumerating files verbiage... they just move straight to 'Starting application backup').  Then it says "Copying files for <ServerName>(Online)..." on one line only (for just a few seconds) with a percentage that will be somewhere randomly spaced between 0% and 25%.  Then it says "The backup operation successfully completed.  Backup of <ServerName>(Online) succeeded.  Application backup succeeded.  Log of files successfully backed up:  <path to log file>.  (Examples of log files from successful and unsuccessful attempts below, but the TL;DR version is that the backup completes successfully but just plain doesn't even try to backup the actual Virtual Hard Disks, like they aren't even there.)

But of course, the "successful" backup set is always roughly 150-250 MB and doesn't include ANY data at all. You know how if you dig into the folders you see the virtual hard drive file that is essentially the size of the data on the server VHD.  Then if you mount that and look inside it, you see the actual backup of the VHD?  Well... what I'm left with is a 150-250 MB VHD that if I mount it and look inside it, there is no virtual hard drive with the data.  It's just not there.

Some notes:  Both 2012 R2 servers are completely up to date and working perfectly otherwise.  Both are generation 2 and have SCSI controllers (not IDE).  One of these VMs is 670 GB and the other is only 21 GB, so size doesn't seem to matter (also, I have another VM that's 2 TB on that same server and it has no problem, so having enough free resources isn't the issue.)  The event viewer doesn't show any errors at all, because, like it said above, it thinks everything succeeded perfectly.

I've googled my little heart out and come up with dozens of postings and forums talking about generic fixes for wbadmin problems, and while I can't list everything I've tried here, it's been quite a bit.  I just haven't been able to find something specific enough to 2012 R2 on a 2016 host to get me where I'm going... which makes me think this is not a typical problem people face. Somebody out there has to have seen this right?  I feel like it's going to be an easy answer like, 'you can't do that, stupid' or 'check this box, silly' but I haven't found it.  Also, for various reasons, upgrading these servers to newer operating systems is out of the question for the next year or two.

Successful Log File Example (from one of the working 2016+ VMs):

Backed up V:\
Backed up V:\Snapshots\
Backed up V:\Snapshots\397F9C6A-9CFE-44D0-8D4F-5A17D4175090.vmcx
Backed up V:\Snapshots\397F9C6A-9CFE-44D0-8D4F-5A17D4175090.VMRS
Backed up V:\Virtual Hard Disks\
Backed up V:\Virtual Hard Disks\SLC-AD-02_Disk_2-AutoRecovery.avhdx
Backed up V:\Virtual Hard Disks\SLC-AD-02_Disk_2.vhdx
Backed up V:\Virtual Hard Disks\slc_ad_02_disk_1-AutoRecovery.avhdx
Backed up V:\Virtual Hard Disks\SLC_AD_02_Disk_1.vhdx
Backed up V:\Virtual Machines\
Backed up V:\Virtual Machines\5FA4A6CE-38C8-4977-ADFE-0EB1AECB5F96.VMRS
Backed up V:\Virtual Machines\5FA4A6CE-38C8-4977-ADFE-0EB1AECB5F96.vmcx
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: 5FA4A6CE-38C8-4977-ADFE-0EB1AECB5F96
   Caption     : Online\SLC-AD-02
   Logical Path: 


*-----------------------------*

Log file from a 2012 R2 attempt (that obviously didn't work, you'll notice the lines where the VHDs should be listed between 'Virtual Hard Disks' and 'Virtual Machines', is nothing more than a carriage return: 

EVEN MORE DETAILS:  I went and tried including every combination of -include:c: -systemState -allCritical, etc. but all of those switches (of course) backup the specified resource for the hyperv host server, not the VM, and it works perfectly, but it's obviously not backing up what I want.  It looks like it's just plain failing to find the VHDs on the 2012 R2 VMs so it just backs up the VM component without the disks and then gives itself a pat on the back for job well done and heads off to its favorite pub for a mid-strength beer.

The even crazier thing:  IT USED TO WORK!  I have VM backups of these machines from 5 days ago from that same server to a different destination (before we upgraded the backup destination server) that worked perfectly.  So, just to prove the theory that the destination was somehow the problem, I hooked up the old backup server and tried to send it back to the destination where it worked successfully 5 days ago... and it does the same thing now... a backup with no virtual hard disks.

So to sum up:  It worked for all machines.  I added a completely different destination server and replaced the scripts with a version with a few extra lines of house-keeping for moving old backups out of the way before the new one runs, and changed the destination share.  It works for all 2016 and 2019 servers, never worked right for either 2012 R2 VMs after the new scripts and destination.  I tried sending it back to the old destination with the old script... and now that doesn't work either.  Tried rebooting 2012 VMs and the host server, no change.

WHAT AM I MISSING???

Any help is appreciated.  Thanks in advance.

Hi,

IP address is set on Hyper-V host machine. When I try to query it using the following SCVMM command, IPAddress field in the adapters is empty.

 Get-SCHostNetworkAdapter -VMHost $vmRef.VMHost 

Has anyone faced this issue earlier? Is there any way to fix this issue? 

Thanks,

Priya

Priya

I bought an old dell R710 to learn hyper-v, AD, VMware etc. only about a month ago. I installed hyper-v bare bones on the R710 - Windows hyper-v server 2016. The free version which has no GUI. So I'm learning powershell (ver 5.0) as I go along and I have the virtual switch installed. I have the VMmachine installed.

Hi all,

I'm running a Hyper-V host on a Windows 10 machine (beefy gaming type PC, 32GB ram, 1TB SSD) and attemping to spin up Windows 10 guests (as differencing disks off a parent disk). The problem is that often VMs start and often get stuck on the boot screen. I can often restart them and they boot in fine (though not always). I have looked around and none of the obvious problems/solutions seem to help.

If I were to get server class hardware and run e.g. Windows Server 2019 would this boost the reliability of the VMs i.e. fewer if any black screens?

Or should they run just as reliably on my Windows 10 gaming rig and my problem is most likely something else?

Any thoughts appreciated

m

Anyone knows how to fix this bug?

https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/best-practices-analyzer/dynamic-memory-is-enabled-but-not-responding-on-some-virtual-machines

This happens on alot of our VM's running a 2016 Hyper-V Cluster - hardware is HPE BL460c G9.

"This is expected behavior if the virtual machine is booting" - True dat!

Hi,

Can anyone guide how to move the storage disks to CSVS if they already have VMS?

Thanks.

Want to move my Hyper-v „data-files“ to a different disk, found options for the virtual disk in settings, but nothing for virtual machines and the rest.

Is there any way with settings, etc. or can‘t I change the original path when creating the virtual machine?

Hi,

Is it possible to have hyper-v replica between hyper-v server 2016 (core) and windows server 2019?

Consider that VM configuration versions are the same.

Using pfSense as an example if I had a single hyper-V server and I wanted to have a VM running pfSense internet facing and then behind the pfSense a LAN with multiple VM on it then it would simple to setup in terms of vswitches ie. 

1) an external vswitch for the WAN side of the pfSense VM 

2) an internal vswitch for the LAN side of the pfSense and the VMs on the the LAN.

This is actually what the pfSense documentation recommends (the same principles would apply to all firewall setups like this). 

The more complex situation occurs when you have a failover cluster and you want to run the same setup.  As an example - 

2 x hypervisor, 1 VM running pfSense and multiple VMs on the LAN side where those VMs could be on either hypervisor. Hyper-V does not have the equivalent (as far as I know) of VMWare's distributed vswitch which would be ideal here. 

So the only way I can see it working is to use external vswitch(es) only. 

You could either use vlan tagging on one external vswitch or have 2 external vswitches one for the WAN connection and one for the LAN connection. 

Either way the only upstream (physical network) L3 gateway would be for the WAN and not the LAN. 

Does anyone know of another way of achieving the above or is that about right in how to achieve it and if so can anyone see any pros or cons between vlan tagging on one vswitch or using two vswitches ?

Many thanks

I have a new hyperV server joined to domain. since I do not have production VM configured on the new host. I thought of using it for testing the addition of Win2016 DC in my 2008 r2 DC production env. 

I converted both my production DC (physical) with disk2vhd. copied them to hypervisor and spun them back on new host. Created a virtual private switch and assigned the private switch to each vm network. change IP address on DCs to same as production and deployed windows 2016 core and win10 and assigned IP address similar to production network instead of self assigned APIPA as my converted domain would not function with APIPA. 

Would it be safe to install ADDservices on windows 2016 server without impacting production domain as they are all in private network but with same ip. I can see it does hit host and other guest VM in production with ping. I guess it would be save to introduct windows 2016 for test and simulate before I do it in production. On reason I have to complete the test is I still use domain.local for internal therefore I have to do a thorough test before adding win 2016 DC in production 

Hi,

I have three Hyper-V hosts - two are Hyper-V Server 2016, and one is Server 2016 Standard edition. Each server holds two VMs - a domain controller, and an application server. I use Nakivo for backing up all three hosts, which supports Hyper-V RCT and is configured to create "forever incremental" daily backups. It usually works great, but there is one weird issue with it, and it happens only on the Server 2016 Standard edition host - after I reboot one of the VMs it hosts, the next backup will be huge - as if it was the first time I am backing up this VM.

It is also worth mentioning that this specific host is of an older hardware model (new R440 vs. R510), and is physically located on a site which is different to the other Hyper-V hosts and the backup server (symmetrical 100Mb FC, though).

Has anyone ever seen anything like this?

Going to jump right in because I'm just completely stuck with what's going on and Microsoft has been zero help under our SA contract.

I have an eight (8) node Server 2016 Hyper-V cluster.  The nodes are split between two Dell chassis, if that matters, with a dedicated host management network/private network, iSCSI network and fiber channel connection to each blade using individual switches in the chassis.  The CSVs consist of six (6) iSCSI all-flash backed LUNs and six (6) FC spinning-disk backed LUNs, with one iSCSI flash LUN for a quorum disk.  Most of the VMs are held on the iSCSI disks, for performance reasons, with data VHDs being held on the FC LUNs.

When a machine is properly paused/drained to be rebooted, for any reason (patching, maintenance, etc.), when it rejoins the cluster after being rebooted, all of the cluster disks in the GUI start to flash.  The stats, such as the size of the disk, disappear and then reappear quickly.  In the events, on the rebooted node, I can start to see "'STATUS_BAD_NETWORK_PATH(c00000be)'. All I/O will temporarily be queued until a path to the volume is reestablished." error messages.  This event throws for seemingly random CSVs, as it could be all of them, or a subset of disks, but it never seems to be consistent.  Mind you, the node is still paused, it has all of its networking capabilities and is properly communicating with the other cluster nodes.

At this point, the other nodes begin to throw errors on the same disks the rebooted node was complaining about, especially the nodes that are the owner of those disks.  Then, the majority of times, the CSV will fail and run through recovery options to come back up on another node, causing several VMs to crash in the process.

One last odity in this is that even though the rebooted node complains about a BAD_NETWORK_PATH for some of the FC disks, none of the FC data disks have ever failed, only the iSCSI all-flash LUNs.  This is more detrimental to me though, because the majority of OS disks are held on these LUNS.

Any help is greatly appreciated, thanks!

Windows Servers Synchronization

We are lookinb to replace our Vmware private cloud with new hardware and hyper v.(running about 20 windows VMs)

Hardware is Lenovo SAN storage and 4 x physical servers connecting to the SAN with fibre channel. Note one of the servers is a hit spare for redundancy.

We will be using Windows Server 2019 Datacenter but how do we configure so if a server fails we can run thise VMs up quick smart on the spare host?