Default POA Maintenance Schedules

Hi,

I found that my POAs Default Schedules don't match what's described here:
https://www.novell.com/documentation/groupwise2014r2/gw2014_guide_admin/data
/adm_poa_config_maintenance.html

I don't have "Default Daily Maintenance Event" and "Default Weekly
Maintenance Event"; instead I have "Default POA Mailbox/Library Maintenance
Event", "Default Weekly Maintenance Event" (Audit Report only), "Mailbox
Statistik Event". I also get this when I create a new Post Office. For 3
Scheduled Events are only 2 actions: "Default Audit Report" and "Mailbox
Statistic". The latter does a Content Check, but there is no daily Structure
Check.

Where does this difference come from? Does it make sense to change this
according to the docu?

"Default POA Disk Check Event" also differs: Trigger action at: 100 MB, Stop
Mail processing at 0 MB.

Thanks,
Mirko

Tags:

  • Hi Mirko,

    I recommend you set up your scheduled maintenance to match the documentation. If yours differs from the documentation then sometime in the past the jobs were adjusted. This is typically seen on systems that have been upgraded over the years.

    Cheers,
  • Hi Laura,

    yes, the system has been upgraded since GW 7.

    What confuses me is that even when I create a new PO/POA, I get the same
    Default Schedules as for the existing POAs. Are there old templates
    somewhere in the system?

    And that creates the problem that I don't know the exact settings for the
    "new" Default Schedules - the documentation isn't detailed enough. Are there
    screenshots available somewhere?

    Thanks,
    Mirko


    >>>


    > Hi Mirko,
    >
    > I recommend you set up your scheduled maintenance to match the
    > documentation. If yours differs from the documentation then sometime in
    > the past the jobs were adjusted. This is typically seen on systems that
    > have been upgraded over the years.
    >
    > Cheers,


  • Hi Mirko,

    Go to the Scheduled Maintenance tab on one of your POAs - I for reasons of my own I do this on a POA in the primary domain, if one exists. Delete the current, incorrect, scheduled jobs. Create new ones according to the documentation. Then go to all the other POAs and just enable these jobs. You only need to create the scheduled jobs in one place and that makes them available to all other POAs in your system.

    Cheers,
  • In article <5A0EC33B.C296.0030.1@hs-offenburg.de>, Mirko Guldner wrote:
    > yes, the system has been upgraded since GW 7.

    Ah yes, the defaults have evolved some since then. Even more since they
    started in GW5, never mind the totally manual way in GW4 (though I still have
    those notes if anyone ever needed them)

    > What confuses me is that even when I create a new PO/POA, I get the same
    > Default Schedules as for the existing POAs. Are there old templates
    > somewhere in the system?

    They are created once in the Primary system, after that they are totally at
    the mercy of any admins working with them.

    > And that creates the problem that I don't know the exact settings for the
    > "new" Default Schedules - the documentation isn't detailed enough. Are there
    > screenshots available somewhere?

    I started just figuring out what they should be and possibly have influenced
    what those defaults are with my page I started in GW5 days and have been
    updating and tuning ever since, so you can use it as a guide.
    Http://www.konecnyad.ca/andyk/gwmnt5x.htm
    Otherwise one of us will have to create a new system and then document exactly
    what those settings are, not that I've always agreed on every detail of what I
    have seen, but then defaults are just a good safe starting point, so do think
    your way through them, especially on timing. I have one client who's PO is
    big enough I have to be careful of timing the weekly contents checks that are
    hitting 20 hours to run.


    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    http://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please show
    your appreciation by clicking on the star below. Thanks!


  • Many thanks Laura and Andy, that clarifies it a lot for me. I wasn't aware
    that these schedules and actions are defined once and then available for all
    POAs; I even spent some time recently to check if there are different
    settings...

    I'll try to adopt the recommendations from Andy's page. Timing makes that a
    bit complicated, I think I'll need to do some tests first, to see how long
    the different actions take. Currently I have one weekly action with
    structure and content check which takes quite some time:

    Overall processing time for the entire job: 42:57:03
    Accumulated task processing times spent on the job: 99:00:51


    Thanks,
    Mirko

    >>>

    > In article <5A0EC33B.C296.0030.1@hs‑offenburg.de>, Mirko Guldner wrote:


    >> yes, the system has been upgraded since GW 7.

    > Ah yes, the defaults have evolved some since then. Even more since they


    >
    > started in GW5, never mind the totally manual way in GW4 (though I still


    > have
    > those notes if anyone ever needed them)
    >
    >> What confuses me is that even when I create a new PO/POA, I get the same


    >> Default Schedules as for the existing POAs. Are there old templates
    >> somewhere in the system?

    > They are created once in the Primary system, after that they are
    > totally at
    > the mercy of any admins working with them.
    >
    >> And that creates the problem that I don't know the exact settings for

    > the
    >> "new" Default Schedules ‑ the documentation isn't detailed enough. Are


    > there
    >> screenshots available somewhere?

    > I started just figuring out what they should be and possibly have
    > influenced
    > what those defaults are with my page I started in GW5 days and have been


    >
    > updating and tuning ever since, so you can use it as a guide.
    > http://www.konecnyad.ca/andyk/gwmnt5x.htm
    > Otherwise one of us will have to create a new system and then document
    > exactly
    > what those settings are, not that I've always agreed on every detail of
    > what I
    > have seen, but then defaults are just a good safe starting point, so do
    > think
    > your way through them, especially on timing. I have one client who's PO


    > is
    > big enough I have to be careful of timing the weekly contents checks
    > that are
    > hitting 20 hours to run.
    >
    >
    > Andy of
    > http://KonecnyConsulting.ca in Toronto
    > Knowledge Partner
    > http://forums.novell.com/member.php/75037‑konecnya
    > If you find a post helpful and are logged in the Web interface, please
    > show
    > your appreciation by clicking on the star below. Thanks!

  • In article <5A159DD3.C296.0030.1@hs-offenburg.de>, Mirko Guldner wrote:
    > Currently I have one weekly action with
    > structure and content check which takes quite some time:

    I really hope that this is two separate jobs as they should be done
    separately. Structural check/fix can be done more frequently and should
    be on its own. Contents then can be the once a week (or even twice if
    there is time to see if given errors really clear)

    > Overall processing time for the entire job: 42:57:03
    > Accumulated task processing times spent on the job: 99:00:51


    Thats a long one, and all the more reason to make sure Structure and
    Contents be separate so that they don't trip over each other.
    At that long a contents check, it is worth evaluating options for
    more/faster resources and/or splitting the load in some fashion.

    The PO with the longest processing time I have among my clients takes
    about 20 hours for a Contents check with the nightly Structure checks
    taking about an hour, so I would expect your Structure only GWChecks to
    be in the 2 hour range.
    How Clean does your current job run? If there are there errors/problems
    that persist week after week, then addressing them as needed would help
    reduce the time the jobs take as well as proactively fix issues before
    users complain or are even aware of them.
    How much is the swap space used on that box? If more than half is used,
    I take that as a time for more RAM. More CPU cores can make a big
    difference on performance on such systems. Limiting how much is in the
    live system is one way to split the system. That one PO I mentioned
    only keeps 800 days of mail live, after that they have to get from the
    Retain archive.


    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    http://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!

  • Hi Mirko,

    With regards to your weekly content check... In your scheduled maintenance job for Contents do you have the "Attachment File Check" enabled? If so this adds significant time to the job. I leave this unticked and only use it when necessary. As Andy has said your Structure and Content checks must be two seperate jobs. I recommend a Structure check each night and then a Content check once a week. Don't forget about your Disk Check routine to prevent GroupWise trying to operate without disk space available, not to mention trigger warnings to you when this situation is approaching.

    Cheers,