volsnap question
Tech-Archive recommends: Fix windows errors by optimizing your registry
I am jetting the following message in my perfromance report. The
shadow copies of volume C: were deleted because the shadow copy
storage could not grow in time. Consider reducing the IO load on the
system or choose a shadow copy storage volume that is not being shadow
copied.
Can any one please explian how to fix this.
Kind regards
Tony
.
Relevant Pages
- Event ID 25 - Volume Snapshot Error
... I have deployed an HP NAS 2000s running Windows Storage Server 2003, ... The shadow copies of volume E: were deleted because the shadow copy storage ... Allocated Shadow Copy Storage space: ...
(microsoft.public.windows.file_system) - RE: KB913648 Volume Shadow Copy Service update
... You've already posted this idea about resizing the shadow storage due to ... VOLSNAP.SYS driver used to take and manage volume snapshots requires paged ... 65536 bytes of paged pool are allocated. ...
(microsoft.public.windows.file_system) - Re: Volume shadowing between FC Storage at different sites, and the allocation class
... I have done multiple tests on these disks across a multi-site cluster. ... I was able to shadow $1$DGA disks with Storageworks $2$DUA ... > I have just connected to some Fibrechannel based storage from my VMS ...
(comp.os.vms) - Re: Event ID 25 - Volume Snapshot Error
... recall at some stage I played with a Defrag tool which allowed me to create ... - Why does the Volume Shadow Copy run for so long? ... > storage could not grow in time. ... > Allocated Shadow Copy Storage space: ...
(microsoft.public.windows.file_system) - RE: VSS and Storage association in use and cant be deleted
... I do have shadow copies set on D and I'm fine with the current size that is ... D...I get the error "Failed to remove the storage area association for volume ... the shadow copies will be cleaned when disabling Volume Shadow ... > Windows Server 2003-based server cluster file share ...
(microsoft.public.windows.server.sbs) |
|
