So… you decided to finally configure backup for your servers, and just when you’ve chosen the “backup solution”, troubles start.
What do we need for doing Windows Server backups?
Nothing too fancy – we can use the built-in Windows Server Backup (feature that needs to be installed through Server Manager, PowerShell, …) combined with some location (network share, disk, volume) with enough free space. (yes, we can also use some other backup software, but this is not the topic here)
Let’s say that we have installed Windows Server Backup feature and chosen a network share for our backup location. The one other thing we need on this share are the right permissions for our service account (an account under which the backups will be done – for example, BackupAccount).
So, we go to this share (\\BackupLocation\MyBackups\) and check if our service account has the required permissions:
Everything looks fine (our service account has permissions, folder is shared and accessible from the source server – yes, Windows Firewall is also configured properly ).
We go back to our source server where we configure our backup schedule as a Full Computer backup, once a day, to the backup location previously mentioned, using the service account previously specified for this backup job. Everything goes fine.
Then, just for fun, we try to run our backup schedule (just to see if everything works as it should). We click on the Backup Once option (with Using the previously scheduled… option), and just at the end of this wizard, we receive the following error, saying that our backup destination is not writable (yes, it’s the good old Windows Server 2008 R2, but it really doesn’t matter… the same happens on newer/older versions as well ):
We’ve checked (and double-checked) everything – our share, permissions, Windows Firewall, and “who knows what”, and this wizard still says we cannot write to the backup destination! This must be an issue with the free, out-of-the-box backup solution.
The issue here is that I’m running the Windows Server Backup console as “myself” (i.e. my user, for example, SERVER\tomica) and I don’t really have the required permissions on the backup share (I’m not a member of the local Administrators group on the backup destination and, as you may remember, only our BackupAccount has the required permissions set).
So, is this an issue?
No, not really because our scheduled backup will complete successfully (it will be running under the user account with correct permissions on a backup share).
And, if we really want to make this first backup right now, we can run it from the Task Scheduler console (by checking the “Allow task to be run on demand” checkbox first, for the backup task).
Hope this helps someone with similar problems (it’s kind of a dumb “issue”, but…).