I always have a small percentage of VSS problems (with thousands of
clients) but right now I am seeing a huge increase and I have not been able
to fix them with our script which can usually fix VSS issues without a
reboot and rebooting the servers does not fix it either.  I just email our
Microsoft rep to see if he knew anything about this.

On Fri, Sep 15, 2017 at 11:25 AM, Zoltan Forray <zforray AT vcu DOT edu> wrote:

> Same scenario here. Just worked with a user on their backups having
> constant errors that seem to be VSS related on their 2008 R2 SP1 servers.
> One of the IBM articles I found points you to Microsoft for hotpatches
> related to VSS problems.
>
>
> On Fri, Sep 15, 2017 at 10:57 AM, Tom Alverson <tom.alverson AT gmail DOT com>
> wrote:
>
> > Is anyone else seeing a large increase in VSS problems (maybe since patch
> > night) primarily on WIndows 2008 non R2 servers?  The VSS errors are not
> > fixed by our usual VSS fixer script or even rebooting.  Running VSSADMIN
> > list writers will show the system writer as always missing on these
> > servers, and this is causing the TSM backups to do a non VSS backup and
> log
> > it as a failure.
> >
>
>
>
> --
> *Zoltan Forray*
> Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
> Xymon Monitor Administrator
> VMware Administrator
> Virginia Commonwealth University
> UCC/Office of Technology Services
> www.ucc.vcu.edu
> zforray AT vcu DOT edu - 804-828-4807
> Don't be a phishing victim - VCU and other reputable organizations will
> never use email to request that you reply with your password, social
> security number or confidential personal information. For more details
> visit http://infosecurity.vcu.edu/phishing.html
>