Quantcast
Channel: Small Business Server forum
Viewing all articles
Browse latest Browse all 8539

SBS 2011 Cannot add a second backup destination, tried option 1 & 3 in KB

$
0
0

I have a newish SBS 2011 server. I configured one backup destination (Seagate 500Gb USB2 external disk) when I first setup the server a few weeks ago. I have now installed all updates, and "fixed" all the inbuilt bugs & errors, and I am trying to add extra backup destinations.I have another 2 USB disks - a Toshiba & a LaCie. The Toshiba is brand new, and the LaCie was being used for backup on my old SBS2003 server. Both disks are working fine - I have re-formatted & tested them on the new server& on a PC.

When I attempt to add either disk as a backup destination using the SBS Console, at the end of the process I get the error: "Configuring Server Backup Failed", and when I click View Error Details I get: "Cannot configure backup schedule" - the server cannot configure the backup schedule. Please try again. If try again etc etc. Checking the system event log I see 2 entries - both with source userpnp, one is event id 2003 & the next is 2001. Text is "drive management has concluded the process to add service volsnap instance id xxx  with the following status: 0, and "drive management has concluded the process to driver FileRepsoitory\volume.inf.... with the following status: 0x0

This didn't really surprise me - every SBS2011 server I've installed has had issues adding backup destinations (surely you can fix this MS). I then tried using WBAdmin to add the disks, and using either disk it gets to the point where it prepares the disk, then fails with "Incorrect Function". I get the same event log entries as above.

In either method, the disk is prepared. Any partition on the new disk is removed, and a partition is created without a drive letter allocated.

Please help - I can't take a backup off-site.


Viewing all articles
Browse latest Browse all 8539

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>