Devolutions Server Backup
Hi All
Im getting the following Error when i try to create a Server Backup via administration/backup-manager:
UnauthorizedAccessException - Access to the path '\\server\Backup$\DevolutionsServerConsole_14092021_124414.bak' is denied. at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath) at System.IO.File.InternalDelete(String path, Boolean checkHost) at Devolutions.Server.DatabaseBackupManager.c48aee1ed5d2db179aa186f9bb19c359b(BackupJobEntity ceeec69514a5cf571c01eb5a5f6620347) --- Access to the path '\\server\Backup$\DevolutionsServerConsole_14092021_124414.bak' is denied.
First i tried it directly with the local Path X:\Backup but i got the same.
Folder structure after a failed attempt:
Which user needs full access to this path? The local service user is already local administrator on this vm.
Thanks,
Andreas
All Comments (12)
Hello Andreas,
The account used by the scheduler service needs full rights on the folder. The .bak is done by the SQL Server, then the scheduler service zips the file, adds a password if one is configured, and then removes the .bak. If you confirm that the rights are correct, can you try re-installing the Scheduler service from the Devolutions Server console, I have seen a case where it had to be reinstalled to fix the issue you experience?
When everything is running smoothly, you should be left with the 2 .zip at the end.
Best regards,
Richard Boisvert
Hello,
The account that needs access to the path is the one that is configured in the DevolutionsSchedulerService in the services if the Integrated Security option is enable in the DVLS database settings. Otherwise, it would be the identity of the account that runs the SQL Server service.
Best regards,
Érica Poirier
Hi Richard
Hi Erica
Thanks for the explainations.
SQL Agent User and Scheduler Service User has both write access on this folder.
I also reinstalled the service itself and still the same error.
Sorry for the hiding, but the data is sensitive.
I just want to show you, that ive added here both users (usually not needed, because the service user is local admin).
The second user is the SQL Agent user, which is running on the SQL Server itself.
I also tried adding the SQL Service user - still no success...
Is there any other way for troubleshoot?
Maybe on which step it exact fails?
Thanks,
Andreas
Hello,
Thank you for the information.
As per your first screen capture, it seems that the account is unable to delete the .bak file. Could you please verify that the service account has Delete right in the destination folder?
Best regards,
Érica Poirier
Hi Erica
Yes i can confirm, the Service Account has modify right on the folder and also on the file itself (inherited permissions of the folder).
Best Regards
Andreas
Hello Andreas,
Since the rights are correct, it seems to be a bug that we have seen sporadically; the SQL process that performs the backup still has a lock on the file. We have an internal ticket for this issue, I have linked this thread to it. I will report back once we have more details.
Best regards,
Richard Boisvert
Hello Andreas,
Quick update regarding the issue, it is related to an Out of Memory exception. The server runs out of memory while compressing the file, which is why it does not remove the .bak, this way you still have a copy of the backup.
Additional logging will be added in the next release of Devolutions Server, but for now, the solution is to add more memory to the server.
Best regards,
Richard Boisvert
Hi Richard
Thanks for your input.
Our Devolutions Server is acutal sized with 4 Cores and 8GB RAM. Monitoring shows me, that the Server only has peaks of 75.51% Usage.
Its a really strange problem, because since about 20 days the backup runs just fine. I got a single BAK File yesterday at 16:38, but all other Backups are complete and correct.
Also no Memory Peak there.
Best Regards,
Andreas
Hello Andreas,
After further testing by QA, adding more memory does not solve the Out of Memory exception. The engineering team is still looking into the issue, I will report back their findings.
Best regards,
Richard Boisvert
Hi Richard
I have exactly the same problem and cannot backup the database and therefore I am blocked from updating ...
Our server has 16GB of memory and all the other prerequisites mentioned above are fulfilled. Any solution to that?
Kind regards
Urs
Hello Urs,
The initial issue was fixed in the 2021.2.5 version.
Are you able to perform a backup of the SQL database from SSMS? https://learn.microsoft.com/en-us/sql/relational-databases/backup-restore/quickstart-backup-restore-database?view=sql-server-ver16&tabs=ssms#take-a-backup
Best regards,
Richard Boisvert
Hi Richard
Sorry for the late answer. I lost the issue out of my eyes due to more urgent tasks. Backup directly from SSMS was working correctly. So I set permission for full control to "everyone", which did the job. Backup is now working correctly. Thank you for your support.
Kind regards
Urs