Recommneded Upgrade from GW2014/SLES 11 to GW2018/SLES 12

I currently have a Groupwise 2014 R2 system on a SLES 11 SP4 virtual machine. I have Mobility on a separate SLES 11 SP4 virtual machine. I'm planning to upgrade to GW 2018 and SLES 12. What's the preferred way to do this?

1) Upgrade inside existing VM?

2) Build brand new SLES 12 VM and then copy over postoffice and domain data and build GW2018 from scratch?
Parents
  • 3) Build a new SLES12 VM, install the binaries, down the old box, detach the VMDK holding GW data from the old box, attach it to the new box, move the secondary IP over to the the new box (or add the / replace with the primary, whatever your agents currently listen on), create the / place copies of the config files, run the upgrade. (assuming we're talking of plain SLES as opposed to OES)

    Basically all approaches wil do it. With 2) you'll have a pretty short downtime (assuming the dbcopy way) and keep the old system intact. Handy if little purple monsters rush into the building. With 3) you'll have even less downtime, but you'll have to (i.e. you should) prepare another sort of fallback plan.
Reply
  • 3) Build a new SLES12 VM, install the binaries, down the old box, detach the VMDK holding GW data from the old box, attach it to the new box, move the secondary IP over to the the new box (or add the / replace with the primary, whatever your agents currently listen on), create the / place copies of the config files, run the upgrade. (assuming we're talking of plain SLES as opposed to OES)

    Basically all approaches wil do it. With 2) you'll have a pretty short downtime (assuming the dbcopy way) and keep the old system intact. Handy if little purple monsters rush into the building. With 3) you'll have even less downtime, but you'll have to (i.e. you should) prepare another sort of fallback plan.
Children
  • mathiasbraun wrote:

    > With 3) you'll have
    > even less downtime, but you'll have to (i.e. you should) prepare
    > another sort of fallback plan.


    It's always a good idea to keep your domain and post office on its own
    virtual disk. That way, you can assign a separate disk controller for
    slightly better performance. In some cases it cam be a higher
    performance disk controller than is used on the disk that hosts your
    OS. If necessary, you can even use higher performance storage to host
    the virtual disk. Perhaps all this is unnecessary but you would have
    the ability to do it.

    With your GroupWise data on its own virtual disk you can quickly down
    your system and clone the virtual disk to create a full backup much
    more quickly than copying files. It's always a good idea to have a
    couple of good backups before attempting anything out of the ordinary
    and that includes attaching a virtual disk to a new VM. By using a
    copy, your original system remains intact for a quick fallback should
    it become necessary.

    Attaching the virtual disk to the new VM is the quickest way to get the
    data there. If your existing system doesn't currently have your
    GroupWise files on its own virtual disk then I suggest shutting down
    the current server running GroupWise and attach its virtual disk to
    your new server in order to copy over the files. Copying files between
    two disks on the same server is considerably faster than copying them
    across the wire. It isn't necessary to use dbcopy in this situation.
    You can use whatever copy utility is available. And, of course, you'll
    want to copy them to their own virtual disk which you can then mount
    anywhere you need it.

    If you are using VMware, their official position is that they don't
    support upgrading the OS in a VM from one major release to another and
    suggest that you create a new VM to accomplish the upgrade. Upgrading
    from SLES11 to SLES12 is considered a major upgrade from VMware's
    perspective.

    --
    Kevin Boyle - Knowledge Partner
    If you find this post helpful and are logged into the web interface,
    please show your appreciation and click on the star below this post.
    Thank you.