locked
Schedule Backup as administrator error "You must be a member of the local Administrators or Backup Operators groups to schedule a backup." RRS feed

  • Question

  • Logged in as administrator
    Going through Administrative Tools -> Windows Server Backup -> Backup Schedule
    Setting up a new remote backup on a different server (requiring different login credentials to save to that location if it matters)

    Everything goes through until I hit Finish on the Confirmation page, then after a few moments it gives me this:

    Error:
    "You must be a member of the local Administrators or Backup Operators groups to schedule a backup."

    It does let me run the Backup Once through Windows Server Backup to the same location, but not through Backup Schedule.


    From: http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2management/thread/7ef89d20-a305-4d17-a376-e13fc0468edc/
    Wednesday, January 27, 2010 1:06 AM

Answers

  • Hi,

    To configure scheduled backup to network location, there is a restriction in Windows Server Backup that the user configuring the backup must be a valid user on the local machine (where backup source is) and the same user should have write access to the network share. To overcome the scheduling issue, would suggest to add the user having access to the network share as a BackupOperator on the backup source machine.

    ------------------------------------------------------------------------------- This posting is provided "AS IS" with no warranties, and confers no rights
    Wednesday, January 27, 2010 9:51 AM

All replies

  • Hi,

    To configure scheduled backup to network location, there is a restriction in Windows Server Backup that the user configuring the backup must be a valid user on the local machine (where backup source is) and the same user should have write access to the network share. To overcome the scheduling issue, would suggest to add the user having access to the network share as a BackupOperator on the backup source machine.

    ------------------------------------------------------------------------------- This posting is provided "AS IS" with no warranties, and confers no rights
    Wednesday, January 27, 2010 9:51 AM
  • Well, that seems to fix it, but the restriction seems silly when there is a popup asking for network login credentials (and the error is not in any way helpful).

    Thanks
    Wednesday, January 27, 2010 2:05 PM
  • Hello,
      thanks for confirming that it resolved the problem. We take your feedback and will take up this as a feature request in the next Windows Release.


    Thanks,

    Bikash Agrawala [MSFT]

    --------------------------------------------------------------------------------- This posting is provided "AS IS" with no warranties, and confers no rights


    Monday, February 1, 2010 10:48 AM
  • I too was facing this error when trying to create a scheduled backup on a Windows 2008 R2 server instance for Exchange 2010. Abhinav indeed provided the answer to my problem. Only because it was still a bit cryptic, I will try to clarify the solution for others Googling this topic.

    What I did: create a scheduled backup using Windows Server Backup for Exchange 2010 to a network share with a specific backup account from my Active Directory

    The error I got: You must be a member of the local Administrators or Backup Operators groups to schedule a backup

    The solution: Add the backup user account from Active Directory to the Backup Operators group locally on the machine using the server manager/Configuration/Local Users and Groups/Groups. I already had added the Active Directory group Backup Ops in which this backup account resides, but that did not work. You need to add the backup account directly to the local Backup Operators group . Also make sure the backup user account has access to the network share to which you want to perform the backup. These rights may be set through the Active Directory group in which you placed the backup user account and this does not (though it may) be the backup user account directly.

    • Proposed as answer by VanillaDeath Friday, April 26, 2019 11:52 AM
    Friday, October 15, 2010 12:30 PM
  • Dear All,

    Thanks for your valuable comments.

    In my case one server in dmz and others servers and storage at inside and they are part of domain when I trying to schecule backup on dmz server same message appears " You must be a member of the local Administrators or Backup Operators groups to schedule a backup"

    In that case how I can schecule my backup on dmz server while I can only take backup on shared network folder.

    Need your suggestion...

    Regards,

    Azhar

    Sunday, April 10, 2011 11:23 AM
  • This is ridiculous restriction, unnecessary, and very annoying too
    Wednesday, July 6, 2011 12:09 AM
  • i am trying to administrator account and he as read and write access to the share folder.....

    administrator user added in Backup Operators groups too ,to schedule a backup. but the issue as when i am trying to take backup once  to the shared folder the backup got successful.

    But i am trying to take schedule backup getting error after giving credentials 

    and i am  sure administrator account has read/write access permission to that folder   and also for taking backup user in backup operations group too

    Friday, March 23, 2018 11:10 AM
  • The user name being used for accessing the remote share folder is not recognized by the local computer


    Friday, March 23, 2018 11:28 AM
  • How is this done on a domain controller? When I try to add the local account it says "This snap-in cannot be used on a domain controller. Domain accounts are managed with the Active Directory Users and Computers snap-in." But as far as I know you can't create a local account using AD UC.

    So if I can't add a local account to the DC, then how can I setup a backup schedule with Windows Server Backup that saves to a network share?

    UPDATE: This doc applies to Server 2008 but seems like it is still true for Server 2012.

    Found my answer: 

    The following conditions are requirements for scheduling daily domain controller backups:

    • The destination volume for the backup must be on a separate hard disk from the source volumes. You cannot perform a scheduled backup to a network shared folder.

    • The external storage device for the backup must be connected to the domain controller that you are backing up.

    Source:  https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc754843(v%3dws.10)

    • Edited by Mop Closet IT Wednesday, November 21, 2018 4:34 PM Found more info
    Wednesday, November 21, 2018 4:13 PM
  • Teşekkürler Ederim. sayenizde sorunu çözdüm. bilgisayarım+yönetim+localuser and group +group+domain yedekleme kullanıcısına yetki verdim.
    Saturday, December 29, 2018 12:18 PM
  • Couldn't find Local Users and Groups in Server Manager, but if you go to Winkey+X/Computer Management (or Run lusrmgr.msc) on the source machine, you'll find Local Users and Groups. This fixed it for me! You'd think the error would be more specific :P
    • Edited by VanillaDeath Friday, April 26, 2019 11:59 AM added lusrmgr.msc as another option
    • Proposed as answer by CB27a Wednesday, August 5, 2020 10:59 PM
    Friday, April 26, 2019 11:56 AM
  • Thank you thank you thank you @VanillaDeath. 

    I spent nearly half an hour banging my head against this issue when I should have been sleeping.

    I had the backup user in the Domain Backup Operators Group and it worked fine on the Primary Domain Controller, but Windows Server Backup on an application server on the same domain kept throwing up this stupid message saying

    "windows backup cannot schedule a backup because the user credentials provided are not a member of the local administrators or backup operators group".

    In hindsight, the message is actually clear. It clearly says "local" but that's easy to miss after a long day way past bed time.

    Added the user to the local backup operators group using lusrmgr.msc as suggested and it worked.

    I suppose it makes sense from a security perspective, but then again if a bad actor has access to one of your machines, then you're kinda in trouble already. 

    Wednesday, August 5, 2020 11:08 PM