If you don’t want to change permissions then you can alternatively just uninstall the windows updates that caused the issue in the first place. Solution 3: Uninstall the windows updates You can also upgrade to 11.0.1 from an older version of BackupAssist if you have valid BackupCare.If you have BackupAssist v11 you can simply upgrade to the new BackupAssist 11.0.1 release to automatically work around the issue. The security implications of this change are mild because SMB permissions are not changed, however you can reduce the scope of the ACL change by using individual user accounts instead of “Everyone”.It may also be that you are experiencing a different problem. Run a Check Destination to test the change, and double check the settings is the backup still fails.
Changing the ACLs behind the share permissions does not affect the attack surface of the share, as long as the share is only accessible to the backup machine. Note: Please do NOT change the permission controls for the SMB share, as this may leave your backups vulnerable to hackers, and it will not solve the issue anyway.Use Windows Explorer to open the Security properties for the DataContainer.vhdx, and Edit to assign “Full Control” to the “Everyone” group.If you are not maintaining BackupCare and are running an older version than v11, follow these steps: In particular, the user that Windows uses to mount disks over SMB can be assigned differently, so access rights for the virtual disk file may need to be altered to allow access for the different user, until Synology have a fix. The above windows updates have changed the way permissions are handled using SMB protocol on Synology NAS devices. DataContainer backups to Synology NAS devices may start to fail with BA4801 error, due to Windows updates released in April Affected environmentsīackupAssist Classic versions up to v11.0.0 running on all Windows OS with the updates listed here:
0 kommentar(er)
