3,013 questions
@DreamCatcher-0722 FYI I opened a ticket with Synology yesterday but have yet to hear anything back.
KB5001347 (April 2021 Update): Issue with Server Backup on Hyper-V Server 2016
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 92%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED0%3C/text%3E%3C/svg%3E)
DreamCatcher-0722
21
Reputation points
Are there anyone else seeing issues with Windows Server Backup on Hyper-V Server 2016 after installing KB5001347? We can reliable reproduce failing backups at stage "system state".
After uninstalling KB5001347 backups run as expected again. After re-installing KB5001347 backups stop working again.
The error message(s) in backup management console is/are:
- The mounted backup volume is inaccessible. Please retry the operation.
- The operation ended before completion.
The following error(s) is/are logged in event viewer:
- 517, Backup: The backup operation that started at 'UTCTIMESTAMP' has failed with following error code '0x8078004F' (The mounted backup volume is inaccessible. Please retry the operation.). Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
- 10170, HYPER-V-VMMS: Requester reported unsuccessful backup for the virtual machine 'MACHINENAME'. (Virtual machine ID GUID).
Thank you in advance!
Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V
Windows for business | Windows Server | Devices and deployment | Set up, install, or upgrade
Windows for business | Windows Server | User experience | Other
20,221 questions
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 60%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDD%3C/text%3E%3C/svg%3E)
Doug Dafforn 21 Reputation points2021-04-20T00:23:30.38+00:00 What are you using as the backup destination? I have been waiting for this type of inquiry as I have observed the same thing happening with WIndows 2016 and 2019, both serving as hyper-v hosts. I'm also getting the message 'The mounted backup volume is inaccessible'. This is happening when I attempt the backups to a synology NAS device.
I have been able to backup successfully to a windows-based network share.
Like you, I can remedy by removing KB5001347.
-
DreamCatcher-0722 21 Reputation points
2021-04-20T05:16:10.337+00:00 At our site it is a Synology NAS device too. It‘s regardless of using SMBv2/3.
Sign in to comment
20 answers
Sort by: Most helpful
-
Doug Dafforn 21 Reputation points
2021-04-21T10:46:02.067+00:00 -
DreamCatcher-0722 21 Reputation points
2021-04-21T14:21:39.153+00:00 That sounds great. We would be happy to get further information from your site about the ongoing process and what Synology says.
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(208, 41%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELZ%3C/text%3E%3C/svg%3E)
Ladislav Zelinka 51 Reputation points2021-04-22T08:02:12.363+00:00 I made it too
https://account.synology.com/en-global/support/2784859/detail2021-04-21 11:17:59
Dear customer,Thanks for contacting Synology Technical Support.
If your SMB service works fine on another Windows I suspect that something wrong is with your updated Windows Server. From my expierence I can recommend to check SMB version on server and NTLM settings on it. If you are using DSM 7.0 your Windows needs to have enabled NTMLv2 (Send NTLMv2 response only). Please also check which version of SMB are you using on your DSM. If you are using SMB1 you need to enable it on Windows device. Below you can find more information about Windows configuration.
https://learn.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/network-security-lan-manager-authentication-level
https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3
.....
== NOTHING :( -
Doug Dafforn 21 Reputation points
2021-04-22T11:25:33.253+00:00 I had a conversation with synology yesterday and they reviewed the logs of their device in relation to the moment of failure in the backup. I use a product called Backupassist that sits on top of windows backup. It is at the very end of the backup after all drive data is backed up that an 'application backup' quickly sweeps across the VMs and this is where the backup fails. The synology tech speculated that something has potentially changed in the vss writer due to the April cumulative update, or that possibly there is an NTFS command occurring at this final stage that is causing a problem since the synology device does not use NTFS. The NTFS command idea is interesting since I can successfully run the same backup jobs to a windows-based share without issue. I have also reached out to Backupassist to see what is occurring in this final VM application backup stage. Is it some kind of checkpoint removal that is failing?
@DreamCatcher-0722
@Ladislav Zelinka
Sign in to comment -
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(220.8, 78%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELW%3C/text%3E%3C/svg%3E)
Luc Wuyts 6 Reputation points2021-05-06T05:16:09.62+00:00 Giving "Everyone" all rights to the container seems to solve this problem.
-
DreamCatcher-0722 21 Reputation points
2021-05-06T07:22:31.603+00:00 Seems you might confirm things @Ladislav Zelinka detected. Giving Everyone permissions might be a workaround but not a solution. You might reduce this to giving affected machine accounts permissions to the container. Does this work for you too?
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(227.2, 15%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EK%3C/text%3E%3C/svg%3E)
kc 1 Reputation point2021-07-03T10:11:12.397+00:00 This helped me thank you.
Brand new Synology DS, backing up server 2016 with system state, they were constantly failing (all other backups worked fine) on the NAS (but backups did work locally). I've tried so many things these past few days, and this worked, giving "everyone" rights to the vhdx files.I've opened a support ticket with Synology as well, as I would prefer a better solution, but at least I have my backups working and can enjoy my weekend now.
Sign in to comment -
-
JiayaoZhu 3,926 Reputation points2021-04-20T06:42:53.487+00:00 Hi,
Thank you for your posting!
Based on your descriptions and the link that you gave us, I would like to check first that have you tried the ways mentioned in the link that you yourself found. If so, can you give us some information about the result?
Secondly, based on these three error codes: 10170, 2155347997 and '0x8078004f', your issue may be related to VSS issue. Specifically, you may encounter backup corruption or configuration file corruption when your VSS requestor is trying to backup your server.
Here is an article that covers a bunch of available ways for you to resolve your issue:
https://www.auslogics.com/en/articles/fix-errors-0x807800c5-and-0x8078004f/
Please note: Information posted in the given link is hosted by a third party. Microsoft does not guarantee the accuracy and effectiveness of information.
You may also need to check if there is any offline backup destination shown after rescheduling backup with fresh destination. Remove these offline backup destinations and this shall mostly resolve the issue.
Thank you for your support!
Best regards
Joan--------------------------------------------------------------------------------------------------------------------
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
-
DreamCatcher-0722 21 Reputation points
2021-04-20T08:01:42.353+00:00 Hi @JiayaoZhu ,
I've already checked via DISM/SFC for corruption in component store. There is no issue at all. The VSS writers are working correctly too. As @Doug Dafforn wrote this seems to be related saving backups to a Synology NAS.
The bunch of articles you mentioned and a lot more of them I processed before I opened this thread. ;-)
Interestingly I monitored that some of the affected systems started backup automatically after (un-)installing KB5001347 (regardless of the monitored result).
Thank you
-
Ladislav Zelinka 51 Reputation points
2021-04-20T08:16:27.727+00:00 I have same state.
After update all server, all windows backup work not.
I run windows backup from commandline:
wbadmin.exe start backup -backupTarget:\192.168.223.6\backup\Banka\2 -user:XXXXX\XXXXX -password:XXXXX -include:d:\Banka -vsscopy -quietand result:
*wbadmin 1.0 - Backup command-line tool
(C) Copyright 2013 Microsoft Corporation. All rights reserved.
Note: The backed up data cannot be securely protected at this destination.
Backups stored on a remote shared folder might be accessible by other
people on the network. You should only save your backups to a location
where you trust the other users who have access to the location or on a
network that has additional security precautions in place.
Retrieving volume information...
This will back up DATA(D:) (Selected Files) to \192.168.223.6\backup\Banka\2.
The backup operation to \192.168.223.6\backup\Banka\2 is starting.
Creating a shadow copy of the volumes specified for backup...
Please wait while files to backup for volume DATA(D:) are identified.
This might take several minutes.
Creating a shadow copy of the volumes specified for backup...
Please wait while files to backup for volume DATA(D:) are identified.
This might take several minutes.
Scanning the file system...
Please wait while files to backup for volume DATA(D:) are identified.
This might take several minutes.
Found (0) files.
Scanning the file system...
Found (0) files.
Scanning the file system...
Found (0) files.
Scanning the file system...
Found (0) files.
Scanning the file system...
Found (5) files.
Scanning the file system...
Found (5) files.
Scanning the file system...
Found (5) files.
Scanning the file system...
Found (5) files.
Scanning the file system...
Found (5) files.
Scanning the file system...
Found (5) files.
Scanning the file system...
Found (5) files.
Scanning the file system...
Found (5) files.
Scanning the file system...
Found (5) files.
Scanning the file system...
Found (5) files.
Scanning the file system...
Found (5) files.
Scanning the file system...
Found (5) files.
Scanning the file system...
Found (5) files.
File identification is complete.
The backup of volume DATA(D:) to \192.168.223.6\backup\Banka\2 is starting...
The backup of volume DATA(D:) could not be completed. Error: The mounted backup volume is inaccessible. Please retry the operation.Summary of the backup operation:
The backup operation stopped before completing.
The backup operation stopped before completing.
Detailed error: The mounted backup volume is inaccessible. Please retry the operation.
Log of files successfully backed up:
C:\Windows\Logs\WindowsServerBackup\Backup-20-04-2021_07-39-36.log
Log of files for which backup failed:
C:\Windows\Logs\WindowsServerBackup\Backup_Error-20-04-2021_07-39-36.log
There was a failure in preparing the backup image of one of the volumes in the backup set.
The mounted backup volume is inaccessible. Please retry the operation.*I send backup to Synology too. Local backup is OK
-
Ladislav Zelinka 51 Reputation points
2021-05-04T13:14:35.063+00:00 I try this:
Command: wbadmin.exe start backup -backupTarget:\192.168.228.6\backup\Banka\1 -user:BckUpZA01\Backup -password:XXXXXXXX -include:d:\Banka -vsscopy -quiet
command is ended with error:
...
The backup of volume DATA(D:) could not be completed. Error: The mounted backup volume is inaccessible. Please retry the operation.
...WireShark:
32594 117.188137 192.168.228.2 192.168.228.6 SMB2 186 Session Setup Request, NTLMSSP_NEGOTIATE
32595 117.188735 192.168.228.6 192.168.228.2 SMB2 300 Session Setup Response, Error: STATUS_MORE_PROCESSING_REQUIRED, NTLMSSP_CHALLENGE
32596 117.189043 192.168.228.2 192.168.228.6 SMB2 342 Session Setup Request, NTLMSSP_AUTH, User: PNM\ZILINA01$
32597 117.194366 192.168.228.6 192.168.228.2 SMB2 131 Session Setup Response, Error: STATUS_LOGON_FAILUREWhy PNM\ZILINA01$, it is source computer account ? In command is BckUpZA01\Backup !!!!!
-
DreamCatcher-0722 21 Reputation points
2021-05-04T13:56:09.43+00:00 I think things you discovered go into the right direction. There seem to be other authentication issues with Fujitsu Server View Power Monitoring and KB5001347 too, I only saw in dependency of authentication issues.
Microsoft is very quiet about the support request I opened. Maybe they are working on a fix and hopefully release it with may's cumulative update.
-
Ladislav Zelinka 51 Reputation points
2021-06-28T11:43:03.767+00:00 I am now ok, Synology support fix my NAS-es. Now work backup well.
-
DreamCatcher-0722 21 Reputation points
2021-06-28T11:49:09.307+00:00 Strange. Synology support told me I have to wait until official patch. :-(
Sign in to comment -