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

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?
0
Assist-Netopa
Asked:
Assist-Netopa
  • 3
1 Solution
 
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
 
Assist-NetopaAuthor Commented:
No solution found, manually cleared logs until server was made redundant
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

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