Upgrade question

We have 2 rt systems currently (4.0.4 and 3.8.8). A few months ago I upgraded to 4.0.4 from 3.8.7 and with the information here and tutorials I found it was a very smooth transition. I now want to upgrade the other system and have a couple of questions.

We are a virtual shop so I am wondering if I simply clone our 4.0.4 system, change the name, IP, postfix mail settings and aliases, dump and load the database (to a new name) and upgrade the db to 4.0.4 will it work? Or do I need to recompile/reconfigure the software and change --with-db-database=newdbname?

If I need to reconfigure, is there a simple way of doing that without having to go through the entire installation?

Thanks in advance!

Joe

We are a virtual shop so I am wondering if I simply clone our 4.0.4
system, change the name, IP, postfix mail settings and aliases, dump
and load the database (to a new name) and upgrade the db to 4.0.4
will it work? Or do I need to recompile/reconfigure the software and
change --with-db-database=newdbname?

If I need to reconfigure, is there a simple way of doing that without
having to go through the entire installation?

You can clone the VM your RT 4.0.4 is running in, but you should also
reconfigure RT and run make upgrade again to install any changed files
(before make upgrade-database).

When RT installs, it writes into files a few things grabbed from your
./configure line. To reconfigure (without having to reinstall all the
deps) and make sure you don’t miss any changes, you’ll want to re-run
./configure on the cloned VM with your tweaked options
(–with-db-database for starters). You can find the previously used
./configure incant at the top of /opt/rt4/etc/RT_Config.pm.

You might also take the opportunity to upgrade to RT 4.0.5 at the same
time. :slight_smile:

Hello,

I currently have RT v4.0.7 installed on a Debian server (RT was
installed from Debian repositories). For various reasons, I need to
put RT onto a new server, and was going to stick with Debian, but
instead of using RT from the repositories, I am planning on doing a
source install (the repositories are not updated very often, and doing
a source install will be easier to keep RT updated, IMO)

I am wondering what the best way to go about this is. I am seeing two
ways to do this:

1.) Install RT v4.0.7 on the new server, then import current
configs and database. Once confirmed all is working properly, perform
upgrade to v4.0.17. Or

2.) Install RT v4.0.17 on new server. Import configs and database
from current 4.0.7 server. Jump to the database schema upgrade part
of the “upgrade” instructions

The second option would of course be easier and more efficient, as it
eliminates a step, and it seems to me that it should work, since it
seems the biggest part of upgrading RT seems to be the database schema
part; I just don;t know if there might be any “gotchas” doing it that
way.

What would be the best/recommended way to go?

Thanks! :slight_smile:

-Alan

source install (the repositories are not updated very often, and
doing a source install will be easier to keep RT updated, IMO)

4.0.17 was actually added to unstable and testing at the end of
August. The Debian packager for RT works quite hard.

2.) Install RT v4.0.17 on new server. Import configs and database
from current 4.0.7 server. Jump to the database schema upgrade part
of the “upgrade” instructions

This is what I would do. It’s a new server, so you even have plenty
of opportunity to do a test upgrade first.

-kevin

Quoting “Kevin Falcone” falcone@bestpractical.com:

4.0.17 was actually added to unstable and testing at the end of
August. The Debian packager for RT works quite hard.

Ah, I did not know that, though I only run “stable” in a production
environment.

2.) Install RT v4.0.17 on new server. Import configs and database
from current 4.0.7 server. Jump to the database schema upgrade part
of the “upgrade” instructions

This is what I would do.

OK, thanks for the confirmation that that is the way to go (don’t
worry, I won’t hold you accountable for anything that goes wrong! lol)

-Alan