Hyper-V VSS on iSCSI

Similar Questions

• Hyper-V backup fails VSS in Windows Server R2 2012

  When I try to do a backup of a VM (just the virtual machine, nothing else selected) on my Windows Server R2 2012 machine, I get the following error:

  I still have to find an answer to this question.

  Log name: Application
  Source: SPP
  Event ID: 16387
  Task category: no
  Level: error
  Keywords: Classic
  User: n/a
  Computer: BitVault
  Description:
  Microsoft Hyper-V VSS Writer writer experienced an error during the creation of the snapshot.  More information:.
  The event XML:
  
   
     
      16387
      2
      0
      0 x 80000000000000
      2746
      Application
     
     
   
   
      Microsoft Hyper-V VSS Writer
     
     
      Writer experienced a transient error.  If the backup process is started, the error does not happen. (0x800423F3)
      Unknown error (0x80004005)
   
  

  It's about getting the VSS event log

  A VSS writer has rejected an event with error 0x800423f3, the writer experienced a transient error.  If the backup process is restarted,
  the error does not recur.
  . The changes that the writer made to the writer components while managing the event is not available to the applicant. Check the event log for events from the application hosting the VSS.

  Operation:
  PrepareForSnapshot event

  Context:
  Execution context: writer
  Writer class ID: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
  Writer name: Microsoft Hyper-V VSS Writer
  Writer Instance ID: {4736e32f-5954-4b83-9ca5-37c560f308d5}
  Command line: C:\Windows\system32\vmms.exe
  Process ID: 3556

  PS C:\Users\Administrator > vssadmin list writers
  vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
  (C) copyright 2001-2013 Microsoft Corp.

  Author name: 'Task Scheduler Writer'
  The writer ID: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
  Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
  Status: Stable [1]
  Last error: no error

  Writer name: 'recorder VSS metadata store.
  The writer ID: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
  Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
  Status: Stable [1]
  Last error: no error

  Writer name: 'Performance Counters writer. "
  The writer ID: {0bada1de-01a9-4625-8278-69e735f39dd2}
  Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
  Status: Stable [1]
  Last error: no error

  The writer's name: "System Writer".
  The writer ID: {e8132975-6f93-4464-a53e-1050253ae220}
  Writer Instance Id: {2ff32bb9-b4dd-4959-bfa9-7ea79b4567ba}
  Status: Stable [1]
  Last error: no error

  Author name: 'ASR Writer.
  The writer ID: {be000cbe-11fe-4426-9c58-531aa6355fc4}
  Writer Instance Id: {4b7e63c6-ecb1-47f2-b317-e665b5de8c8c}
  Status: Stable [1]
  Last error: no error

  Author name: 'Microsoft Hyper-V VSS Writer.
  The writer ID: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
  Writer Instance Id: {4736e32f-5954-4b83-9ca5-37c560f308d5}
  State: [8] failed
  Last error: error renewable

  Author name: 'Dedup Writer'
  The writer ID: {41db4dbf-6046-470e-8ad5-d5081dfb1b70}
  Writer Instance Id: {5ac93c0a-dc01-4564-bac9-23051e2783a7}
  Status: Stable [1]
  Last error: no error

  Author name: 'Shadow Copy optimization Writer. "
  The writer ID: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
  Writer Instance Id: {a24b7ea7-e48b-44eb-9521-585648b7951b}
  Status: Stable [1]
  Last error: no error

  Name of the author: "COM + REGDB Writer".
  The writer ID: {542da469-d3e1-473c-9f4f-7847f01fc64f}
  Writer Instance Id: {b9b0674c-119c-4345-870d-fadc0e7beda4}
  Status: Stable [1]
  Last error: no error

  Author name: 'Registry Writer'
  The writer ID: {afbab4a2-367d-4d15-a586-71dbb18f8485}
  Writer Instance Id: {30a6302b-d5c8-4b9a-a0b7-61049e1c4767}
  Status: Stable [1]
  Last error: no error

  Author name: 'WMI Writer'
  The writer ID: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
  Writer Instance Id: {74ee0321-a546-4f94-a624-c715f2290db4}
  Status: Stable [1]
  Last error: no error

  PS C:\Users\Administrator > Get-VMIntegrationService - VMName

  VMName name active PrimaryStatusDescription SecondaryStatusDescription
  ------ ----                    ------- ------------------------ --------------------------
  Home time true synchronization OK
  House real Heartbeat OK OK
  Pair key / value of home Exchange real OK
  House real stop OK
  House VSS True contactless
  House Guest Service Interface fake OK

  Hello

  Post your question in the TechNet Server Forums, as your question kindly is beyond the scope of these Forums.

  http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

  TechNet Hyper-V Forum.

  https://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?Forum=winserverhyperv

  See you soon.

• Moving from VSS to VDS and how many have

  Having some difficulty deciding to VDS how we should have in our Organization.

  We have 4 clusters all under one site, wait for 1 of them they run all 2 VSS, one for data and one for iSCSI storage. 1 cluster that is different is the last cluster of Production that still turns a VSS for iSCSI, but data are running on a VDS.

  Data of each cluster network is identical and connect to the same basic switch, all the VLANS on all clusters are identical

  Each iSCSI network cluster runs in its own set of switches and do not touch each other so very isolation.

  I'm a fan of join our VDS data network, but I've seen several posts on how to configure for Sites and I was wondering what is the best for our environment.

  I heard that normally it is 1 VDS to rule them all, but I think plus 1 VDS for each cluster and not one for the site.
  The reason behind this is that the role of each cluster is very different and I would like to work on clusters in a vacuum and I know that if I make a change in that it won't have another effect.

  Cluster-1 prod (5 guests) < == cluster of Production for applications outside of our web site main base claim system

  Dev cluster (6 guests) < == pole of development for all the work of development

  UAT Cluster (2 guests) < == user acceptance tests before accepting the changes in demand

  Prod Cluster 2 (2 guests, which has the vds) < == main cluster of Production for our web-based system

  So what you think 1 per site, 1 by cluster or stay with VSS

  First of all, go to vDS probably :-) And on how many vDS, I don't like the idea of a single vDS for the whole environment (including testing) but a vDS for clusters is too if you have clusters with similar roles, and for this reason I propose a vDS for the production Cluster and another for Dev/UAT Cluster.

• The CSV on Equallogic DPM backup storage

  We have a cluster of Hyper-V connection to an Equallogic PS6000e CSV on iSCSI and have recently started to configure the Hyper-V virtual machine protection.

  The question that we see involves the backup expire (VSSADMIN list writers watch time out) and the event logs show iSCSI cannot connect to the target volumes. When I look at the Windows iSCSI initiator (2008 R2) we see all target communication successfully. SUCCESS tools are installed on each Hyper-V host and we have configured iSCSI targets to use CHAP authentication and IP restriction for the iSCSI network.

  If I disable the writer VSS Equallogic (DPM tempted to use it as a hardware VSS writer) backup of virtual machines Hyper-V succeeds by using the Hyper-V VSS software default recorder. Our option is to use only IP iSCSI access restrictions but do we need to provide the DPM server with one interface on the iSCSI network.

  I want to know is what are the side effects of a disabling Equallogic VSS writer using the /unregserver eqlvss on each node of Hyper-V and to return to the recorder VSS Hyper-V software (other than the impact on performance).
  Y at - it a component of the Equallogic SAN on a windows environment that awaits the Equallogic VSS writer to work?

  Not within the DPM.   This is known as an "off-host Backup" or "server less backup" programs such as Backup Exec.  (Called ALA)   NetBackup and Commvault support also, but not of DPM.    DPM cannot just "login", that is, the IP address and the qualified name full name to use.

  Generically, to do this, the backup sw, called Service VSS (Volume Shadow) to calm the system files and the flush cache.  When VSS will do that if our HW vendor's will connect to vss-control over table volume, select the volume, create the snapshot and return (in XML format), the name and IP address.    This information can be used to indicate the version of CLI, MS initiator iSCSI (msiscli) where and how much you connect to.   DPM doesn't have this capability.

  Also MS changed in W2K8 XML format, if the backup server must be the same operating system as the server to be backed up.  W2K3 or W2K8, you cannot mix them to disable the backup host.

  DPM will have to build software to manage the processing of the XML file and tell the iSCSI initiator to connect to.  Put the snapshot in offline mode, and then remove it when finished.   So not an easy task by any means.

• Issue of Dell PS6100 replication and DR

  Hello everyone, I have 2 PS6100 SAN in two other site (site A and site B) for DR purposes. The VM .vhd files are stored in a volume on site A SAN. While the volume is replicated to site b. replication works very well. Our MRC is the following: when A VM site goes down. 1 interrupt us the replication from site A to site B. 2 volume) we turn on the virtual machine to site B. 3) promote us the incoming line to site B. 4) attached to the Hyper-V host using ISCSI initiator. (5) provide online on Hyper-V host volume and assign a drive letter. (5) and then attach to VM. My question is, can the volume PS6100 repeated in volume? So I don't have to go through this process. I would like to just start the VM DR in site B and have the fixed volume. Details of the two sites: WAN link 40Mbps Dell EqualLogic Microsoft Windows Server 2008R2 host servers Microsoft Windows Server 2008R2 VM PS6100

  Hello

  N ° there is no direct replication like this.   You need to watch a replication based on the host for this ability.   You can only promote or clone a replica to access.

  Kind regards

• Migration of the iscsi initiator software to hardware initiator on 2012 Hyper-v cluster.

  Hello

  We have 10 blades x M620 with Broadcom 10gig 57810 M1000e CMC card dedicated for iSCSI Equallogic PS 6110 San.

  Currently software used on cluster hyper-v Windows 2012 connect SAN PS6110 iscsi initiator.

  150 VMS are in production on 15 CSVs.

  We want to change the initiator of the software to the hardware on all our existing blades without CSV output.

  Is it possible on hyper-v cluster 2012 to have 5 blades with initiator software and remaining 5 blades with hardware initiator with same CSV cluster?

  If coexistence of initiator software and material as possible through hosting then I can apply this change a bit on our 10 blades without cluster downtime.

  Hello

  What version of FW EQL do you use?

  Yes, it is possible, however a couple of updates warn first.

  1.) install the latest firmware / boot code and driver for Broadcom cards.

  2.) put the node into maint mode then you can disconnect the SW iSCSI provenance and sign in using the HW iSCSI adapter.

  3.) do not try to do it with an active node / online.

  The advantage of the HW iSCSI adapter reduces the CPU Overload, if you are maxing out the CPU not now, do not expect a large increase in performance after HW iSCSI card.

  Kind regards

• Hyper-V and iSCSI network

  Hello

  We evaluate a migration of vmware for hyperv.

  I try to understand best practices for networks iSCSI comments.

  I have physical 4ports 1GBit dedicated, on the host for iSCSI traffic.

  I like to use all 4 for iSCSI host (vhdx volumes) traffic.

  Now I thought to do 2 of them shared by creating 2 logical switches in VMM, adding 2 virtual network cards for the host to use.

  The new virtual network cards are 10 Gbit. I don't see an option to change them to 1GBit. To me it seems now that the system prefers the 10 GB adapters. My other two physical cards are no more used.

  I tried to do all 4 ports as virtual, but somehow the 4.7EPA ASM does not see virtual cards. He said only: "no network adapters don't find" at the opening of the MPIO settings.

  Should I just ignore this idea to share and use 2 for host and 2 for iSCSI hosts, or is it a medium work?

  It is recommended to devote at least 2 interfaces on the host iSCSI network.  In addition, you must install the Dell EqualLogic for Microsoft host integration tools and install the MPIO feature.  To enable the MPIO in the guest operating system, you must create at least two virtual switches that are related to the physical SAN on the Hyper-V host adatpers.  Virtual machines must be configured with at least two of these virtual switches.  Then, since the guest operating system, configure interfaces with IP iSCSI network, Subnet, etc...  You must also install the Dell EqualLogic for Microsoft host integration tools and functionality MPIO DSM in the guest operating system, if it is not running Windows.  If you use Jumbo frames, ensure that all NETWORK adapters used for iSCSI (NETWORK physical cards, NETWORK cards, Guest OS NICs) are enabled for frames.

  In regards to ASM v4.7 EPA you don't see not cards network for MPIO - there is a known ASM / ME v4.7 bug in Windows Server R2 2012 linked to the EPA.  It is likely that the configuration of MPIO is fine (you can check it out through the initiator Microsoft iSCSI MPIO EqualLogic tab - it's just that ASM / me has a problem of information display.)  This bug has been fixed in version recommended to v4.7 GA HIT/Microsoft - which is intended to be published very soon.

• ISCSI vss for vds VMK migration

  ESXi 5.0.0 469512

  vCenter 5.0.0 455964

  I am migrating standard switches in the switches distributed in my lab and would like to know how to migrate the vmk iSCSI vSS to the vDS.  I read through a few articles and a few vmware docs but have not been able to find any useful info.  Very well, I moved my portgroups\vmks management, vm, and vmotion.  When I try to migrate the vmk iSCSI to the vDS portgroup via the Wizard add a host, I get the following message appears saying that the vmk is always linked to the iscsi adapter.

  "This can only be done while the vmkernel network adapter vmk2 is used by the iSCSI adapter.  Remove the VMKernel network adapter
  adapter for iSCSI to carry out this operation. "

  Do I really need during dissociation of the core of the iSCSI adapter?  I do this manually in some way?  If this is the case, what are the General steps for getting the vmk iscsi migrated successfully?

  Another question...  I read that it is not a good idea to have vCenter virtualized and using vDS and actually Vmware does not support.  Even if it's a waste of nics, vCenter should have it's own of the vss?

  Thank you!

  I had the same error/scenario and that's what I did to make it work.

  (1) I put the host in maintenance mode (optional but wasn't sure of the result)

  (2) entered in the vmhba iSCSI storage--> properties--> tab Configuration network adapters and removed the two vmk, I created on the vSS service in order to configure paths multiple iSCSI.  Once you remove the vmk, your host will see iSCSI data warehouses, but you won't just active multipathing (I went from 2 devices - 4 paths of 2 devices - 2-way).

  (3) went home--> inventory--> Networking and had all my dv port pre-created groups. Right clicked on the dvSwitch and click on manage hosts.

  (4) click on the checkbox for a host that I am train (in maintenance mode) and made the migration as documented in the above pdf.

  (5) I re-entered the vmhba iSCSI storage adapters and added the two new vmk (which should have the same number of vmk carried out the vSS service).

  (6) repeat the other hosts one at a time

  Sorry I had to type this out quickly.  Let me know if I was not clear on some time.

• iSCSI HBA NIC teaming on recommended vSS?

  Hi all

  Just curious when you have two iSCSI HBAS do not use VMwares iSCSI Software initiator you still need to make sure that the following configs are in place? :

  Vmk1 - iSCSI0 - VMNIC1 - Active

  VMNIC2 - not used

  VMK2 - ISCSI1 - VMNIC2 - Active

  VMNIC1 - not used

  Or can you just leave it as active/active with Orig Port ID?

  There is much info on what to do with the software iSCSI initator but what when you have HBA?

  Yes. I added a link to my previous post which illustrates the configuration.

  André.

• Dell Modular Disk storage hardware provider service stops during a VSS backup

  On my Windows 2012 Hyper-V failover cluster, using 2 R710 servers with iSCSI and SAN MD3220I. When the backup (backup of Altaro Hyper-V), I get these 3 mistakes of two servers during the backup every night. Service was set to restart.

  "The service modular disk storage hardware provider ended unexpectedly. It has done this 1 time. The following corrective action will be taken in 60000 milliseconds: restart the service. ' * Event ID: 7031.

  "Name of the failing application: SMPROV ~ 1.EXE, version: 10.84.26.2, timestamp: 0 x 50405699 name of the failing module: ntdll.dll, version: 6.2.9200.16579, timestamp: 0x51637f77 Exception code: 0xc0000374 should compensate: 0x00000000000ebd59 id of the failed process: 0 x 414 Faulting application start time: path 0x01ce9f773f388ae3 of the failing application: C:\PROGRA~2\Dell\MDSTOR~1\VDS_VSS\provider\SMPROV~1.EXE.

  The failed module path: C:\Windows\SYSTEM32\ntdll.dll report Id: d9128602-0c14-11e3-940c-dc509918130b

  Faulting full name of the package:

  On a package of faults application ID: * EventID: 1000 "

  "An attempt was made to issue a command to a password protected storage system and the password is not known. * EventID: 5004 "

  I contacted Altaro and their support has never seen these errors and they claim that they are just a backup VSS, nothing special. My Windows 2008 R2 Hyper-V cluster never saw these errors for more than 2 years.

  Someone help here?

  Julian, my problem is very similar, though different because I use Veeam.  Here is what I posted on the forums of Veeam - if all goes well, it will help you

  Looks like the solution is to uninstall the 'SmVssProvider' who, when running "vssadmin list providers", is listed as:

  The provider name: "SmVssProvider."

  Provider type: hardware

  Provider ID: {24e4e8a3-69cb-4370-8b7b-c5276cd49765}

  Version: 10.84.02

  This service is launching the premium add-on snapshot service that you can buy for the MD by Dell line. If you do not buy it, you don't need this provider. (for as far as I understand it at least)

  To uninstall this provider, navigate to the folder in the folder storage uninstall VDS - VSS MD. By default, it is at:

  C:\Program Files (x 86) \Dell\MD Storage Software\VDS_VSS\Uninstall Modular Disk Storage Hardware Provider (* BE CAREFUL here and double check your path.) There is more than one with a similar path and name.* uninstall program)

  Once inside this folder, run the "uninstall modular disk storage hardware Provider.exe.

  Note that the uninstall program is very rudimentary - there is no GUI or confirmation that it's over. The file and the service will simply disappear.

  This will remove the "SmVssProvider" and the corresponding Windows services:

  'Modular disk storage hardware provider' (SMPROVIDER1. EXE - identical to SmProv ~ 1.exe).

  In my case, service of 'Modular disk storage hardware provider' has been set to start "Automatic", although it did not work, so I was unable to uninstall the provider without stopping I/O or disruption to my VMs. There is no restart request either. Although YMMV so proceed with caution.

• VSS volume control Config Wizzar error

  Hello

  I get an error when I validate the configuration of the VSS feature on my server with the DELL auto 4.5 Snapshot Manager

  Do you have an idea of the problem?

  Thank you very much for your help

  Error:

  Started at 22:01:57

  Waiting for the ASM on the hyper-rd12 host Agent service.
  Preparation 1 host (s) to save the setting changes
  Apply the settings
  Saving settings of PS Group on the "hyper-rd12 host access.

  An error has occurred:

  Error saving access to the PS grpadmin group: 1. specified group WKAddress is not accessible.

  The well-known group address is the IP address of the iSCSI Group.

  Thus, your group has an iSCSI IP address and then each port on the controller has an IP address (eth0, eth1, eth2, eth3 (depending on the model, you can have 1, 2 or 4 iSCSI ports (older models may also have 3 iSCSI ports)).)

  Always use IP iSCSI of the group in the connectivity section in ASM and not the IP address of one of the eth ports.

  If you have used this, disable all but 1 of your iSCSI network cards and try to ping the IP of the Group and all the IPs port. If you can not achieve one or more of them, you need to check your network because it would be a separate iSCSI configuration, which will not work with an Equallogic implementation.

• Snapshots created with the EqualLogic VSS provider are not displayed in SAN HQ

  Hello

  Poster for the first time. We have just implemented an EqualLogic SAN, PS6100X network, and we're having performance issues between our DPM backup server, one of our hosts Hyper-V and VM images stored on the San. I will try to provide as much information as I can

  Environment:

  Dedicated iSCSI using Dell Force10 switches network

  hyper-V (Windows Server 2008 R2) 3 hosts
  -2 hosts has a NETWORK 4 port GB dedicated adapter connected to the iSCSI network; 1 host has connected to the network iSCSI NETWORK 2 GB dedicated ports card
  -Each Hyper-V host computer has a dedicated on the EQ SAN, RAID-50 volume that stores the Hyper-V virtual machines
  -EQ VSS provider installed on all hosts Hyper - V 3 and works correctly

  Using DPM 2010 for backup

  Problem: on Hyper-V hosts 1 and 2, any/all backup activities are very slow. On the Hyper-V host 3rd, however, activities related to backup all are incredibly fast! We compared the NIC configurations, HIT / settings ME and ASM, but we cannot understand why it is so slow on hosts 1 & 2.

  In addition, whenever DPM 2010 tells the EQ VSS provider to create a snapshot, we see the snapshot being created in the EQ Team Manager, but he does not appear in the list of iSCSI connections. According to the documentation SAN HQ, instant and volumes should appear here.

  We also disabled TcpAckFrequency for all 3 hyper-v hosts. It helped a little, but there is still a HUGE difference with regard to backups of the DPM.

  We're pretty sure that there is something misconfigured on the hosts Hyper - V 1 & 2, given that the host Hyper-V 3 has no performance issues.

  How can I get snapshots to appear in the list of iSCSI SAN HQ connections?

  Version information:
  SAN AC = 2.2.0.5924
  Storage Array Firmware = 5.2.4

  There are two different issues in this post for the SANHQ doesn't show only not iSCSI connections.

  Now SANHQ displays the correct total connection number but doesn't provide details of connections individual iSCSI for snapshots, which it should. So in the meantime use Workgroup Manager that shows the details for each snapshot (I know that's not the best answer, it's a short term solution).

  The fact the SANHQ shows details of instant connection does not mean that they aren't here and I can't imagine anything to do with the question of the DPM.

  The real difficulty, look for upcoming beta SANHQ and subscription for this on the EQL support site. You can do it now.

• Error message from DPM 2010 and an unexpected error has occurred on the DPM server during a VSS operation.

  Hello

  I have a server running on a Windows 2008 R2 server DPM 2010

  Currently save a mix of virtual and physical machines, these are a mix of Windows Server 2003 SP2, 2008 & 2008 R2.

  The DPM was previously a bit crumbly, but it was supposed to be caused by lack of disk space. A QNAP server was introduced and configured as an iSCSI target. After the initial problems, it works now.

  EXCEPT

  Three volumes of backup not. They were part of the protection group but they had no point of recovery at all. I deleted their protection groups and have tried to add them to their original groups. These 3 volumes all fail with the following error message:

  An unexpected error occurred on the DPM server machine during a VSS operation.

  Error details: VssError:Shadow copy the specified volume only is not supported. (0x8004230C)

  3 volumes are on 3 different servers.

  All 3 servers are running Windows 2003 SP2

  3 servers have other volumes that are save successfully and consistantly

  There are an additional 3 servers Windows 2003 SP2 that all volumes save successfully and consistantly.

  I can run shadow copies on these three volumes on servers

  All servers run the latest DPM Agents

  3 volumes have unused production capacities, Gig instead of Mb

  The pool of storage on the DPM server has two disks in the storage pool, the local disk has 10 TB of capacity and 45% free, the iSCSI target has capacity to 55 and 78% free.

  There are no. VSS errors in system or application logs (or I've noticed in just about any other log file) on the DPM server or the customer Server

  I have tried to add in the protection group, 3 volumes at once, one at a time or a small directory, or create a new protection group and still get the same errors.

  I ran the Windows updates on these servers

  So far all I can say the disk permissions look OK and match those of the other volumes of work.

  I know that having two drives in the storage pool is not ideal, and it will be changed but not up to what I have fixed the problems on the three volumes.

  Hello

  I suggest you to report this issue in support for Windows Server 2008 R2: http://technet.microsoft.com/en-us/windowsserver/bb512923

  Thank you.

• How can I get technical support for Hyper-v

  Hello

  Recently (28/04/2012) we restarted Hyper-V, which hosted 4 VM, after restarting the server, one of the virtual machine automatically lost all data/changes to the 29/09/2011

  that affected our production department, what could be the problem? This known issue? How can we ensure that this will not repeat?

  Thank you very much for your help!

  Simeon

  Hi Anthony,.

  I never saw this happen by itself.  Normally there is latent snapshots that are attached to the virtual machine.

  Someone probably restored one of them.

  To prevent something like this or to have an audit trail, that I suggest you use SCVMM 2012 it will record all of these respective changes.

  The best of my knowledge, I don't think that it's a known issue or bug.  On a side note, if you don't manage SCVMM 2012 as a management console.  You should at least be back up the virtual machine by using Windows backup.  It will take a VSS based backup workloads.  Store it on an external drive or somewhere on the network.  This will allow a quick restoration of the physical virtual machine if this happens again.

  You should also back up the inner content of the virtual machine.  If you already have the System Center Suite I would say looking DPM "Data Protection Manager 2012."

  I hope this helps.

  Dave

• VSS 8194 ID event after installation of 4.6 STRUCK

  I've seen this with some customers separated now.  The error ID 8194 event appears on the Hyper-V with the installed HIT 2012 hosts. Has anyone seen this?

  The volume shadow copy Service error: error unexpected mark of the IVssWriterCallback interface. HR = 0 x 80070005 access is denied.
  . This is often caused by incorrect security settings in the process of the writer or the applicant.

  Operation:
  Data collection of Writer

  Context:
  Writer class ID: {e8132975-6f93-4464-a53e-1050253ae220}
  Author name: System Writer
  Writer Instance ID: {c4cafe6b-9e92-49e6-b95e-35b7cd4c0cac}

   

  The forum below intimates that existed previously and the achievement points.

  http://social.technet.Microsoft.com/forums/en-us/c66d3ab4-44D7-4a24-bb4b-9b20b3ed56d1/backup-of-HyperV-2012-CSV-intermittent-fails-with-error-0x80042301?Forum=dpmhypervbackup

   

  It seems a solution is to configure removing access to the network service account, it does really is to stop the call to VSS, so no access not denied error is reported. The double \ is the result of the export of registry and is required.

  Windows Registry Editor Version 5.00

  [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\VSS\VssAccessControl]
  "NT Authority\\NetworkService" = DWORD: 00000000