Anonymous_User Absent Member.
Absent Member.
1256 views

Some Backup issues -- documentation etc.

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
to:
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
Labels (2)
0 Likes
1 Reply
Anonymous_User Absent Member.
Absent Member.

Re: Some Backup issues -- documentation etc.

WillR wrote:

I remembered the location of the bad information about the smdrd
"refresh" -- see below --

It is the smdrd.conf file...

It says...
# smdrd a HUP signal with "/etc/novell-smdrd refresh"


>
> 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...


*********** BAD INFO FOLLOWS ****


# NOTE: This file is also auto updated when using other management
interfaces.

# Lines starting with the pound symbol '#' are treated as comments and
# ignored. Blank lines are also ignored.
# Other lines are considered as configuration options.

# Each configuration option has the following format:
# Option: Value
# or,
# Option=Value
# Options and Value are case insensitive, where applicable.
# There should be no space between Option and the colon ':' or equal '='
symbol.
# When using the equal '=' symbol, there should be no space between the
symbol
# and the value. Any Option that does not have a name value pair
representation
# follows its own format as detailed in the man page of sms.conf.

# If you make changes to this file, either reboot your machine or send the
# smdrd a HUP signal with "/etc/novell-smdrd refresh" or, do a "ps x" as
# root and look up the pid of smdrd. Then do a "kill -HUP <pid of smdrd>".
# smdrd will read this file whenever it gets that signal.


--
Will R
PMC Consulting
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.