Prev: rename Exchange server
Next: MSExchangeTransport Event ID 12014
From: Ed Crowley [MVP] on 28 Jan 2010 10:21
The it would make sense if you're running store maintenance all night long.

One-hour windows are generally not the best way to do this because you don't
allow enough time for maintenance to finish. You should change it so that
it starts after your backups finish, stop just before the start of business,
and consider letting it run all weekend. For example, Tue 0100-0500, Wed
0100-0500, Thu 0100-0500, Fri 0100-0500, Sat 0100-Mon 0500.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"Luke" <Luke(a)discussions.microsoft.com> wrote in message
news:BB325C52-E1B2-4887-A86D-22ECAA01ED4A(a)microsoft.com...
> Each store has a 1 hour window with the first being 1am, the second store
> 2am, etc.. This is for all 7 days of the week.
>
> This was setup by someone else though.. and although the stores are fairly
> small (not more then a few GB each) I am wondering if this is enough time
> to
> get all the work done.. I know exchange will pick up where it left off in
> the
> next window, but that doesn't seem ideal to me.
>
>
>
> "Ed Crowley [MVP]" wrote:
>
>> What is your store maintenance schedule?
>> --
>> Ed Crowley MVP
>> "There are seldom good technological solutions to behavioral problems."
>

From: Luke on 29 Jan 2010 00:02
That sounds like a good plan.. I'll give them all at least 4 - 5 hours per
night and all weekend as well.

I'll set this on Monday (dont want to break anything on Friday arvo) and see
what happens.

By the by, checking the CPU usage today and noticed it has gone back to
pretty much idle all the time, with a big spike every couple of hours. I
dunno..

Thanks very much your your response!!
From: Ed Crowley [MVP] on 29 Jan 2010 00:22
If you schedule multiple stores' maintenance concurrently, you may be warned
about it in the event log. If performance during that period isn't a
problem, don't worry about the warning.
--
Ed Crowley MVP
"There are seldom good technological solutions to behavioral problems."
..

"Luke" <Luke(a)discussions.microsoft.com> wrote in message
news:58A083EB-0537-4E22-84FA-E097CC02D8BF(a)microsoft.com...
> That sounds like a good plan.. I'll give them all at least 4 - 5 hours per
> night and all weekend as well.
>
> I'll set this on Monday (dont want to break anything on Friday arvo) and
> see
> what happens.
>
> By the by, checking the CPU usage today and noticed it has gone back to
> pretty much idle all the time, with a big spike every couple of hours. I
> dunno..
>
> Thanks very much your your response!!

From: Luke on 7 Feb 2010 17:20
Hi Ed,
I seperated out the maintenence and backups so that there are no overlaps,
but after a day the CPU started behaving how it did previously.

The problem was Kaspersky 6.0 for Exchange 2007. It runs updates every 2
hours, but after an update it scans the whole store again :S.. Every 2 hours
the store was being scanned for 1 hour.. not ideal.

I've changed the updates to once a day, outside of the maintenence and
backup windows but before things get busy, and now the CPU teeters around 5%
all day, with a big spike during the update/scan around 7am.

I will see how this travels during the week, but I think that with CPU, Disk
and memory utilization all being down, it should help performance a lot.

I really wasn't expecting the AV software to fully scan the stores after an
update, so that was a bit of a shock.

Thanks once again for your assistance and pointing out the AV as a suspect!!

Kind Regards,

Luke
From: Rich Matheisen [MVP] on 7 Feb 2010 17:31
On Sun, 7 Feb 2010 14:20:01 -0800, Luke
<Luke(a)discussions.microsoft.com> wrote:

>Hi Ed,
>I seperated out the maintenence and backups so that there are no overlaps,
>but after a day the CPU started behaving how it did previously.
>
>The problem was Kaspersky 6.0 for Exchange 2007. It runs updates every 2
>hours, but after an update it scans the whole store again :S.. Every 2 hours
>the store was being scanned for 1 hour.. not ideal.

Is there no option to scan just the messages that arrived, say, in the
last two days, and to do so at some time that's more convenient?

>I've changed the updates to once a day, outside of the maintenence and
>backup windows but before things get busy, and now the CPU teeters around 5%
>all day, with a big spike during the update/scan around 7am.

Updating AV signatures only once a day may not be the best thing to,
but scanning everything on every AV signature update probably isn't
either.

Doesn't that AV software have an option to rescan messages when
they're accessed? Or to rescan the entire store, say, once a week (or
once a month)?

You might want to have a look at MS Forefront for Exchange. Right now
it uses Kaspersky5, but it can also scan each message with several
other AV engines. What one engine might miss, another may catch.
---
Rich Matheisen
MCSE+I, Exchange MVP
First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: rename Exchange server
Next: MSExchangeTransport Event ID 12014