5.3 to 5.7 Rev 2 upgrade on new server (linux)

Michael,

That is a pretty big leap.

I would check with support to see if you need to ‘walk through’ any intervening releases to set configuration files to some intermediate level.

We are in the process of testing 5.7rev2 and are coming from 5.5.

When copying a site from 5.5 to 5.7:

* we were told to open and then save again every single HL7-variant, because 5.7 adds something to the file.

* run ‘mktclindex’ in …/tclprocs to index all procs.

* there seems to be an issue with ‘fileset-local’, so I think you need to remove all the ‘fileset-‘ files in all the process-directories.

* be aware of symbolic links/shortcuts that point to your old cloverleaf installation. You will need to change these.

We are still testing all the interfaces, but so far so good. I hope you have tested the migration that you described.

The techniue I used on my most recent upgrade was to go from a Cloverleaf 5.2 server (AIX 5.2) to a Cloverleaf 5.6 server (AIX 5.3), which went as well as I could imagine, considering the magnitude of the upgrade (hundreds of sites and over a thousand interfaces).

Here is a high level description of my steps:

– wipe server LPAR clean and do scratch install of everything (OS, HACMP, SNA, Cloverleaf 5.6, make advancements like ether channel)

– do vulnerability scans and comply with any security department findings

– do scratch install of Cloverlead 5.6 and create mda_upgrade site as default site

– NFS mount READ ONLY /sites filesystem from the Cloverleaf 5.2 server onto the Cloverleaf 5.6 server and make it look like it is where Cloverleaf expects the old sites to be via a symbolic link

– use hcirootcopy on the Cloverleaf 5.6 server to upgrade each old 5.2 site and activate them granually to control the size of my potentail problems

– use our downtime model to turn on and test all the modules in the site I upgrade

– make the site ready for golive with alomost 100% confidence and know I can back out quickly with 100% confidence; so I’m not faced with a no point of return situation

– when ready to golive and switch over stop Cloverleaf 5.2 inbound interfaces let outbound interfaces empty out then shutdwon 5.2 site and turn on interfaces on new Cloverleaf 5.6 server

The average downtime of each site golive switch over from Cloverleaf 5.2 server to Cloverleaf 5.6 server ran about 2 mintues most of the time and out of some 1,200 interfaces I was able to do the entire upgrade without virtually a single significant issue that wasn’t detected and remediated during the mock golive testing using our downtime model.