volume shadow copy

Why is the service turned on by default?
thanks

To protect your files, so you can revert to a previous version of a file that probably became corrupt. In build 5231, I had a photo I loved so much that was accidently corrupted after I tried to convert it to PNG, I simply converted it by going to the properties of the file, volume shadow tab. This feature was previously only available in Windows Server 2003. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"David Sherman" wrote in message

Why is the service turned on by default?
thanks

Andre Da Costa [Extended64] wrote:

To protect your files, so you can revert to a previous version of a file that probably became corrupt. In build 5231, I had a photo I loved so much that was accidently corrupted after I tried to convert it to PNG, I simply converted it by going to the properties of the file, volume shadow tab. This feature was previously only available in Windows Server 2003. --

Well as you probably remember, the service doesn't start by default in Windows 2003, it is left in the manual state and is only called when it is actually being used.
So either there is an issue here or VSS works slightly differently in Longhorn, so its a fair question either way.

How does it work with Server 2003 and SB2003?
I wonder also how this reactes with Diskkeeper 9 when doing a defrag. When I lasted checked it, 3rd party defrag tools would not work the Volume Shadow Copy turned on a Server.
On Tue, 25 Apr 2006 22:16:26 +0100, "Robert Moir" wrote:

Andre Da Costa [Extended64] wrote: To protect your files, so you can revert to a previous version of a file that probably became corrupt. In build 5231, I had a photo I loved so much that was accidently corrupted after I tried to convert it to PNG, I simply converted it by going to the properties of the file, volume shadow tab. This feature was previously only available in Windows Server 2003. --
Well as you probably remember, the service doesn't start by default in Windows 2003, it is left in the manual state and is only called when it is actually being used.
So either there is an issue here or VSS works slightly differently in Longhorn, so its a fair question either way.

In a Server environment its different, you would enable it on a back up Server or SAN, so it would configured to automatically create previous versions of all client user files files in the domain. Although this would be determined by a qouta and what file types can be backed up. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta
"David Sherman" wrote in message

How does it work with Server 2003 and SB2003?
I wonder also how this reactes with Diskkeeper 9 when doing a defrag. When I lasted checked it, 3rd party defrag tools would not work the Volume Shadow Copy turned on a Server.
On Tue, 25 Apr 2006 22:16:26 +0100, "Robert Moir" robspamtrap+msnews@gmail.com> wrote:
Andre Da Costa [Extended64] wrote: To protect your files, so you can revert to a previous version of a file that probably became corrupt. In build 5231, I had a photo I loved so much that was accidently corrupted after I tried to convert it to PNG, I simply converted it by going to the properties of the file, volume shadow tab. This feature was previously only available in Windows Server 2003. --
Well as you probably remember, the service doesn't start by default in Windows 2003, it is left in the manual state and is only called when it is actually being used.
So either there is an issue here or VSS works slightly differently in Longhorn, so its a fair question either way.

Andre Da Costa [Extended64] wrote:

In a Server environment its different, you would enable it on a back up Server or SAN, so it would configured to automatically create previous versions of all client user files files in the domain. Although this would be determined by a qouta and what file types can be backed up. --

Andre, as far as I know, Volume Shadow copies run locally to the server. You would have a server with two volumes (ideally different spindles), place your shares on one volume and use the other for the shadow copies.
As far as I know, you can't do this over multiple servers, e.g. you seem to be proposing that Windows 2003 lets you pick a "Volume Shadow Copies Server" for your whole domain which shadows every share you choose on any server on the network... and I don't think it works that way.
-- -- Rob Moir, Microsoft MVP Blog Site - http://www.robertmoir.com Virtual PC 2004 FAQ - http://www.robertmoir.co.uk/win/VirtualPC2004FAQ.html I'm always surprised at "professionals" who STILL have to be asked "Have you checked (event viewer / syslog)".

David Sherman wrote:

How does it work with Server 2003 and SB2003?

General info about VSS here: http://www.robertmoir.co.uk/win/ShadowCopiesFAQ.html
The machine takes a 'snapshot' of the various volumes at a time chose by the admin, and copies the difference in the files to the shadow.
For backup programs that can use the VSS service, these take a snapshot of the object(s) being copied in the same way, and write the shadow copy out to the backup media.

I wonder also how this reactes with Diskkeeper 9 when doing a defrag. When I lasted checked it, 3rd party defrag tools would not work the Volume Shadow Copy turned on a Server.

The defrag tools were protecting you http://support.microsoft.com/default.aspx?scid=kb;en-us;312067
(*sigh* I should add this to my VSS FAQ sometime...)
-- -- Rob Moir, Microsoft MVP Blog Site - http://www.robertmoir.com Virtual PC 2004 FAQ - http://www.robertmoir.co.uk/win/VirtualPC2004FAQ.html I'm always surprised at "professionals" who STILL have to be asked "Have you checked (event viewer / syslog)".