VolSnap EventID: 21 The flush and hold operation for volume C: was

[Ulrich Schroeter]

Eventlog:

Source: VolSnap
Event ID: 21
Description:
The flush and hold operation for volume C: was aborted because of low
available system memory.

2 servers w2k3-sp2 us.english, both configured as DC
one with E2K3-sr2 installed.

Error message on E2K3 server while backup from plain
W2K3 server thru Veritas Backup Exec 9.1
Backup - ASHAEXC1
OFO: Initialization failure on: "\\ASHAEXC1\Shadow?Copy?Components".
Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
OFO: Snapshot error (0x8007000e): Ran out of memory


environment: w2k3-sp2 us.english

On Exchange Server:
volsnap.sys 153.600 bytes
filedate 03/25/2003, 14:00:00
fileversion 5.2.3790.3959

related kb 907875
3 Gb switch isn't set in boot.ini

before 2 weeks we have had a related problem
the problem disappeared after a server reboot
now it appears again.

any hints?

regards, uli

[John Toner [MVP]]

Sounds like a memory leak. I would suggest this hotfix:

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

Regards,
John

Visit my blog: http://msmvps.com/blogs/jtoner

"Ulrich Schroeter" <UlrichSchroeter@discussions.microsoft.com> wrote in
message news:4D53780C-89F1-4A61-BCBE-D08DDAB8456B@microsoft.com...
> Eventlog:
>
> Source: VolSnap
> Event ID: 21
> Description:
> The flush and hold operation for volume C: was aborted because of low
> available system memory.
>
> 2 servers w2k3-sp2 us.english, both configured as DC
> one with E2K3-sr2 installed.
>
> Error message on E2K3 server while backup from plain
> W2K3 server thru Veritas Backup Exec 9.1
> Backup - ASHAEXC1
> OFO: Initialization failure on: "\\ASHAEXC1\Shadow?Copy?Components".
> Advanced Open File Option used: Microsoft Volume Shadow Copy Service
(VSS).
> OFO: Snapshot error (0x8007000e): Ran out of memory
>
>
> environment: w2k3-sp2 us.english
>
> On Exchange Server:
> volsnap.sys 153.600 bytes
> filedate 03/25/2003, 14:00:00
> fileversion 5.2.3790.3959
>
> related kb 907875
> 3 Gb switch isn't set in boot.ini
>
> before 2 weeks we have had a related problem
> the problem disappeared after a server reboot
> now it appears again.
>
> any hints?
>
> regards, uli
>