Configuring Groupwise 7 without NDS or reparing NDS
Peter Guhl
A customer of mine is running Groupwise 7 on Linux. Now we have set up a
copy (from an image) which should be shifted to another IP-adress and
serving as a backup system in case the first server fails (getting the
messagebase via dbcopy - that's enough for now).
The problem is that the first server has been configured using NDS and
the nds at the second server doesn't want to work. Whenever I want to
connect the local server, no matter if by consoleone, ndsconfig,
ndsbackup etc. I get errors -632. Only deleting the tree using ndsconfig
seems to have succeeded (I don't need *this* tree, I only need some tree
I can authenticate which is completely independent from the one the
first groupwise installation is running in). Now I see 2 possibilities:
A) Make nds work with a new, clean tree
B) Configure GroupWise independently from any NDS (if that's possible at
all)
I already tried A) and got the impression that I forgot to clean
something out (some files or configurations nds-uninstall does not
remove). I tried B) too, but I soon found out that I definitely lack
in-depth Groupwise-knowledge for such a task.
I managed to connect the NDS at server 1 and select the domain from
server 2, but that doesn't look like a good thing to me since I guess
that the IP-Address-Changes done here will be written back to the main
tree and might later be written down to the first GroupWise installation
breaking it.
Is there somebody around knowing more and willing to help?
Of course I know that there are failover and clustering mechanisms built
into NDS and GroupWise too but I have no idea how long it would take to
change the whole thing into such a setup. That would be another unknown
area to explore first - and that's where the money shortage comes in... ;-)
Kind Regards
Peter