Backups Failing - a ton of VSS errors

Good day,

I'm receiving an overwhelming amount of errors when attempting to perform a ShadowProtect Server backup.  I'm receiving event IDs:

12289    VSS
12293    VSS
12298    VSS
9604      MSExchangeIS
6            VSNAPVSS

I can get you the language on the errors if desired.  I've installed the following MS hotfixes already: om/kb/833167
http:/ / om/kb/940349
http:/ / om/kb/957778
http:/ / om/kb/969219
http:/ / om/kb/979457

I did a MOUNTVOL /R because I saw I should on a post somewhere.  This removed all unused volume mounts on the server.

Small Business Server 2003 SP2
RAID 5 drives
backing up to a 2TB external drive

At this time, I am unable to perform a full backup of the server and I'm getting a bit nervous.  This problem was taking place before I swapped one of the RAID5 hard drives that were failing.  It is still taking place.

I'd appreciate any and all help you can provide, everybody.

Thank you.

Steven Taylor
Sue TaylorProject ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Larry Struckmeyer MVPCommented:
Have you investigated the condition of and re registering of the VSS writers?  Here is one link on the subject

I recently had a problem backing up an Exchange server because BackupExec was using the NetApp VSS provider and not the MS VSS provider.  My point is that perhaps you need to be using the MS VSS provider for your particular backup.  Or, put in more general terms, perhaps there is confusion about which VSS provider your app should use.  

In order to see which VSS providers are running use:  "Vssadmin list providers"

Perhaps the last vss provider you added is causing the issue.  If that was NetApps, you can temporarily disable this with "Navssprv.exe -r service /u"

However, you do need that provider for certain functions such as expanding a drive (I believe).  Check with NetApp for more info, but I safely disabled it, ran an Exchange backup with BackupExec (which then defaulted to MS VSS) and fixed my problem.  

Sue TaylorProject ManagerAuthor Commented:
The problem was that Shadow Protect's VSS writer and Microsoft's were clashing.  Once SP was disabled, it worked just fine.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Sue TaylorProject ManagerAuthor Commented:
Oh, and Microsoft Business Critical Support did a ton of other things too...
Sue TaylorProject ManagerAuthor Commented:
I called Microsoft to fix it.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.