Re: Backup fails with volsnap error
- From: "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 16 Jul 2007 18:24:41 -0400
There's a fair number of hotfixes for VSS-related issues, but I'd have
thought you'd have them covered with SP2. There is one recent KB about 3rd
party backup software, but you're talking SBS backup, right?
When you say memory usage is through the roof, what specifically is using
that memory? How much RAM is on the server? Can you post back a list of
anything using over 100 mb of RAM along with how much it's using (just sort
the list in Task Manager by CPU and list anything over 100,000 K - there
should only be a few).
"Lance Kujala" <LanceKujala@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3EDAC295-BEA6-43EC-BD3C-869B4F869F7F@xxxxxxxxxxxxxxxx
running sbs 2003 sp2 with exchange sp2 + latest patches.
the backup is occasionally failing with a vss error.
looking in the event log, I see event id 21 error
"the flush and hold operations for volume C: was aborted because of low
available system memory."
this error shows up for all drives in the backup.
checked the KB's, nothing that applies to this situation.
will try defragmenting the hard drives (one is 5% the other 15%)
I have noticed that memory usage has gone through the roof over the last
few
months after applying the OS/Exchange/3party service packs.
Any ideas on how to deal with / work around this problem?
.
- Follow-Ups:
- Re: Backup fails with volsnap error
- From: Lance Kujala
- Re: Backup fails with volsnap error
- Prev by Date: Re: Gmail on POP3 Connector
- Next by Date: Re: Backup fails with volsnap error
- Previous by thread: Unable to manage SharePoint
- Next by thread: Re: Backup fails with volsnap error
- Index(es):
Relevant Pages
|
Loading