The FBackup tasks have been configured with administrative accounts, either the built-in "Administrator" or a second account, which I'll call "Admin2".
If the FBackup tasks use the built-in Administrator account, the tasks run without error. However, I do not want to use this account unless absolutely necessary.
If the FBackup tasks use the Admin2 account, we have Source and Destination errors. I was able to avoid these errors by reconfiguring the task in Task Scheduler so that the task runs with highest privileges. The files are backed up, but we still see these warnings in the logs:
Code: Select all
Failed to set privilege SE_BACKUP_NAME : L'appelant ne bénéficie pas de tous les privilèges ou groupes référencés [1300]
Failed to set privilege SE_RESTORE_NAME : L'appelant ne bénéficie pas de tous les privilèges ou groupes référencés [1300]
The Admin2 account does possess the "Back up files and directories privilege" via its membership in the Administrators group, so I don't understand why these warnings occur. To be even more certain that the Admin2 account has the requisite privileges, I made it a member of the "Backup Operators" group. This had no effect -- the warnings still appeared in the log when the backup job was run.
I know that FBackup forum staff don't consider this warning to be particularly serious if the files are backed up correctly.
However, I'm trying to set up FBackup so it runs without any warnings or errors of any sort.
Do you have a suggestion for configuring the Admin2 account so it can run an FBackup task without these "failed to set privilege" warnings?
regards, AndyA