)
Whether the amount of space restore points consume on your hard disk is
too much or not enough is up to you, but either way, it??™s easy enough to
change. At the Command Prompt, type:
vssadmin resize shadowstorage /for=C: /on=C: /maxsize=5GB
(Replace C: with the drive you want to adjust, and 5GB with the actual
amount of space you wish to allocate.) If you want to release the limit for
shadow copy storage, omit the maxsize parameter, like this:
vssadmin resize shadowstorage /for=C: /on=C:
Now, you may have noticed that you need to indicate the drive letter twice.
This permits a nifty little hack: it turns out you can allocate space on one
drive to hold the shadow data from another drive. For instance, type:
vssadmin add shadowstorage /for=C: /on=D:
to have the shadow data for drive C: stored on drive D:. (If C: is your primary
Windows drive, putting your shadow data on D: should improve performance.)
To rescind this order, delete the shadow storage ???association???
with this command:
vssadmin delete shadowstorage /for=C: /on=D:
You can also delete shadow copy data without changing the associations:
vssadmin delete shadows /for=C: /all
Or, if you have a lot of drives and you want to clear the shadow data for all
of them at once, use this WSH script (see Chapter 9):
Set oWMI=GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\
cimv2")
Set cVolumes = oWMI.ExecQuery("Select * From Win32_ShadowCopy")
For Each oVolume in cVolumes
326 | Chapter 6: Troubleshooting
oVolume.
Pages:
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464