IF you have any answers or thoughts on some of these issues feel free to
pass on your wisdom...

The admin manual for GW8 is not that clear on GW8 backups --
requirements and methodology.

Some Minor examples...

Error one -- see below. It appear that GW is not enabled for TSA's on
the latest OES.

Error two: If you do edit the smdr.conf file, the correct command to
unload and reload is as follows...

/etc/rc.d/smdrd restart

Somewhere they provide the wrong directory and use "refresh" instead of
"restart" see below...

Third -- See Page 421-422...
Restoring a post office

3 If you do not use GWTSA or TSAFSGW to restore the post office,
time-stamp the restored user databases so that old items are not
automatically purged during nightly maintenance

What time-stamp? Now? yesterday? the time of the crash? My retirement date?


From page 451 of the GW8 admin guide...

cd /opt/novell/sms/bin/

5 To verify that TSAFS is running with GroupWise functionality, use:
../smsconfig -t

(or /opt/novell/sms/bin/smsconfig -t )

Results should include:
The loaded TSAs are:
tsafs --EnableGW

Note that GW does NOT show despite the following note.... Ny systems are
all patched to the latest OES2 SP2


NOTE: On the latest version of Novell Open Enterprise Server, GroupWise
functionality is always enabled and you do not need to use the
--EnableGW switch.

6 To make GroupWise functionality the default, modify the SMS
configuration file:

6a Change to the directory where the SMS configuration file is located.
cd /etc/opt/novell/sms

6b In a text editor, open the smdrd.conf file.

6c Change the following line:
autoload: tsafs
autoload: tsafs --EnableGW

6d Save the file and exit.
7 Continue with Running TSAFSGW on Linux.

================================================== ========

I guess that iff you already know the system the directions are clear.
-- Like a Mac it's intuitive -- if you already know how to run the system.

btw -- "iff" is spelled correctly -- "if and only if" :-)

Perhaps what would be good to see is for Novell to bring in a new
administrator and hand them what we the customers would get, the
manuals, the software and say a brand new system on which the admin is
to install OES2 Linux, GW8 and told -- move the current system to the
new hardware.

It might be an informative exercise for the people that write the
software and the people that write the manuals -- not to mention the GW8
"system architects" who plan the entire system and the interactions of
the various modules.

I suspect the new admin would be as puzzled as most customers by the
vague and sometimes conflicting and occasionally wrong instructions.

Do what Microsoft does -- put the new "admin" in a glass cage and let
the developers and manual writers watch. Oh, and don't let the admin see
the newsgroups on the first pass -- deprive them of the information you
get here. That should make it _real_ entertaining.

Why this rant?

One of the things I would recommend is a a booklet on how to upgrade a
Linux OES2 system to new hardware. Where you set up a new system and
then just move the old data to the new system -- somehow. There seems to
be a myriad of options -- with no clarity on the best methodology.

Will R
PMC Consulting