Experienced users will always recommend keeping a copy of your Windows drive or at least your documents and other files safe at another location, as it might not be possible to get those files back again. If it’s not bad enough to have to reinstall Windows again afterwards and then apply the hundreds of Microsoft updates, any personal files will also have been lost as well if they were not backed up beforehand. To resolve this problem, in the VM's settings, change from Production checkpoints to Standard on guests that are domain controllers running pre-2016 OS, when the Hyper-V host is running Windows Server 2016.One of the worst things that could happen to a computer user is losing the contents of the Windows drive, whether it’s through corruption, self inflicted damage or hardware issues. The problem may be related to the new Hyper-V Production Checkpoint architecture. This is a known issue for pre-2016 Domain Controllers running in VMs on 2016 / Win10 Hypervisors.
Hyper-V solution 2 - Change the Production checkpoints to standard Mistakes can render the system inoperable.
Warning: Changes to the registry should only be performed by an experienced Systems admin. Restart the service 'Hyper-V Volume Shadow Copy Requester' or restart the guest.Writer name: Microsoft Hyper-V VSS Writer If Last Error is anything other than No Error then there is an issue with that writer. Check the Last Error and State output specifically. This will provide an output of all VSS writers known to Windows on that machine. To do this, open an elevated command prompt and run the following command: vssadmin list writers If the reason for the error is a failing VSS writer, it's recommended to find which one is causing the issue. Solution 2 - Check for failing VSS writers You should also run a registry cleaner after the other backup solutions have been uninstalled.
It is best practice to only have one backup solution installed at any one time. If you have (or had) more than one backup program installed on your system, disable / uninstall all of the programs except for BackupAssist NextGen, and run the backup job again. Many backup application have their own proprietary snapshot manager which can cause conflicts with other backup solutions installed on the system. Solution 1 - Check if multiple backup applications are installed Review the solutions and follow the ones that apply to your system and the error that you have encountered.Īt the end of this section, is a section specifically for Hyper-V backups. Volume Shadow Copy Error 0x80042321 - some snapshots not imported Resolutionīelow is a set of solutions for many of the common Volume Shadow Copy Errors that may occur during a backup. Volume Shadow Copy Error 0x80042321 - some snapshots not imported
0 kommentar(er)
