question

DreamCatcher-0722 avatar image
0 Votes"
DreamCatcher-0722 asked DreamCatcher-0722 commented

KB5001347 (April 2021 Update): Issue with Server Backup on Hyper-V Server 2016

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 'UTC‎TIMESTAMP' 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-server-2016windows-server-hyper-vwindows-server-backup
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

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.

0 Votes 0 ·

At our site it is a Synology NAS device too. It‘s regardless of using SMBv2/3.

0 Votes 0 ·
nelsonhernandez-8582 avatar image
0 Votes"
nelsonhernandez-8582 answered

I have a similar problem on Windows Server 2016. It appears to be a permissions issue when accesing the volume on the VHDX drive. At the beginning I though it was a corrupted volume, but the volume is fine.

I tried creating a VHDX drive and it works OK, but formatting it is a different story. Mounting has no volume label and formatting fails with "insufficient permissions" even as Administrator. Uninstalling KB5001347 brings VHDX handling back to normal.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LucWuyts-7118 avatar image
1 Vote"
LucWuyts-7118 answered kc-1079 edited

Giving "Everyone" all rights to the container seems to solve this problem.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Seems you might confirm things @LadislavZelinka-1921 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?

0 Votes 0 ·

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.

0 Votes 0 ·
LucWuyts-9786 avatar image
0 Votes"
LucWuyts-9786 answered nelsonhernandez-8582 commented

Yes, this is only a workaround. It was sugested by Backup Assist support yesterday.
I only added "everyone" to the vhdx, the share itself is still limited to the backup user.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I checked permissions on the backup volume and I see Everyone with special permissions.

What change does have to be applied to volume permissions for the workaround to work? Do the security changes apply to the root folder only or to the root folder and items inside all folders?

0 Votes 0 ·
LucWuyts-7118 avatar image
0 Votes"
LucWuyts-7118 answered nelsonhernandez-8582 commented

I did not change the permissions to the disk-volume and share, only changed permission to the vhdx data container.

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

How can I change permissions to the vhdx data container?

I am backing up to a VHDX hosted on a Synology NAS share and the only way to backup is by not installing KB5001347 on the affected system.

0 Votes 0 ·
LucWuyts-7118 avatar image
0 Votes"
LucWuyts-7118 answered nelsonhernandez-8582 commented

I added everyone via the synology web-interface.
Backup Assist says it is also possible via the normal windows file explorer, but i did it via the synology interface.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

hello,
Did anyone solve this issue? Windows 2012 R2, windows backup (wbadmin) stopped working with NAS Synology after installing KB5001387. I have tested with other device NAS Qnap and here backup was completed without errors.
Regards

0 Votes 0 ·

Currently the only known workaround available is to add read/write permissions to Everyone at the vhdx file, not the shared folder. This can be done by right-clicking the vhdx file and opening properties and adding Everyone on the permissions tab.

0 Votes 0 ·
RadoSK-1715 avatar image
0 Votes"
RadoSK-1715 answered RadoSK-1715 commented

Good News. The Synology team fix this problem. The fix will be included in the next update. The support team sent me a new configuration of the samba daemon. .All windows updates were applied. Everything seems to be ok.

· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi,

So glad to hear that your issue is solved, and thanks so much for sharing the issue. If you do not mind, can you help accept answer for any of the replies in this blog that you think is helpful (you can accept answer for your own reply as well), so that this blog will list on top of our forum. I have seen many people who have a similar issue with yours and we have already reported this issue to our product ream. Now you solved this issue and share to us, it will help many people get access to their solutions more quickly.

Thanks for your sharing again!

BR,
Joan

0 Votes 0 ·

Hi RadoSK,

could you please, please post the "new configuration of the samba daemon " you mentioned above?
II think it would be very helpfull for everyone, who has the same problem (as me!).
Thank you !

: )
Anton

0 Votes 0 ·

I recommend waiting for the update. Better than damaging your NAS setup. I don't think that this specific fix will work on your device. It is not just a simple conf file. Or contact Synology support directly for sent the configuration.

1 Vote 1 ·
RonaldRossi-7767 avatar image
0 Votes"
RonaldRossi-7767 answered

I want to thank everyone on this thread
I have been troubleshooting this for two days
The only way I was able to get it to work was using everyone group with RW on the vhdx file
Oddly Windows Server 2008R2 that is still running is using a VHD file and was unaffected
I think having the everyone group with RW is a security risk
Not being a SAMBA expert I thought it was a security change I made but could not find any documentation to support that fact
Searching and searching I finally found this thread this morning and it revealed what I was thinking
A Windows update out of our control caused this error
Looks like an issue with SMB and Synology, the symptoms are very odd with different features etc
FWIW our regular file backups where unaffected

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LucWuyts-9786 avatar image
0 Votes"
LucWuyts-9786 answered

Backup Assist just releast version 11.01 wich should solve this problem

https://www.backupassist.com/support/en/references/release-notes/current/history.htm

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ZoliSch-8379 avatar image
0 Votes"
ZoliSch-8379 answered

Hi All!

The KB5003671 on W12R2 create same error again. Somebody know how to solve this error in windows server backup?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

DreamCatcher-0722 avatar image
0 Votes"
DreamCatcher-0722 answered DreamCatcher-0722 commented

Synology Support told me they released DSM 7.0 which should fix the issue. It is downloadable here: https://www.synology.com/DSM70

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you for the update. I will be looking for the push to register with the DSM1815+ that is affecting me. It is still on "DSM 6.2.4-25556" and not indicating v7 is available for it. I'd hate to brick the thing, so close to retirement!

0 Votes 0 ·

I can confirm from my site update is working flawlessly and the issue is solved with it. Nothing didn't brick here. DSM 7.0-41890 should be the final release. I don't know, why it isn't pushed actively now.

0 Votes 0 ·