Anyone testing Microsoft Volume Shadow Copy?

[James Pratt]

>> -----Original Message-----
>> From: C. Bensend [mailto:benny at bennyvision.com]
>> Sent: Monday, December 14, 2009 2:17 PM
>> To: nagios-users at lists.sourceforge.net
>> Subject: [Nagios-users] Anyone testing Microsoft Volume Shadow Copy?
>> 
>> 
>> Hey folks,
>> 
>>    I am hitting a situation where certain Windows 2003 Server file
>> servers will stop doing shadow copies on their share volumes.  The
>> service itself starts up and shuts down periodically like it
>> should, but a new shadow copy is *not* created as viewed in Pervious
>> Versions from a Windows box.
>> 
>>    Looking at the vssadmin.exe command on the Windows server, I see
>> I can:
>> 
>> 
>> vssadmin List Shadows
>> 
>> 
>>    And it prints out a listing of the existing shadow copies.
>> However, without awk and grep (and no, I cannot install cygwin or
>> anything like that), I don't have a clue how to process it.
>> 
>>    Is anyone already testing Volume Shadow Copy?  Does anyone know
>> of performance counters or anything I can use via the Nagios EventLog
>> agent or NSClient++ to check to see that new shadow copies are being
>> created?
>> 
>>    I'm running out of Google on this one...
>> 
>> Thanks!
>> 
>> Benny
>> 
>> 
>> --
>> "It's not all about getting up and putting four slices of kickass
>> in a two slice toaster."         -- ark86, on Fazed.net


Hi, this may help, but I cannot tell for sure in your particular case.
I've installed it on a few servers here to resolve win2k3 VSS-related
backup errors/issues.

http://support.microsoft.com/kb/940349


cheers,
James

------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null