Upgrade or migrate to RT4?

Hi,

I’ve been following along with user’s experience in moving to RT4. In order
to see if I wanted to upgrade my RT3.8.4 I’ve been using at my work place
for the last 2 years I installed a fresh virtual machine with a vanilla RT4
install. I like it and would like to use it for production.

I would prefer to import the data into RT4 than upgrade the existing 3.8.4.

I do nightly mysqldumps of the database and tar up the contents
of*/usr/local/share/request-tracker3.8
*, /usr/share/request-tracker3.8 and */etc/request-tracker3.8
My question is : "It possible to run the upgrade scripts on the database and
get the data in the new instance (RT4) without actually upgrading my 3.8.4?"
or do I have to run the upgrade process on my 3.8.4 instance?

Maybe I missed it - is there a step by step guide for doing this?

Thanks in advance.

Paul

Hi,

I’ve been following along with user’s experience in moving to RT4. In order to see if I wanted
to upgrade my RT3.8.4 I’ve been using at my work place for the last 2 years I installed a
fresh virtual machine with a vanilla RT4 install. I like it and would like to use it for
production.

I would prefer to import the data into RT4 than upgrade the existing 3.8.4.

I do nightly mysqldumps of the database and tar up the contents of
/usr/local/share/request-tracker3.8, /usr/share/request-tracker3.8 and /etc/request-tracker3.8
My question is : “It possible to run the upgrade scripts on the database and get the data in
the new instance (RT4) without actually upgrading my 3.8.4?” or do I have to run the upgrade
process on my 3.8.4 instance?

Maybe I missed it - is there a step by step guide for doing this?

Upgrading to RT4 means doing exactly what you want.
Import your mysqldump on the fresh VM (into either rt4 or rt3) install
RT4 and tell configure where to find your database.

RT ships with a lot of documentation about installing and upgrade.
You can find it in the README and docs/UPGRADING*

-kevin

Hi,

I’ve been following along with user’s experience in moving to RT4. In order to see if I wanted
to upgrade my RT3.8.4 I’ve been using at my work place for the last 2 years I installed a
fresh virtual machine with a vanilla RT4 install. I like it and would like to use it for
production.

I would prefer to import the data into RT4 than upgrade the existing 3.8.4.

I do nightly mysqldumps of the database and tar up the contents of
/usr/local/share/request-tracker3.8, /usr/share/request-tracker3.8 and /etc/request-tracker3.8
My question is : “It possible to run the upgrade scripts on the database and get the data in
the new instance (RT4) without actually upgrading my 3.8.4?” or do I have to run the upgrade
process on my 3.8.4 instance?

Maybe I missed it - is there a step by step guide for doing this?

Upgrading to RT4 means doing exactly what you want.
Import your mysqldump on the fresh VM (into either rt4 or rt3) install
RT4 and tell configure where to find your database.

RT ships with a lot of documentation about installing and upgrade.
You can find it in the README and docs/UPGRADING*

-kevin

  Kinda butting in, but that is exactly what I did when I went

from 3.6.7 to 3.8.7 in Ubuntu: create vm, install RT, take dump, read
dump, apply upgrades to the database (using the script provided in 3.8
to do that), adjust config as needed, and run it. I would expect 3.8
to 4 to be the same, but I will have to wait until ubuntu releases RT
4 as a package to do that. :wink:

I just migrated from RT 3.8.8 to 4.0.1 (debian-version/-repository) just with
dbdump and a fresh RT4-installation.

I copied the RT_SiteConf-file into my RT-folder and tried to run
"/usr/sbin/rt-setup-database" but it always failed to use MySQL, it was a real
nightmare because it always wanted to change some “SQLite3”-database.

I had to modify that nasty
"/etc/request-tracker4/RT_SiteConfig.d/51-dbconfig-common" file to use my
mysql-database, had cost me 2 days to figure out :frowning:

After modifying i run “update-rt-siteconfig-4” to write some stuff

In the end running “/usr/sbin/rt-setup-database --dba rt
–prompt-for-dba-password --action upgrade” worked for me FINALLY !!!

Too bad, that this is SO undocumented (until now).

I just migrated from RT 3.8.8 to 4.0.1 (debian-version/-repository) just with
dbdump and a fresh RT4-installation.

I copied the RT_SiteConf-file into my RT-folder and tried to run
"/usr/sbin/rt-setup-database" but it always failed to use MySQL, it was a real
nightmare because it always wanted to change some “SQLite3”-database.

I realize there probably aren’t docs for upgrading between the debian
packages, but the docs that the RT tarballs ship with explicitly tell
you not to just copy your RT_SiteConfig between 3.8 and 4.0 because it
creates a world of pain.

Thomas

oh, i forgot to tell that i DID modify my RT_SiteConfig to fit the new allowed
values (looked into the RT_Config for it).

i DO know that copying old-configs into new systems always makes the world into
a new hell, but that was what i’ve done: i made a copy, transfered it and wiped
out all “old” that was obsolete

I do nightly mysqldumps of the database and tar up the contents of
/usr/local/share/request-tracker3.8, /usr/share/request-tracker3.8 and /etc/request-tracker3.8
My question is : “It possible to run the upgrade scripts on the database and get the data in
the new instance (RT4) without actually upgrading my 3.8.4?” or do I have to run the upgrade
process on my 3.8.4 instance?

I believe you’re confusing upgrading the libraries and upgrading your
database. You can install RT 4.0.2 on a new server and import your
database and then run the database upgrade steps. Running the 3.8.4 data
under 4.0.2 will not work. You must review the database upgrade steps
documented in the README and in docs/UPGADING-3.8 and 4.0 and then
complete all of the steps relevant to your install.

-kevin

You can install RT 4.0.2 on a new server and import your
database and then run the database upgrade steps. Running the 3.8.4 data
under 4.0.2 will not work. You must review the database upgrade steps
documented in the README and in docs/UPGADING-3.8 and 4.0 and then
complete all of the steps relevant to your install.

We’re planning to do the same thing; I have 3.8.10 as my production system
and I have set up 4.0.2 as the new system. Right now 4.0.2 is set up and
running but I have not imported the 3.8.10 database.

From reading the various READMEs I have to run the upgrade script. My
question is how do I get the 3.8.10 database data into the rt4 database?

Do I just do the mysql dump thing:

mysql -u #username# -p rt4 < rt3.dump

and then run

/opt/rt4/sbin/rt-setup-database --prompt-for-dba-password --action upgrade

Thanks.

You can install RT 4.0.2 on a new server and import your
database and then run the database upgrade steps. Running the 3.8.4 data
under 4.0.2 will not work. You must review the database upgrade steps
documented in the README and in docs/UPGADING-3.8 and 4.0 and then
complete all of the steps relevant to your install.

We’re planning to do the same thing; I have 3.8.10 as my production system
and I have set up 4.0.2 as the new system. Right now 4.0.2 is set up and
running but I have not imported the 3.8.10 database.

From reading the various READMEs I have to run the upgrade script. My
question is how do I get the 3.8.10 database data into the rt4 database?

Do I just do the mysql dump thing:

mysql -u #username# -p rt4 < rt3.dump

and then run

/opt/rt4/sbin/rt-setup-database --prompt-for-dba-password --action upgrade

Yes, with one caveat. You need to ensure that any tables that do
exist in rt4 aren’t there after you import the rt3 database, so you
probably want to drop the rt4 database and create it empty before
importing (or figure out what tables to drop manually).

-kevin