Cannot setup Windows Server Backup - Backup Schedule with Remote Shared Folder

zack1989 1 Reputation point
2021-04-12T14:22:16.193+00:00

Hi,
I am a new user of Windows Server 2019. I want to schedule a backup to the remote shared folder. While I can use the Backup Once option, I cannot use a scheduled backup. It prompts all the time username and password window. When I set up Backup Once for the first time I put the correct credentials and the backup went fine. After that, I did not have to put the credentials again. But when I set up the scheduled backup I cannot pass the login/password windows even when I put the correct credentials. I have recorded it and you can see it on the video: https://youtu.be/hHf_Lipwjdg
Do you know how can I set it up?

Windows Server Backup
Windows Server Backup
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Backup: A duplicate copy of a program, a disk, or data, made either for archiving purposes or for safeguarding valuable files from loss should the active copy be damaged or destroyed.
450 questions
{count} votes

4 answers

Sort by: Most helpful
  1. JiayaoZhu 3,911 Reputation points
    2021-04-13T03:34:39.917+00:00

    Hi,

    Thank you for your posting!

    Based on your descriptions, please check if it is running as the account you are testing to access the shared folder - sometimes it is running as an account which may not have permission on target folder. Or you can check if it has some sharing permissions incorrectly set on your destination folder.

    I found this blog's issue is similar with yours (although its environment is server 2012, it should be applied to your 2019 server as well):

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/b45eec29-0c8c-4fc0-b984-b607e5fb16ba/using-windows-server-backup-to-back-up-files-to-network-shared-drive?forum=winserver8gen

    In addition, I suggest you not to post the location of your shared folder for security reason, you can use screenshots and black your location with pen.

    Thank you for your time!

    Best regards
    Joan

    --------------------------------------------------------------------------------------------------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  2. zack1989 1 Reputation point
    2021-04-13T07:11:42.383+00:00

    Hi,
    thank you for your answer. I thought it is not a problem with permissions since it works just fine for Backup Once - the storage folder can be accessed by WSB. The problem is with scheduled backup. I am using the same account for both backups but it does not work for the scheduled. Do you think that it still can be a problem with permissions?
    Yeah, I should have not put the location of my shared folder...
    Thak you,
    Wojtek

    0 comments No comments

  3. JiayaoZhu 3,911 Reputation points
    2021-04-14T09:44:38.49+00:00

    Hi,

    Thank you for your reply!

    After my research, it seems that your issue is still related with permissions. Sometimes, even your account is granted all NTFS permission, if your account is not enabled with Full Control, you still cannot do scheduled backup because of your permission issue. So, just try to copy or create a new folder in your drive and to see if you have full control over your account. If not, you may need to sent your feedback to the system management team. The article is here:

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/b45eec29-0c8c-4fc0-b984-b607e5fb16ba/using-windows-server-backup-to-back-up-files-to-network-shared-drive?forum=winserver8gen

    In addition, you can just go to %windir%\logs\windowsserverbackup to see if there is any error codes or messages related to your Windows server backup. By default, tracing is enabled in Windows Server Backup to preserve logs. These traces will be present in files under this directory. More information:

    https://social.technet.microsoft.com/Forums/windowsserver/en-US/1cdb9617-7ea5-4f5a-a89a-e492a118920c/backup-log-location?forum=winserverfiles

    Thank you for your support!

    Best regards
    Joan

    --------------------------------------------------------------------------------------------------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  4. JoshKell 1 Reputation point
    2021-06-11T14:37:34.667+00:00

    Same backup issue, same settings that work on one 2016 server don't work on another, same permissions, same network location, same domain, same user. Server that it does not work on, does allow the one-time manual run using the same credentials, works fine. That tells us our folder path and credentials are working. But then when attempting to setup a schedule it initial accepts the credentials when registering the job, but when you select finish and it starts creating the backup schedule it does not like the user/pw and prompts user name or pw is incorrect and there's no getting past it. It's ridiculous, and it's not a permissions thing, that's what low level tech says, not criticizing just saying. I believe the prompt would be different if it was a permission's issue. Sure one should always check the permissions on the network share, set and reset them several times just to make sure but people who come here have done that a million times already. What I think is happening the backup job is looking for one set of credentials for the net share (a domain user), but then is looking for a local user to setup the back up job's schedule, least that's how it read in to it and it's the only thing that make sense beyond it's just a permissions thing. Seems when yo run the one-time backup, it does not look for that second authentication because you're not setting up a schedule, so then to me that's why that method works. If my assumptions are all correct I have no idea how to fix this, and why does it work on one server an not other when they are both the same 2016 OS using the same credentials and permission to run the backup? Riddle me that one. My advice is try an create a backup script, rather than using the backup wizard and setup a scheduled task for it, or use 3rd party app or a managed IT service for backups, it's what MS wants us to do anyway. Otherwise you will be manually running that backup daily/weekly/monthly which ever you do.

    0 comments No comments