Re: Backup fails with volsnap error
- From: Lance Kujala <LanceKujala@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 16 Jul 2007 15:44:02 -0700
Hi Dave;
Yes, using NtBackup via the SBS backup.
1GB RAM, PF Usage is 1.2GB.
earlier in the year PF usage was hovering around the 1GB range.
Main Tasks
- store.exe 314,344
- dbserver.exe 174,156 (not sure what is running this)
- SMEX_Master.exe 162.048 (TrendMicro AV)
- sqlservr.exe 144,912 (the standard sbs servers)
- OfcService.exe 140,500 (TrendMicro)
- svchost.exe 97,388 (?)
- services.exe 89,352
- sqlservr.exe 65,520 (second sbs sql server)
- NTRtScan.exe 61,904 (trendmicro)
Obviously the TrendMicro AV is also a memory hog.
What is strange is that when I just "run" the backup task from scheduled
tasks during the day with everyone logged in, there are no problems; but when
it is run at night, that is when the problems happen.
Lance Kujala
MSCE
"Dave Nickason [SBS MVP]" wrote:
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: Dave Nickason [SBS MVP]
- Re: Backup fails with volsnap error
- From: Eugene Tan
- Re: Backup fails with volsnap error
- References:
- Re: Backup fails with volsnap error
- From: Dave Nickason [SBS MVP]
- Re: Backup fails with volsnap error
- Prev by Date: Re: Backup fails with volsnap error
- Next by Date: Re: Exchange/Domain Question
- Previous by thread: Re: Backup fails with volsnap error
- Next by thread: Re: Backup fails with volsnap error
- Index(es):
Relevant Pages
|
Loading