WCS Upgrade 4.2 to 5.2 - Upgrade Linux First?

serotonin888 · ‎03-13-2009

Hi All,

I just attempted to upgrade our WCS software from 4.2.62.0 to 5.2.130.0. During the upgrade it kindly informed me that 5.2.130.0 is not supported on Red Hat 4. Therefore it would seem that I need to upgrade to 5.

But which task should i compelte first?

The linux upgrade or WCS?

The error mentions that 5.2 is not officially supported on linux 4. So does that mean I should do the upgrade to WCS and then upgrade Linux?

(I am not linux expert)

Appreciate any help

Thanks

ericgarnel · ‎03-13-2009

It would be best

You also need to make sure that you have enough ram & free space as well

run /opt/WCS-4.2.62.0/Backup

copy the backup to another machine, cd, large flash drive,etc. for safe keeping

pop in the RHEL 5 CD or DVD, reboot

type linux upgradeany

ref:

http://www.redhat.com/docs/manuals/linux/RHL-9-Manual/install-guide/s1-upgrade-examine.html

Once the upgrade is complete, copy over the new WCS file, chmod a+x WCS-5.2.130.x.bin

then from the command line (in same dir as file) ./WCS-5.2.130.x.bin

(whatever the filename is) hit tab and it will complete it for you.

follow the prompts and once it is successfully installed run the following:

/opt/WCS-5.2.130.x./Restore

You will see it perform many migration steps.

It may fail on the first run, so be prepared to try again.

You can do it from the gui as well

It installs just fine on CentOS too

serotonin888 · ‎03-19-2009

Thanks Eric

Sounds like a good plan. I will let you know how it goes.

Thanks

Andy

serotonin888 · ‎04-29-2009

Just thought I'd post back what we did in the end.

1) Backed up DB and Licenses files

2) Set up new VM Instance running Red Hat 5.3

3) Shutdown old physical server (as the license is tied to the hostname we couldn't have both servers running at the same timeâ€¦ I think this is something to do with Linux.. )

4) Change the name on the new server. Disable the redhat firewall.

5) Run the install script

6) Restore the DB (just remember to use binary FTP and not ascii when transferring the backup file. Ascii mode corrupts the tar file backup and you get an error during restore of â€œinvalid distance codeâ€)

7) Restart services

The license files are included in the DB backup. If the you don not change the host name to match the original you will not be able to start the WCS services.

Thanks