Recommendation for upgrade and move

RT Users
1

We are upgrading our RT3.0.7_01 instance to RT3.2 shortly. We are also
moving to a fresh new server, from Solaros to RHEL, and newer version of
MySQL. I wanted to check with the list on recommended approach.

I planned on doing a fresh install on the new server - MySQL, RT,
everything. Then mysqldump the existing RT db on the old server and restore
to the new one.

I am hoping that I don’t have to upgrade the old RT first? Any other
considerations?

Thanks.

Joe Micciche

2

3.2.0 has a slightly different db schema. So probably you
are ok, if you run the upgrade scripts after restoring mysql.
See REAME and UPGRADING files in the 3.2.0 distribution.

bobg

3

Date: Fri, 2 Jul 2004 15:20:39 -0400
From: Joseph_Micciche@Progressive.com
Subject: [rt-users] Recommendation for upgrade and move
To: rt-users@lists.bestpractical.com
Message-ID: OFA7C7F93B.CD6CF696-ON85256EC5.0069D2D0@progressive.com

We are upgrading our RT3.0.7_01 instance to RT3.2 shortly. We are also
moving to a fresh new server, from Solaros to RHEL, and newer
version of
MySQL. I wanted to check with the list on recommended approach.

I planned on doing a fresh install on the new server - MySQL, RT,
everything. Then mysqldump the existing RT db on the old
server and restore
to the new one.

I am hoping that I don’t have to upgrade the old RT first? Any other
considerations?

I did a very similar thing myself, except that I treated the database
move separately to the to the RT system move.
I installed MySQL on my new box, did a mysqldump of the data, imported
it and got the old RT system pointing at the new database server. Once
this was all OK, I then looked at moving RT.
In this way, when you install RT, you can apply the upgrade scripts when
you’ve done the install to modify the db schema.

Cheers
Carl

   Carl Vincent              http://www.netskills.ac.uk/ (URL)
   Systems, Software, Webmaster           0191 222 5003 (voice)
   NETSKILLS - Quality Internet Training  0191 222 5001  (fax)