Re: zmdbintegrityreport

[Keith Fong <keith@sfu.ca>]

We disable the zmdbintegrityreport in production, and run it against our staging environment about once a semester.  Our staging environment is a snapshot copy of our production environment, so this allows us to perform the report without impacting performance in production.


On Sep-13-10, at 9:21 AM, Amos wrote:

> Hmm... overlooked this previously.
> 
> http://www.zimbra.com/docs/os/latest/administration_guide/C_CronTab%20Jobs.14.3.html#1059012
> 
> So what have some of the larger sites on here done?
> 
> 
> On Mon, Sep 13, 2010 at 10:24 AM, Amos <a.goo0h@gmail.com> wrote:
>> When are folks running zmdbintegrityreport?  I realize it's important
>> to run, but gosh, server becomes pretty much unusable when it's
>> running.  Looking at
>> http://wiki.zimbra.com/wiki/Performance_Tuning_Guidelines_for_Large_Deployments#MySQL
>> I notice our my.cnf is already at those levels, so hesitant to raise
>> anything much further.  Not sure how much that would help with
>> zmdbintegrityreport anyway.
>> 
>> By default zmdbintegrityreport runs Sunday nights, but that tends to
>> be a peak time for us.  So I tried Saturday night, and now a professor
>> complained.  I hate to run it while zmbackups are running, but may
>> have to.  Maybe just during an incremental the contention won't be so
>> bad.
>> 
>> Yeah, we need to split things out onto more servers, but doing so
>> rather gradually.  This is on a Sun B8000 blade with quad, quad core
>> AMD chips.  Probably could use some more memory.
>> 
>> Memory:      Total        Used        Free      Shared     Buffers
>> Mem:      32942652    32718860      223792           0     1244704
>> Swap:      8393848       36180     8357668
>>