Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

question about GWcheck

14 views
Skip to first unread message

april

unread,
Mar 1, 2010, 2:32:33 PM3/1/10
to
We are running GroupWise 8.0.2. We only have 130 mailboxes and the total
size of post office is about a little more than 100 GB. What I do not
understand is our weekly gwcheck takes between almost 3 days to finish.
Is that right?
The settings for GWcheck are as follows:

Action: analyze/fix databases
structure
index check
contents
collect statistics
fix problems
update user diskspace totals

I also noticed there is another default weekly maintenance event
Action: audit report
What is audit report for?

Can someone advise?

Thanks a lot!

Edward van der Maas

unread,
Mar 1, 2010, 5:04:34 PM3/1/10
to
april wrote:

> We are running GroupWise 8.0.2. We only have 130 mailboxes and the
> total size of post office is about a little more than 100 GB. What I
> do not understand is our weekly gwcheck takes between almost 3 days
> to finish. Is that right? The settings for GWcheck are as follows:

Have you checked the webconsole of the POA and check the gwcheck
threads when your gwcheck job is running ? How many threads are
allocated to gwcheck ?

--
Cheers,
Edward

Mr. Beer

unread,
Mar 1, 2010, 2:35:49 PM3/1/10
to

You may want to try

http://forums.novell.com/novell-product-support-forums/groupwise/groupwise-8x/

Massimo Rosen

unread,
Mar 1, 2010, 6:08:27 PM3/1/10
to
Hi,

april wrote:
>
> We are running GroupWise 8.0.2.

I'm very sure you're not running that version, as it doesn't exist yet.

> We only have 130 mailboxes and the total
> size of post office is about a little more than 100 GB. What I do not
> understand is our weekly gwcheck takes between almost 3 days to finish.
> Is that right?
> The settings for GWcheck are as follows:
>
> Action: analyze/fix databases
> structure
> index check
> contents
> collect statistics
> fix problems
> update user diskspace totals

Well, first of all, you should not be doing this. You should not run a
structure and contents check in the same run, and you should not run an
uncalled contents check with fix enabled without reason.

Other than that, no it should not take 3 days. I just happen to run a
full contents check over a 300GB Po. Took about 6 hours.


> I also noticed there is another default weekly maintenance event
> Action: audit report
> What is audit report for?

To update the information you get when you highlight any part of the
sysetm in ConsoleOne and chose "information".

CU,
--
Massimo Rosen
Novell Product Support Forum Sysop
No emails please!
http://www.cfc-it.de

April

unread,
Mar 2, 2010, 3:29:01 PM3/2/10
to
April wrote:
> First of all, thank you very much for the response.
>
> Secondly, are you saying structure with index check and contents with
> collect statistics should run in separate schedule? If yes, fix problems
> should be scheduled with structure or contents schedule? Please advise!
>
> Thank you much!
First of all, thank you very much for the response.

We are running GropWise version 8.0.1.(typo error :-) )

Secondly, are you saying structure with index check and contents with
collect statistics should run in separate schedule? If yes, fix problems
should be scheduled with structure or contents schedule? Please advise!

Thank you much!

Edward van der Maas

unread,
Mar 2, 2010, 3:59:44 PM3/2/10
to
April wrote:


> We are running GropWise version 8.0.1.(typo error :-) )
>
> Secondly, are you saying structure with index check and contents with
> collect statistics should run in separate schedule? If yes, fix
> problems should be scheduled with structure or contents schedule?
> Please advise!

Run a structure check (+ fix problems) every day of the week.

Then in the weekend run a content check (+fix problems) on Friday night
(or whatever night of the weekend you prefer).

--
Cheers,
Edward

Edward van der Maas

unread,
Mar 2, 2010, 5:20:13 PM3/2/10
to
April wrote:


> I would appreciate it if you could explain what structure check is

Imagine a filing cabinet with lots of draws in it and each draw
contains folders. A structure check will check if each draw will open
so you can take folders out of the draws.

> for and what content check is for.

So all those folders in the draws contain records which are linked to
eachother. The content check will make sure that those records are
correctly linked to eachother. Before you can do a content check you
need to make sure the actual draws can still be opened obviously so
hence why you run a structure check every day and a content check once
a week.

> For the size of post_office around
> 100GB, how long it will normally take to do the above two tasks?

Really hard to tell as it depends on a lot of factors. Server hardware,
post office load etc.


--
Cheers,
Edward

Massimo Rosen

unread,
Mar 2, 2010, 6:17:33 PM3/2/10
to
Hi,

April wrote:
> First of all, thank you very much for the response.
>
> We are running GropWise version 8.0.1.(typo error :-) )
>
> Secondly, are you saying structure with index check and contents with
> collect statistics should run in separate schedule?

They should be run seperate, yes, but they should never be run
"scheduled" at all, at least not with "fix" enabled. These are repair
options, not maintenance.

Dave Parkes

unread,
Mar 5, 2010, 3:23:49 PM3/5/10
to
You don't need structure again on the second job

Cheers Dave


--
Dave Parkes [NSCS]
Occasionally resident at http://support-forums.novell.com/

0 new messages