WCS Upgrade 4.2 > 5.2 on Linux - Hints & Tips

Unanswered Question
Feb 16th, 2009

Hi There,

Has anyone had any experience upgrading WCS from 4.2 to 5.2 on Linux?

I'm interested to learn from anyone who has completed the upgrade. Any issues encountered? Testing plans? Backuot plans? etc etc.

Many Thanks

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
ericgarnel Mon, 02/16/2009 - 08:47

You should run a backup 1st. then the upgrade process should be fairly straight forward.

I go as far as to scp the backup to our san as well.

Keep your license keys handy too.

serotonin888 Wed, 04/29/2009 - 23:42

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.


Pushkar Sambhoos Wed, 05/06/2009 - 21:28

There are no known issues for upgrading form WCS 4.2.x.x to WCS 5.2.x.x on either Windows or Linux. As suggested, it's always a good idea to backup your database before proceeding with the upgrade.



Cisco TAC


This Discussion



Trending Topics - Security & Network