Apologies if this is not the right forum.

So I was preparing a new server to host virtual machines. This is a Dell PE r710, Dual quad-core Xeon processors, 48 GB RAM, 2x 72 GB SAS drives. The server has Hyper-V Server 2008 R2 installed. iSCSI volumes hosted in a Dell EqualLogic SAN will host the actual virtual machines. We have 5 of these with similar setups, 3 of which are setup in a cluster. We have 2 set aside for additional projects. These will not be clustered as they will be hosting Lync virtual machines. Anyway we have 1 server setup and working with 2 VM's. The 2nd server will initially host 2 additional VM's. My goal was to format the iSCSI volume on the 2nd server and prepare it to host VMs. Except I accidentally logged into the 1st server (it's one of those days - I was interrupted as I was typing in the server name into Remote Desktop and it auto-populated the first server instead of the 2nd) and begin formatting the volume. Needless to say Lync stopped working and the VMs crashed. I immediately recognized my mistake and stopped the format but obviously it was too late.

I was hoping I could recover the data on that volume. We have a trial of this software called GetDataBack NTFS edition. It can recognize the volume ok and it can scan it and see files. Unfortunately it does not see actual VHD files. Instead what happens is that it sees the VHD files as separate volumes/partitions/etc and recovers the data within the VHD files. Not sure if it should do that, waiting on a response from Runtime. Kind of cool in a way if we ever needed to recover data within a VHD file. Anyway, does anyone know of software that can recover data from a volume but not scan the contents of the vhd file and include that data in the recovery? By this I mean I want to recover the actual VHD files, not the data within. Perhaps Virtual Machine Manager can do something? We do have it installed and manage our VM's with it. It would save us the trouble of re-deploying Lync. Apparently there's a lot of ADSI edits needed to undo the changes Lync did to AD/ Even migrating users back requires some ADSI edits. Trying to find those online someplace just in case.

We did not have backups yet of these 2 VMS as we just recently got them setup and have moved a few users over (some of us from IT). We still had some configuration/tweaking/adjustments to make before migrating the remainder of our OCS users. I know, I know, backup backup backup. The SAN we have can even do snapshots of iSCSI volumes but we didn't even think of enabling it yet.

Regardless in what happens with the VM's, I enabled Windows Server Backup and will immediately setup nightly backups once the VM's are operational again. I will also have our SAN admin enable snapshots, and just for laughs I will also enable snapshots on the individual VM's. We're also currently testing out Data Protection Manager. Kind of wish we already had it implemented....sigh...

Thanks,

Banging my head against a board with a nail in it...

Hi Folks

I while ago I posted about an iSCSI backup up issue on this VM Windows 2012R2 Server. I have over the intervening period solved the iSCSI issue by routing it through the host server and presenting a filesystem to the disk manager in the said VM Server. I foolishly thought my backups would start again but of course they don't :(

Using the Windows native backup program I setup the backup for full backup with the system state and bare metal recovery as well the data and system drives.

The backup fails with the error 'A virtual disk support provider for the specified file was not found' and subsequent 'there was a failure in preparing the backup image of one of the volumes in the backup set'

I looked in the registry for this "FsDepends” key, change REG_DWORD value “Start” from “3” to “0” and its already set to 0

There is no other backup solution installed on this VM Server that I can disable or uninstall so I am a bit stumped.

The backup sets up the backup and formats the drive for the backups without an issue so I assume the issue is elsewhere and not with the backup destination drive.

Your thoughts would be appreciated please?

Regards

Jerry Barrett

Jerry Barrett

I took my Windows Server 2016 Datacenter test server in my home lab (Dell R710 with two X5650s and 32GB of RAM) and installed Server 2019 Datacenter on it to try out the new features that are centered around VMs (Hyper-V) and data deduplication. The OS install went fine, but after enabling Hyper-V in Server Manager, the system goes through its normal reboot that occurs during Hyper-V enablement, then it proceeds to boot loop. Windows Server 2019 install media's boot repair does not fix the issue, and I cannot get in via Safe Mode. Any advice would be greatly appreciated.

Hi Everybody, 

We are running Windows 2012 R2 Hyper-V Server, and our main production server VM is running Windows 2012 R2 on a dynamic VHDX on a 700GB partition. This VM has been running successfully for about four years without much trouble. 

A database application was installed last week, and since this has happened, I've seen the hard disk space being reduced day by day until now we are reaching a point where the whole partition will soon be full. Within the VM, the disk usage does not increase, but the VHDX is growing by about 8GBs per day. 

What I think is happening is that there is some process that they are running at night that is copying a huge amount of information and then deleting it, which gives us a sort of white space effect. So I will have to down the server some evening to get back the white space. I'm just wondering if I should use the opportunity to change the disk to Fixed VHDX and if this would help with the problem. 

Any advice appreciated. 

thanks, 

Jonny. 

Hi!

I have a Hyper-V-Host with 2 network adapters. One is for management of the host, one is for Hyper-V/virtual machines. What I don't understand is how the IP configuration of the virtual ethernet adapter on the host should be done. Everythings working fine without doing any configuration at all, but is this the best practice or does this have performance issues?

Thank you!

is there a way to roll back an automatic Windows update, or otherwise recover this hosed VM?

While I was away from my PC (Win 10 Pro host running Hyper-V), a Windows 10 VM it hosts decided to update itself. The VM had been working fine since it was created last year (with usual automatic updates) until now.

The VM boots to the login screen, then says "This might take some time" and "These updates help protect you in an online world" and "Leave everything to us" hahaha! (plus "Don't turn off your machine"). Some ten minutes later there's a popup:

Popup Title: "Location is not available"   

Popup text: "C:\Windows\system32\config\systemprofile\Desktop is unavailable. If the location is on this PC, make sure the device or drive is connected or the disk inserted, and then try again ..."

Clicking OK to dismiss the popup gets a black desktop with only a recycle bin. Clicking the Start button does nothing. Task Manager shows no processes, and no users.

Winkey+R lets me run stuff (if it's on the path), internet is OK (ping, git, etc., work) but networking won't do NET USE  (gets system error 1222)

Any ideas for diagnosing/fixing the problem would be greatly appreciated. This VM is my development system; I do have an old VM Checkpoint but will lose my tailored environment if I revert to that. Luckily all source files are in github

thanks

I have a physical Windows Server 2016 running as AD, DNS, DHCP and File Server. I want to virtualize the the server using Disk2VHD on the existing server and then demote the physical server as a domain controller. I want the set up to be exact so that the customer wouldn't notice any changes (they are running some applications off of file shares). Would this be possible to achieve? 

Hi

We use a Nvidia Quadro P4000 on a HPE DL380 Gen10 with Windows Server 2016 Hyper-V and Passtrough the Card with DDA to a Windows Server 2016 VM.

W've installed the latest drivers. But after a while, without any user input, the card shows the error code 43.

Hello,

I use Hyper-V on Windows 10 for Docker.

Both Default Switch, and Docker created switches get EnableMulticast set to 0 after reboot. This prevents link-local name resolution from working. This seems to happen only on this machine, other machines (perhaps running older versions of Windows 10) do not experience this.

What is setting this value and how to prevent this?

Good day,

I've read up on a couple of blogs online regarding server/virtualization licencing but am now even more confused than before I started.

This is what we want to do:

We have a Physical server with the following specs located in a data center which we want to use for Hyper-V:

- Sockets = 2

- Cores = 8

- Logical Processors = 16

The physical server will be loaded with Server 2016 Standard but not the core version as we need to load more roles on it.

We want to load 3 virtual machines also with server 2016 standard in Hyper - V.

If we do it through volume licencing, how many licences do we need to purchase to cover the Hyper-V server as well as the virtual machines?

Is there a post or something that can simplify the MS Licencing as it seems I'm not the only one that this is confusing to..?

Thank you

Hi,

we are trying to import virtual machines in Hyper-V2012 R2 but it fails with an error Hyper-V did not find virtual machines to import from the location, the folder c:\something\something could not be found. You might not have permission to access it.

Folder structure -Root folder with the name of machine-> 2 folders (virtual hard disks and virtual machines) -> In virtual hard disks folder there is .vhd file and in Virtual machines folder  there is the XML file and also folder with the same name as XML file in which it has BIN and VSV file. 

These machines were created on a host (hyper-v 2012 R2) which is destroyed because of some irreparable issues. So those machines are basically not exported from anywhere. 

Is it because of these machines were not exported from anywhere at first place(because ".exp" file is not available), if yes is there any way to import these machines?  (there are a lot of machines, so ruling our creating empty virtual machines option) 

Thanks in Advance.

Hello,
I'm using Backup Exec 20.1 to perform daily backups of virtual machines, but quite offten the backup end up failing due to error: 

V-79-57344-37935 - Snapshot Technology: Initialization failure on: "VRTSRV::\\backup.blade.local\Hyper-V?Virtual?Machine\DC_b". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).

Snapshot technology error (0xE000942F): Cannot capture a snapshot of the virtual machine volumes. Ensure that the Hyper-V Virtual Machine Management Service is running and the status of the Microsoft Hyper-V VSS writer is Stable.

Check the Windows Event Viewer for details.

When i look for the writer in the "vssadmin list writer" output, the writer is not present there. If I restart Virtual machine management service and run vssadmin again, the writer appears.

Sometimes many backups can complete without the writer dissapearing, but then the writer dissapears again. I can't find any error on warning in Windows Event Viewer.

I'm running Windows server 2016 and the VM's are running on the same server as the Backup Exec is installed on.

So is there any sollution to this problem or a way to find out what is happening to the writer ?

Thanks

Martin

Hi,

So I am testing with Hyper-V Server 2019, which I deployed to three brand new HP Proliant gen10 machines. I'll test on them for a while before putting them in production. Installation was a breeze, as with Hyper-V 2016. However, I can't seem to enable RDP on Hyper-V Server 2019. When I enable through the menu, it says it's done so, but alas, netstat -a reveals there isn't even a process listenening on port 3389.

I checked the registry, HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server is correct. The required services are running. Firewall is completely disabled through netsh for testing. Remote administration is working fine, RDP is not listening at all.

Anyone else ran into this?

Hi,

BackupAssist could not back a VM SQL server if Backup (volume shadow copy) is checked inside the Hyper V/Integration Services. Can you help with a command or script to stop/uncheck Backup (volume shadow copy)?

Thank you so much.

Hello, I've been running a functioning virtualization set on a small Server 2016 install, running a half dozen VMs. Everything was working fine for months, but I let Windows update last night and when it rebooted suddenly none of the VMs would startup. When I attempted to check them with the management tool it tells me it's connecting to the Hyper-V Virtual Machine Management Service, and it never stops saying that except to sometimes say it cannot be reached. This is all locally on the server, not remotely. This has not happened in the past. When I attempt to stop or restart the Hyper-V Virtual Machine Management Service it takes a long time and then ends with Error 1503 saying that it cannot stop the service as it took too long to respond.

I tried rolling back the update, and that changed nothing unfortunately. This is pretty disastrous for me, hopefully someone can help me out!

Edit: As far as I can tell none of the VMs boot, none appear to be on the network switch, and I cannot access them through any means.

The Get-VM command hands powershell, and whether the service is stopped or not (which is does eventually stop after 10+ minutes) the network switch information in the Hyper-V configuration area for switches never becomes available.

Hi,
We have 4 node Hyper-V cluster. HP DL servers + VNX5100 and SAN fabric connection. 2nd node was reinstalled and rejoined to cluster. After 2nd node had rebooted manually, cluster lost CSV disk.

I have spent some days triing to figure out what happend, but have no answer yet. Please, give me a hend! Any advice would be appreciated.

***VMNODE-2
Rebooting started
000009fc.00000a24::2016/11/30-13:58:43.582 INFO  [CS] PreShutdown notification.

Disk paused before moving
000009fc.00001bec::2016/11/30-13:58:43.676 INFO  [DCM] PauseDisk completed on all nodes for resource 'Диск кластера 2'
000009fc.00001bec::2016/11/30-13:58:43.676 INFO  [DCM] short name is C:\CLUSTE~1\Volume1

Disk gone offline
00000814.00001c20::2016/11/30-13:58:43.926 INFO  [RHS] Resource Диск кластера 2 has come offline. RHS is about to report resource status to RCM.

Group moved from node 2 to node 3
000009fc.00001668::2016/11/30-13:58:43.926 INFO  [RCM] move of group f333c385-edf6-486b-ab74-9f9549ab310e from vmnode-2(2) to vmnode-3(4) of type MoveType::Drain is about to succeed, failoverCount=0, lastFailoverTime=1601/01/01-00:00:00.000 targeted=true

Success
000009fc.000018a4::2016/11/30-13:58:43.926 INFO  [RCM] rcm::DrainMgr::GroupMoveSucceeded: [DrainMgr] Group move succeeded for f333c385-edf6-486b-ab74-9f9549ab310e

***NODE-1
Disk paused before moving
00000f18.000017a8::2016/11/30-13:58:43.665 INFO  [DCM] PauseDisk completed for resource 'Диск кластера 2'

Disk marked as Bad due to network disconnected node 2

00000f18.000015a8::2016/11/30-13:58:45.777 WARN  [DCM] Marking Bad resource Диск кластера 2 owned by a dead node 2

Cluster couldn't get Disk Resourse
00001424.00001b28::2016/11/30-14:10:45.668 ERR   [RES] Physical Disk <Диск кластера 2>: HardDiskpSetUnsetDiskFlags: Unable to open device \\.\PhysicalDrive4294967295. Error: 2.
00001424.00001b28::2016/11/30-14:10:45.668 ERR   [RES] Physical Disk <Диск кластера 2>: Set CSV disk resource control: Failed to set CSV disk with partmgr. Error 2
00001424.00001b28::2016/11/30-14:10:45.668 ERR   [RHS] Error 2 from ResourceControl for resource Диск кластера 2.

***VMNODE-3
Disk paused
00000f2c.00001620::2016/11/30-13:58:43.671 INFO  [DCM] PauseDisk completed for resource 'Диск кластера 2'

00000f2c.00001200::2016/11/30-13:58:43.968 INFO  [DCM] PreOnline for Диск кластера 2

Connection broke
00000f2c.000012f8::2016/11/30-13:58:55.853 INFO  [PULLER vmnode-2] Parent stream has been closed.
00000f2c.000012f8::2016/11/30-13:58:55.853 ERR   [NODE] Node 4: Connection to Node 2 is broken. Reason Closed(1236)' because of 'channel to remote endpoint fe80::7d06:9916:577f:7aac%18:~51964~ has failed with status (10060)'
00000f2c.000012f8::2016/11/30-13:58:55.853 WARN  [NODE] Node 4: Initiating reconnect with n2.
00000f2c.000012f8::2016/11/30-13:58:55.853 INFO  [MQ-vmnode-2] Pausing
00000f2c.000012f8::2016/11/30-13:58:55.853 INFO  [Reconnector-vmnode-2] Reconnector from epoch 1 to epoch 2 waited 00.000 so far.
00000f2c.000011e4::2016/11/30-13:58:55.869 DBG   [NETFTAPI] Замечено NetftRemoteUnreachable событие, локальный адрес 10.10.10.110:3343  удаленный адрес 10.10.10.109:3343
00000f2c.000011cc::2016/11/30-13:58:55.869 INFO  [IM] got event: Remote endpoint 10.10.10.109:~3343~ unreachable from 10.10.10.110:~3343~
00000f2c.000011cc::2016/11/30-13:58:55.869 INFO  [IM] Marking Route from 10.10.10.110:~3343~ to 10.10.10.109:~3343~ as down
00000f2c.000011cc::2016/11/30-13:58:55.869 INFO  [NDP] Checking to see if all routes for route (virtual) local fe80::9063:add0:f77a:f7a3:~0~ to remote fe80::7d06:9916:577f:7aac:~0~ are down
00000f2c.000011cc::2016/11/30-13:58:55.869 INFO  [NDP] All routes for route (virtual) local fe80::9063:add0:f77a:f7a3:~0~ to remote fe80::7d06:9916:577f:7aac:~0~ are down
00000f2c.000011c8::2016/11/30-13:58:55.869 INFO  [CORE] Node 4: executing node 2 failed handlers on a dedicated thread

Disk connected
00001598.000014f4::2016/11/30-14:00:06.970 INFO  [RES] Physical Disk <Диск кластера 2>: HardDiskpWaitForVolumesToArrive: CSV disk - SUCCESS - opened handle for device \Device\Harddisk0\ClusterPartition2\. Error 0


Connection restored
00000f2c.00000f40::2016/11/30-14:02:49.607 INFO  [ACCEPT] 0.0.0.0:~3343~: Accepted inbound connection from remote endpoint 10.10.10.109:~49172~.
00000f2c.00002998::2016/11/30-14:02:49.607 INFO  [SV] New real route: local (10.10.10.110:~3343~) to remote  (10.10.10.109:~49172~).
00000f2c.00002998::2016/11/30-14:02:49.607 INFO  [SV] Got a new incoming stream from 10.10.10.109:~49172~
00000f2c.00002998::2016/11/30-14:02:49.639 INFO  [SV] Authentication and authorization were successful

Error

00000f2c.00001ed8::2016/11/30-14:02:52.685 WARN  [DCM] IOCTL_STORAGE_QUERY_PROPERTY(StorageDeviceSeekPenaltyProperty): status 31

Disk error
00001598.000016d8::2016/11/30-14:03:07.025 ERR   [RHS] Error 5023 from ResourceControl for resource Диск кластера 2.

Hello,

At our company, we use Veeam to back-up all VMs on our Hyper-V servers.

We ran into an issue, when we needed to restore a sharepoint 2016 server.

The VHDX that contained the MS-SQL database files was corrupted.

** We had several weeks of SUCCESSFUL VEEAM Backups** that when restored, were corrupt.

Veeam support's response is that it is a Microsoft issue.

What is the best practice to test/confirm or otherwise verify that a VHDX and its file system is not corrupt?

The point of backups is to mitigate risk, I can't imagine that we are the only company to experience this or ask this question.

This question is NOT about backups, it is what is the best practice to ensure what is being backed up is valid.

Thank you.

Is there an update on that Microsoft Blog page?

https://blogs.msdn.microsoft.com/san/2011/09/01/the-windows-disk-timeout-value-less-is-better/

Most, not to say all, storage vendors recommend large timeout values (60, 120, 190) to cop with controller failover and the only recommendation from Microsoft would be "less is better" ?

[quote]

(higher value) can make troubleshooting extremely difficult, because on one hand you would have a SQL client application acting slow, and SQL reporting slow I/O, at the same time that there are no events from Windows.

[/quote]

This page probably refers to a scenario that rarely exists : bad link quality with the storage.

In the more frequent scenario of a inaccessible disk, what do you want to "diagnose" ?  You ought to have warnings / errors at the storage array / switch levels to diagnose.

When a disk outage occurs, unless the OS as some resources to find another path, which is handled t the "multipath / mpio" level , there's nothing else to do but wait , as much as possible.

My experience with storage array controller failover is that when the disk timeout [quote] surfaces [/quote] before the failover completes, Windows simply crashs...