Hello sf=,
1.
Not really, at configurable intervals, VSS takes a snapshot (aka Shadow Copy)
of the state of content stored on selected volume shares. VSS stores only
the changes for the shares, not the entire share content. For example, if
you make a small change to a 5GB file, VSS stores only information about
the change. The service stores as many as 64 versions of a share, depending
on disk space. When the service creates the 65th Shadow Copy (or if you've
used all the disk space allotted for Shadow Copies), the service deletes
the oldest snapshot to make space for the newest snapshot. For example, if
an application writes only changes to a file when the file is modified, that
application's changes will require far less Shadow Copy space than will an
application that rewrites the entire file.
2.
Use at least the default of 10%.
3.
The risk will be that you DON'T use backup's any more. VSS will NOT prevent
you from doing regular backups. And if the size is not big enough it won't
start.
4.
The server should at least allow you to logon locally so that you can work
on it.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
> Dear Meinolf,
> Many thanks again for your prompt help. It has been more than 5 times
> you help me.
> Anyway, There are several question still in my mind:
> 1. If I enable the shadow copy, 60 GB of data, will it make a copy of
> my 60 GB data to my disk for volume shadow copy service? ( so there
> will be 60 GB original data, and 60 GB shadow copy data ??)
> 2. If i allocate 10 GB for shadow copy, where the windows will save
> the rest of 50 GB data as i have 60 GB original data?
> 3. What is the risk of enabling this feature?
> 4. Can I still access the system incase the disk is totally full?
> Thanks in advance.
> I am so appreciated with your help.
> Best Regards
>