When you get a file error “permission denied”, it indicates one of two things:
- At the time of backup the file was exclusively locked by the operating system or by an application.
- In this case the backup agent cannot access the file. The solution is to not have the application open at the time the backup runs (in cases such as Quickbooks), or to use a backup plug-in for cases such as SQL database files.
- The backup agent did not have the privileges (permission) required to access the file(s). To verify whether a certain user has permissions to read a file, you can use the Windows to View effective permissions on files and folders
For the Server Edition, the backup agent service runs as the LOCAL SYSTEM user by default. You’ll need to do either of the following:
- Change the permissions of the file(s) so that the LOCAL SYSTEM user can at least read them, – OR –
- Change the credentials under which the backup agent service (eSiloCron) runs so that it can at least read the files (Use the Services MMC Snap-in, services.msc).
- We recommend creating a separate domain user with all of (and only) the necessary credentials required for the eSiloCron service to avoid it from not working if and when you change your password. It is also advisable to have this user’s password never expire.
- Restart the eSiloCron service so that it starts using the new credentials (THIS IS REQUIRED).
For the Standard Edition, the backup agent runs as the currently logged in Windows user. You’ll need to do either of the following:
- Change the permissions of the file(s) so that the currently logged in Windows user can at least read them, or
- Log in to Windows as a user that has the proper permissions to read the file(s).