SBS 2008 VSS Writers are missing preventing Exchange log file truncation after backup

Reference this previous post relating to the same issue:

http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Server/Q_28534613.html

While this worked initially the same thing has happened again, as in many of the VSS writers are now missing. We feel it is shadowProtect that is interfering with them but cannot find proof.

We would like to keep ShadowProtect installed in case a historical restore is required. The server is running v5.0.1.23057.

Now we have Exchange SP3 installed is there a way to get the writer's functional again once and for all?
Assist-NetopaAsked:
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.

noxchoGlobal Support CoordinatorCommented:
ShadowProtect hast its own VSS writer and if you install it on the server then it takes over the system writer.
Did this problem reoccur after you installed ShadowProtect?
Try to reinstall ShadowProtect completely and see if this brings the VSS Writer back. Also, see if the VSS Writer and VSS Shadow Copy Service are present in Services and started.
0
VB ITSSpecialist ConsultantCommented:
If you need ShadowProtect for historical purposes then deactivate the license, uninstall it from your Exchange box and then move it to another dedicated machine as it is obviously causing havoc with the VSS writers.

The ShadowProtect license is transferable as long as you deactivate it first. See here for more information: http://www.storagecraft.com/support/faq/question/how-do-i-move-my-shadowprotect%C2%AE-license-and-software-different-computer
0
Assist-NetopaAuthor Commented:
VB ITS, yes it may come to that. How about getting the VSS writers back again, re-install SP3 or would installing the latest Exchange Rollup do the same thing?
0
Assist-NetopaAuthor Commented:
No solution found, server was made redundant and therefore closing question
0

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
Assist-NetopaAuthor Commented:
No solution found, manually cleared logs until server was made redundant
0
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
SBS

From novice to tech pro — start learning today.