Full maintenance/repair routines to be done before conversions and at least once a yearAlways make sure you have a current complete backup before doing this.
One particularly part to secure, you should at least periodically manually make a local copy of the PrimaryDomain\wpdomain.db when all the agents and management consoles are down. Making periodic copies of all the Domain\wpdomain.db and PostOffice\wphost.db files is also a good practice as those are files that are always locked while the agents are up, and are hardest for backup systems to get a copy of. DBcopy is your friend to learn, even if only to grab periodic copies of the *.db files, or for real protection a tool such as Reload can help make life a whole lot more protected and easy for administration.
Unless otherwise instructed: if there are error messages, stop and get them figured out. Call co-workers, your favorite integrator (hopefully that is me, or my friend Andreas ;), and/or Micro Focus (formerly Novell) if necessary.
Except where noted, the following steps work for all versions of GroupWise from 5.1 to current, Where GW 5.x steps being in NWAdmin32, GW 6 through 2012 being in ConsoleOne, and GW 2014+ being its own webconsole. The standalone GWCheck.exe can be used for much of the manual steps but is best used when the Post Office Agent is shut down to avoid conflicts when doing the deeper work and especially for the early versions.
Periodic maintenance (every 6 months or so) for the Data Synchronizer Mobility Pack / GroupWise Mobility Service of "vacuuming".
If you happen to have a really old system work with, do consider a consultant who has worked with the versions in question as there is no official support for these older versions (just like Microsoft doesn't support DOS or Windows95).
This content is mirrored at this handy little site: www.groupwise.org
|Last updated 2016-11-26||Copyright © 1996-2016 Andy Konecny||andyweb @ konecnyconsulting.ca|