Unable to add a new Backup Destination via the Windows Backup Console

Unable to add a new Backup Destination via the Windows Backup Console

Problem:

Unable to add a new Windows Backup Destination to an existing Windows Backup Schedule via the Windows Backup mmc snap-in (Console).

Resolution:

Use wbadmin in an Elevated Command Prompt to add the new Destination Drive to the Backup Schedule.

Run the following command in an elevated command prompt to determine the Disk Identifier of the new disk:

wbadmin get disks

Based on the output, locate the disk that will be added to the scheduled backup. Make a note or copy the Disk Identifier (including the brackets). Be sure to copy the correct ID! If you don’t you could end up formatting another drive. The output will resemble the following:

Disk name: xxxxxxxxxxx
Disk number: x
Disk identifier: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
Total space: xxx.xx GB
Used space : xxx.xx GB

Run the following command to add the new disk to the Scheduled backup. Use the Disk Identifier from the previous step as the “AddTarget” parameter.

wbadmin enable backup -addtarget:{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}

When you receive the following prompt, type Y for Yes.
“Do you want to enable scheduled backups with the above settings?”

Once this has been completed, open up the Windows Server Backup Console and make sure that you can see the new.

The only irritating thing about adding a drive via this method is that it allocated a long name to the disk. It’t not really a problem, its just annoying if you have a number of backup drives labelled as ‘Backup 1’ ‘Backup 2’ etc and then you have a generated disk name that doesn’t suit.

Microsoft KB Article:
https://support.microsoft.com/en-us/help/2009365/error-message-when-you-try-to-add-an-additional-disk-to-a-scheduled-backup-the-filename,-directory-name,-or-volume-label-syntax-is-incorrect

Leave a Reply

Your email address will not be published.

This site uses Akismet to reduce spam. Learn how your comment data is processed.