• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1216
  • Last Modified:

Windows Server Backup fails with shared protection point timeout errors

We have a server with consistently failing WBS backups. The errors given on the backup read: The backup of the volume was stopped before the backup started running. There appears to be an error with the volume shadow copy service on this server.

Trying to disable or change the settings of shadow copies on the C: drive result in the error "Failed to delete shadow copies of volume C:\. Error 0x800706ba: the RPC server is unavailable" if disabling and "failed to initialize the Settings dialog for volume C:\." (with the same error code) if trying to change settings. From what I can tell everything appears fine with the RPC service, but the volume shadow copy service doesn't really respond to any start or stop commands.

The server has been rebooted several times since the issue started with no change. I've also run the batch file to re-register all the various VSS components.
0
aspwv
Asked:
aspwv
  • 2
1 Solution
 
rhinocerosCommented:
Windows 2003 ?

RPC 0x800706ba and 0x800706bf errors occur when backup software tries to create VSS shadow copies on a computer that is running Windows Server 2003 SP2
http://support.microsoft.com/kb/969219
0
 
aspwvAuthor Commented:
This server is Windows Small Business Server 2008 x64 Service Pack 2, so I don't believe that would apply in this case.
0
 
rhinocerosCommented:
Why I said that? Because I cannot find your error code in "Windows Server Backup Error List"

Diagnosing Failures in Windows Server Backup
http://blogs.technet.com/b/filecab/archive/2009/09/16/diagnosing-failures-in-windows-server-backup-part-1-vss-spp-errors.aspx
0

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now