Page 1 of 1

FBackup with admin-level account without errors or warnings

Posted: Mon Apr 11, 2016 4:00 pm
by AndyA
We're using FBackup 6 Build 137 with the French version of Windows Server 2008 x64 Standard to back up data files with various permissions.

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 English translation is, "Not all privileges or groups referenced are assigned to the caller."

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

Re: FBackup with admin-level account without errors or warnings

Posted: Fri Apr 15, 2016 7:15 am
by Adrian (Softland)
Hi,

That is not a warning or error message, it is just an informal message in log. It just tell the permissions of the current user under which the backup is executed.

Re: FBackup with admin-level account without errors or warnings

Posted: Fri Apr 15, 2016 3:53 pm
by AndyA
FOA, thanks very much for your response.
it is just an informal message in log. It just tell the permissions of the current user under which the backup is executed.
That's just it. I've configured "Admin2" to have all the permissions to back up any file or folder. IOW, the caller has all the necessary privileges to do anything on the system regarding backup.

The message says, though, that the account is missing certain privileges. Either the message is erroneous or I don't understand the message.

How can I configure this administrative-level account so that this message does not appear?

Thanks again for your help!

regards, AndyA

Re: FBackup with admin-level account without errors or warnings

Posted: Mon Apr 25, 2016 6:55 am
by AndyA
I'll briefly repeat the question.

An administrative-level user configures an FBackup task on Windows Server 2008 Standard x64 to back up files over which he has full control. Every time the task runs, the log file contains a warning message:

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]
Translated into English, it reads "Not all privileges or groups referenced are assigned to the caller."

Yet this admin account has Full Control permissions on these files.

If the built-in Administrator account is used instead to run the FBackup task, the warning does not appear. (Best practice calls for avoiding use of this account because of the security risk -- it avoids UAC.)

Is the warning message erroneous? Does it derive from an FBackup problem? Can the message somehow be suppressed?

regards, AndyA