Quantcast
Channel: Hyper-V forum
Viewing all 19461 articles
Browse latest View live

Error using Window Server Backup on 2012R2 Hyper-V to network share

$
0
0

Hi

I have a Windows 2012 R2 Hyper-V server. It runs a Windows 2012 R2 VM (called server-1).

I want to backup the VM to a network location (\\network-1\server-1_backup$). To do this, I installed Windows Server Backup from the command line and configured a backup to look like this:


C:\Users\admin>wbadmin enable backup
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2013 Microsoft Corporation. All rights reserved.

The scheduled backup settings:

Bare metal recovery : Not Included
System state backup: Not Included
Volumes in backup: (null)
Components in backup: HyperV\server-1
Files excluded: (null)
Advanced settings: VSS Backup Option (FULL)
Location to store backup: \\network-1\server-1_backup$\
Times ofday to run backup: 04:00

 

But when I run this backup manually, I get the following error:

C:\Users\admin>wbadmin start backup
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2013 Microsoft Corporation. All rights reserved.

Do you want to create a backup using the same configuration that you use forscheduled backups?
[Y] Yes [N] No y

The backup operation to Scheduled backup target is starting.
Creating a shadow copy of the volumes specified for backup...
Summary of the backup operation:
------------------

The backup operation stopped before completing.
The backup operation stopped before completing.
Detailed error: A component critical volume failed to snapshot.
Log of files successfully backed up:
C:\Windows\Logs\WindowsServerBackup\Backup-23-02-2015_08-49-55.log

Log of files for which backup failed:
C:\Windows\Logs\WindowsServerBackup\Backup_Error-23-02-2015_08-49-55.log

ERROR - The shared restore point operation failed with error (0x8100010c)
No valid component or volume to snapshot.

A component critical volume failed to snapshot.

 

The log file then looks like this:

Writer Failures
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
Instance Id: {3976D373-854E-4527-B85D-7B61924C8597}
Writer Name: Microsoft Hyper-V VSS Writer
Writer State: 0
Failure Result: 81000112
Application Result: 0
Application Message: (null)
   Component: 1DAF1C56-0635-4043-A933-E97A62EBC139
   Logical Path:
   Component Result: 8100010D
   Component Message: Component reports path on network share which cannot be snapshotted. (0x8100010D)
   Component: 30144C93-56A2-4259-B276-86D59AC767E9
*-----------------------------*
Application backup
Writer Id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
   Component: 1DAF1C56-0635-4043-A933-E97A62EBC139
   Caption     : Offline\server-1
   Logical Path:
   Error           : 8078001D
   Error Message   : The operation ended before completion.


The odd thing is that if I set this up from a Windows 2012 Server using the GUI to exactly the same network destination, the backup works no problem. It just doesn't work when using Server 2012 R2 Hyper-V configured through a command line.

Any help appreciated,

Andrew




Hyper-V incremental backups

$
0
0

Hello.

In a Hyper-V 2012 R2 cluster, with multiple nodes, I witness the following behaviour. When a VM migrates to a different node, all VMs on that node are backed up full. Even though the schedule is to be incremental. If importan; we use transportable vss backup, presenting the snapshots to a backup server.

Slow migration rates for shared-nothing live migration over teaming NICs

$
0
0

I'm trying to increase the migration/data transfer rates for shared-nothing live migrations (i.e., especially the storage migration part of the live migration) between two Hyper-V hosts. Both of these hosts have a dedicated teaming interface (switch-independent, dynamic) with two 1GBit/s NICs which is used for only for management and transfers. Both of the NICs for both hosts have RSS enabled (and configured), and the teaming interface also shows RSS enabled, as does the corresponding output from Get-SmbMultichannelConnection).

I'm currently unable to see data transfers of the physical volume of more than around 600-700 MBit/s, even though the team is able to saturate both interfaces with data rates going close to the 2GBit/s boundary when transferring simple files over SMB. The storage migration seems to use multichannel SMB, as I am able to see several connections all transferring data on the remote end.

As I'm not seeing any form of resource saturation (neither the NIC/team is full, nor is a CPU, nor is the storage adapter on either end), I'm slightly stumped that live migration seems to have a built-in limit to 700 MBit/s, even over a (pretty much) dedicated interface which can handle more traffic when transferring simple files. Is this a known limitation wrt. teaming and shared-nothing live migrations?

Thanks for any insights and for any hints where to look further!

disk2vhd blue screen on start up

$
0
0

Hello

I have a stand alone win08R2 which I would like to convert and then add to my Hyper-V server.

win08R2: dell precision with mirrored HDD.  HDD is partitioned into 2 partitions (d and D)

win2012 R2: hyper-V is a dell R610 Raid 1 (2drives) raid 0 (4 drives)

disk2vhd is completes no errors, but on boot it blue screens and then reboots into recovery mode:

I have tried the following fixes and nothing seems to work:

http://blogs.technet.com/b/jonjor/archive/2011/10/04/vm-does-not-boot-following-p2v-or-disk2vhd.aspx

http://forum.sysinternals.com/win2k8-r2-p2v-failure-to-boot-vm_topic30732.html

among a few others.. similar but no luck.

can anyone direct me to a better solution??

How to specify only possible owner of the VM in Hyper-v cluster (Windows 2012R2)

$
0
0

Good day,

Wewant to preventthe migration of virtual machinesbetween the cluster nodes in indows 2012R2 Hyper-V cluster.

How to specify only possible owner of the VM in Hyper-v cluster (Windows 2012R2) ?


SQL clustering

Is possible to install Hyper-V on windows 7 Enterprise ?

$
0
0
Is possible to install Hyper-V on windows 7 Enterprise ? if yes 64bit or 32bit? 

WS2012R2 - Storage Device version mismatch 6.0 vs. 4.2 - Linux Guest

$
0
0

I have a WS2012R2 Hyper-V host that has a vendor provided Linux based vhd. When that guest boots I get:
"A storage device in 'Server' loaded but has a different version from the server. Server version 6.0 Client version 4.2 (Virtual machine ID). The device will work, but this is an unsupported configuration. This means that technical support will not be provided until this problem is resolved. To fix this problem, upgrade the integration services. To upgrade, connect to the virtual machine and select Insert Integration Services Setup Disk from the Action menu."

I am not sure if there are newer LIS since the newest ones I can find are 3.5 from Jan 2014 and that doesn't match the reported version number. I want to tell the vendor what they need to do to upgrade but I am not sure.

Also if a VMs integration services are upgraded to latest 2012R2 level will VM still function on 2008R2? The vendor wants a single image and won't upgrade if it breaks older OS I am sure.

Thanks.


Brian Hoyt

SCVMM R2 - "Incomplete VM configuration" and other bugs like "failed" status

$
0
0

Noticed a lot of machines in SCVMM go into an irreversible "INCOMPLETE VM CONFIGURATION" status.  All options to manage the machine are then grayed out.  A couple options like "repair" and "refresh" are available, neither of which solves the problem.  These machines are up and running with no related errors in our Hyper-V cluster.  There is also one in a "failed" status with the same symptoms.  

When is this bug in SCVMM going be fixed?  This is supposed to be enterprise VM management software?  Right now, I can't even manage 10 virtual machines with SCVMM because of a BUG.  I have to go to the failover cluster manager or the Hyper-V manager.  

I really don't want to wipe out the entire cluster from SCVMM and readd it, because removing the cluster from management uninstalls the SCVMM agent on all servers.  Needless to say, adding the cluster back to SCVMM management would (ridiculously) require a reboot of all servers in the cluster to "reclaim storage."  Just confirmed that this will happen in my test environment.

If there is a supported way to fix this, please let me know. 

I am by far not the only person that has noticed this problem (try google), but there are no good supported solutions out there.   




Hyper-V host crash and live migration - what happens?

$
0
0

Hello there,

it would be great if you could help me understand how live migrationworks on a sudden host crash of a cluster node.

I know that the cluster functionality mounts the vhd file on another host and runs the VM.

But what happens to the VM itself? Does it crash too and is simply restarted on another host?

To my knowledge the RAM of the VM is run in the RAM of the host, wo I would assume that is all lost on a host crash?

Thanks for any help understanding this,

Best regards, Marcus

Server 2012R2 looses vEthernet switches and cannot stop a starting Vm.

$
0
0

We have three 2012R2 Host Servers in a Failover Cluster, there are 14 Hyper-V VM’s in the cluster.

Yesterday Host3 went down because 3 network adapters disappeared. That left 2 servers (Host1 and Host2) active (that’s sufficient to run all the virtual servers). But for some reason all the virtual servers automatically moved to only one host server. One server cannot support all the virtual servers. However this server tried to run all the virtual servers which made none of the servers active. It showed all the vm servers “starting” but never “running”. By rebooting the host server that held the VM’s, all the VM’s automatically moved to the other good host server and the same thing happened.

So here are the 2 problems that happened:

  1. On Host3 three network adapters disappeared. And could not be recovered without re-installing the operating system. These are needed for the VM’s to run. The adapters are created when virtual switches are created in Hyper-V. The 3 are vEthernet (LAN Virtual Switch), vEhternet (iSCSI2 Virtual Network), and vEthernet (iSCSI 2 Virtual Network)

    2. There does not seem to be any way of turning off a VM when it is in the “Starting” state.

What is recommended size of System drive to keep operating system files , paging files and Memory Dump of hyper-v host.

$
0
0

Hi ,

I want to setup hyper-v host with 128 GB RAM  , Windows 2012 R2

What is recommended size of System drive  to keep operating system files  , paging files  and Memory Dump?

I tested to using 150 GB  , but when the server is crashed, there is no free space to keep memory dump file.


Ramy

How to configure Hyper V VM replication between 2 different sites (located geographically at 2 different cities)

$
0
0
Hi all,

I would like to know how to replicate VM's between 2 different sites which are entirely located at different parts of the cities and also
they are on different domains. Both Servers are running HyperV 2012 R2 Standard. As initial phase I have copied the VM's files  (.vhd and other config files) from Site A to Site B.

In this case, can any one please guide me on how to achieve this replication between 2 different sites.

A quick response is much appreciated...

Thanks in advance. 

Veeam Backup solution

$
0
0

Hi,

We already have a backup solution in place which is IBM Tivoli storage manager. We noticed that Tivoli storage manager is not suitable for backing up virtual environment. Since we are using this software for AIX, Linx, IBM I etc systems and databases.

Is it possible to integrate Veeam Software with TSM and using the existing tape library?

Regards

Sanjay

WSB fails with event ID 521 error 2155348001

$
0
0

This server is a Windows 2008 with Hyper-V and recently upgraded to R2.  For over a year we have had backup issues when using Windows Server Backup where it fails and the Hyper-V VSS writer is waiting for completion.  Typically restarting the server allows me to get a backup.  What can I do to troubleshoot this or should I call Microsoft?

KB 2979256

$
0
0

Is there a work around for this issue which will let us fix VMs with the issue in situ?

http://support.microsoft.com/kb/2979256

Also - if i understand the problem correctly, we are not meant to upgrade the Integration Components of 2012 R2 VMs via offline servicing at all? What if there is an upgraded needed? What are the best practice methods? 

Cheers.


Issues with continued use of Shared VHDx

$
0
0

Hi all,

I have been struggling to get Shared VHDx to work properly for the last week or so.  I have a two 2012 R2 file server VMs clustered sitting on a Windows Server 2012 R2 Hyper-V cluster, I would like to use Shared VHDx for the Quorum Disk Witness and for the File server cluster storage.

Initially when I first create, share and add the VHDx to the two file servers it works without an issue, the file server cluster role will live migrate and storage stays accessible.  However after a period of time e.g. overnight if either of the servers are shutdown/restarted they will not restart.  The error I receive is:

'FS1B' failed to add device 'Virtual Hard Disk'.

Failed to open attachment
'Path to disk\Quorum.vhdx'. Error: 'The request is not supported'.

'FS1B': Cannot get information for attachment 'Path to disk\Quorum.vhdx'.

Failed to open attachment 'Path to disk\Quorum.vhdx'. Error: 'The request is not supported.'.

I have searched around online and came across a couple of people with a similar issue, one fixed it with adjusting his Network Binding (this did not help me).  If I turn off the sharing on the VHDx the server it is attached to will boot fine.

I have also made sure the networking and storage access to the Hyper-V hosts are identical and that all four servers are up to date patching wise.

I don't think I'm missing anything but it really doesn't want to work and driving me a little nuts.

Thanks!

Hyper-V - 2 node cluster goes down if one server shutsdown

$
0
0

Hi all,

I built a 2 node cluster with tiered storage and then I started doing some tests:

* Drain one node and all the VMs moved to the other node, perfect

* shutdown the drained node.

The entire cluster crashed!!! The remaining node is trying to re-connect to the iSCSI SAN without success.

* I booted the drained node. And it would not re-connect to the iSCSI SAN either. I had to force the reconnect in the iscsi control panel to make it re connect.

So why would shutting down one node kill the cluster ? Sure it was the node that had the tiered pool online, but even then, isn't failover cluster supposed to put that one back and working on the other node ?

Why did the active node lose the iSCSI connection too ? It had VMs running on it prior to the shutdown of the other node. My DC that was running on that other node is also now un available, can't ping it or anything.

So what did I miss in the configuration of the cluster ? I followed the msdn 2 node hyper-v cluster doc.

I am really worried atm since I had over the past 3 months a ton of issues with hyper-v going from using tiered storage, shutting down nodes, MAC address on the VMs and the hosts,... I thought that after hyper-v 2008, Microsoft had really made some progress with Hyper-V but I truly regret not going with VMWare again this time around.

That cluster was supposed to go into homologation phase tomorrow at the datacenter but now I am unsure if I ll ever be able to trust it to work.

The SAN is an MD3200i which is reported as Hyper-V ready.

Any hint on where I have gone wrong would be appreciated.

Regards,

Edit: even from the host with powershell I was not able to shutdown the DC and reboot it clean. Said the integration services were not reachable... it is a 2012 R2 servers...

Edit2: One of my VM is gone ! Can't even find the file on the disks either locally on the hosts or on the SAN. WTF!!!

Hyper V 2012 , error cant access the virtual machine settings

$
0
0

Hello Guys,

we have 2 Hosts installed with Windows Server 2012 Standard. These 2 Hosts are configured as an Failover-Cluster. Also we have an IBM Storwhize connected directly via SCSI to both hosts. Its configured as a shared volume in Failover Cluster Manager.

we have the following problem:

From time to time, when i want to open hyper-v settings on host002 , i cant access this, i get this error:

cant access hyper-v settings, running out of memory or disk

But my disk space and RAM is OK. the strange thing is that the virtual machines are accesable via RDP.

To solve this issue temporarily i have to reboot HOST002. If i reboot host002 then it works, but host001 has the same problem.. I think its an issue with the Failover Configuring, because all that started when we have shutted down both servers, then i think failover cluster wanted to move these virtual machines (high availability) and then get in errors.

it would be very glad if anyone can help me (remote or whatever)

All virtual machines are running perfectly, but i cant access the settings and our backup tool VEEAM cant backup the virtual machines..

Thanks Edmond

Merge process when shutting down a VM (Can it be stopped with no issues?)

$
0
0

I'm having a mail server downtime to complete critical updates and also add a 2nd network adapter.

I'm aware at this point that this server is currently running on a 1.6TB avhd file (and I see the parent last modified date back from the last time we had shutdown).

My question is....when I shutdown the VM and the merge process begins, will I be able to add the adapter I need?

If so, will the merge process let me start up the VM at that point when I am ready.

I wont have a long enough downtime for the file to merge into the parent. I believe that would take upwards for 20 hours.

My only goal right now is to add that hardware and reboot a couple of times for updates.

I have only a 3 hour window. Any advice here?

Designing Remote Site Failover (Hyper V Replication & Failover)

$
0
0

Hi All,

We are looking to run a pure Windows 2012 R2 environment for our main office (New York) and want to design as best an instantaneous failover solution to a remote site (Chicago) given we have various and numerous outage problems.

MAIN OFFICE (NEW YORK)

SonicWall NSA220 Router

Dell Server 1 (running Hyper V 2012 R2)

  1. DC Server VM (DC, DNS, DHCP, File Share, etc)
  2. DirectAccess Member Server VM

Dell Server 2 (running Hyper V 2012 R2)

  1. Exchange Member Server VM

Dell Server 3 (running Hyper V 2012 R2)

  1. Database Member Server VM1
  2. Database Member Server VM2

50 Workstations

REMOTE OFFICE (CHICAGO)

Sonicwall NSA220 Router (connect to MAIN OFFICE via VPN)

10 Workstations

Everything I've been readying about Hyper V 2012 R2's awesome Replication & Failover solution leads me to believe we can simply setup the same amount of servers to the Remote Site, connect the two sites via Sonicwall VPN, and then copy the VM's to them using Replication (first local copy, then replication over WAN VPN), and then...when a failure occurs, we simply spin up the VMs at the remote site for near instantaneous failover (along with changes to DNS, MX records, etc.)

Is what we are considering a solid, cost effective solution?  Or should we be setting this up some other way?


Viewing all 19461 articles
Browse latest View live




Latest Images