Upgrade from 5.3 to 5.5 on new hardware

Clovertech Forums Read Only Archives Cloverleaf Cloverleaf Upgrade from 5.3 to 5.5 on new hardware

  • Creator
    Topic
  • #49202
    Rick Martin
    Participant

      We are upgrading from 5.3 to 5.5.  We are also installing new servers.  I don’t want to install 5.5 on the old servers nor do I want to install 5.3 on the new servers.  What’s the best way to get my sites upgraded/promoted from the 5.3 server to the 5.5 server?

    Viewing 3 reply threads
    • Author
      Replies
      • #61085
        Robert Kersemakers
        Participant

          Hi Rick,

          We are upgrading from 5.2 to 5.5, where 5.5 is installed on a new cluster of (HP-UX) servers.

          I made a copy of the production-site on 5.2 by using the mktar, ftp’ed the .tar to the 5.5 server and extracted the site into a test-site on 5.5. I then changed all the inbound/outbound ports/files/directories so I had a working 5.5 testing-site.

          Worked like a charm. Just make sure you don’t copy the $HCISITEDIR/exec directory.

          Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

        • #61086
          Dirk Engels
          Participant

            Hi Rick,

            easiest way of doing this is to mount the old directory on the new server and use hcirootcopy.

            Best wishes from Germany,

            Dirk

          • #61087
            Rick Martin
            Participant

              I tried mapping the 5.3 drive and running hcirootcopy, but got an error.  I just tried it again and it worked fine; so go figure.

              When upgrading from 5.3 to 5.5 is it necessary to run hcixltconvert and hcitpsconvert?

            • #61088
              James Cobane
              Participant

                All,

                When we migrated from 5.3 on old hardware to 5.4.1 on new hardware we accomplished this by installing the new cloverleaf software (5.4.1) on the new hardware, then simply created a 5.3 root directory on the new hardware, tar’d up the configuration files from the 5.3 box, and laid them out on the new box in the 5.3 directory that was created.  You can then perform the normal ‘site promotion’ process to migrate the 5.3 configurations to the new version.  This approach allows the site promotion to handle some potential conversions that are done to the configuration files (i.e. via hcirootcopy, hcixltconvert, hcitclconvert, etc.).

                Hope this helps.

                Jim Cobane

                Henry Ford Health

            Viewing 3 reply threads
            • The forum ‘Cloverleaf’ is closed to new topics and replies.