[Bacula-users] Windows backup-API problem

[Christoph . Teuber]

Hi,

i'm trying to move our backup jobs from Windows based BackupExec to Bacula, but  right now I still have to backup a Windows fileserver. I installed version 1.38.4 Bacula Windows client on a Win2K domain controller. My problem is that things only work if the files to backup are readable for the user, the bacula client service is logged on with. For all other files, I get 'ERR=Access is denied'.

Bacula documentation tells me that the Windows backup-API is used, which should solve this problem, but it doesn't. If I add the user which runs the bacula service to the Backup Operators group, this hasn't any effect at all. Using Local System Account for the Service is even worse, because only files which are readable for everyone are backed up with this configuration.

Some postings here on the list told me that I should install the service as Administrator:

"Perhaps you were not Administrator when you installed Bacula, and if you are
then Bacula should run under User Name SYSTEM (and not LocalSystem)."

I did that as it is the only way to install anything on a domain controller, but the services logon-data is always configured for LocalSystem. A tool like Process Explorer tells me, that the service is running as NT AUTHORITY\SYSTEM. A User SYSTEM doesn't exist at all, there is only an unconfigurable group with this name, which of course can't be chosen as a service logon. I added this group to "Back up files and directories" in the Domain Controller Security Policy, but that didn't change anything. Which didn't really surprise me, because the BackupExec service is configured the same way and it is possible to backup all files without this setting.

Does anybody have experiences with problems like this?

Regards
Christoph