GroupWise upgrade, 18.4 to 24.x and move to new server VM. Does this sound OK?

So GW 2018.4 running on OES 2018.1 (Sles 12.3). Since the underlying server has been upgraded so many times, I would like to start with a fresh foundation. This kis a small system for a handful users.

The GW system is on a separate "disk" in the VM, so I thought I would do this:

1. Do alll the preliminary stuff., top-down rebuild, certificate checks etc.

2. Shut down agents and copy all GW files to an USB drive, copy or DBCopy

3. Shut down VM, back up the complete VM

4. Remove DS from the GW server

5. Clean up DS, removing all objects belonging to to the old server

6. Install a fresh 2024.x OES server with same name and IP

7. Attach the GW disk.

8. Install the GW agents

Have I missed anything? I remember when doing the 2018 upgrade that there was something quite inintuitive about installing the GW agents, but cannot remember what.

Parents Reply Children
  • Verified Answer

    +1   in reply to 

    Rsync does not care. Innocent

    Usually I copy more. /etc/opt/novell/groupwise, /var/log/novell/groupwise, /var/opt/novell/groupwise and the whole /optnovell/groupwise.

    Despite of copying /opt/novell/groupwise you have to install GW software. use "rpm -qa | grep group" to check which parts you have to install.


    Use "Verified Answers" if your problem/issue has been solved!

  • 0   in reply to 

    There is another trick that can be used if only GroupWise has been installed on the source OES and OES does not offer any other services.

    Stop GroupWise, than ndsconfig rm on Souce Server . Clean Source Server Objects in NDS. Install the new OES server same name, same ip as usual in the eDir with the necessary services  Install GroupWise, do not make any configuration. Copy the source NSS vmdk form Source Server into Target OES Server VMWare Dir.

    Integrate the copied VMDK in the target OES (Attention, this only works in the VCenter Client or in the VM Browser depending on the vmware version). Use NSSMU to search for NSS volumes and integrate them into the target machine. Adjust the rights for NSS GroupWise and configure / Upgrade  GroupWise.

    Just done at the weekend because a GroupWise and SLES SP5 --> SP6 update caused Java errors. It was just a plain SLES. By the way, I can advise you to go from OES to plain SLES, there is less stress

    George

    “You can't teach a person anything, you can only help them to discover it within themselves.” Galileo Galilei