Migrating RT3.8 database to RT4.2

RT Users
1

So first off, somehow never used a mailing list before so if I’m doing
this wrong many apologies :wink:

We’re currently running RT3.8.11 on Ubuntu and it’s functioning about as
best as we can expect.

I’m currently documenting/testing installing RT4.2 via aptitude on
Debian Jessie. We’re trying to avoid installing from source for several
reasons.

I’m getting to the point that I need to figure out how to handle
migrating the tickets/attachments from the RT3.8 instance to this new
RT4.2 instance.

I found this page:

And while the versions are off, seems simple enough.

My concern is that is all I’ve found so far, so don’t want to just
blindly assume that is the best way to approach this.

We’re not going to upgrade the existing RT3.8 instance, we want a new
fresh RT4.2 instance but with the existing tickets/attachments.

There is no import/export feature that I can use right?

Any comments/suggestions would be appreciated!

2

There is no import/export feature that I can use right?

https://www.bestpractical.com/docs/rt/4.2/backups.html

-m

3

Thanks, that looks like it could be an option too.

Digging through the docs more, I see that there are two utilities that
could be more useful:

rt-serializer
rt-importer

If I’m reading it correctly, I can use rt-serializer to export the
contents of the RT3.8 database and then take that and feed it into the
rt-importer on the RT4.2 instance.

But, it doesn’t look like they existed in RT3.8…So maybe not really an
option? I wonder if I could still point the RT4.2 rt-serializer to the
RT3.8 mysql database and still use it?On 02/08/2016 04:44 PM, Matt Zagrabelny wrote:

On Mon, Feb 8, 2016 at 3:35 PM, Lee Wiscovitch lwiscovitch@monetra.com wrote:

There is no import/export feature that I can use right?
Backups - RT 4.2.17 Documentation - Best Practical

-m

4

Hi Lee,

The typical upgrade path is to take a backup of your database (I think
that’s what Matt was pointing out), restore it on the new machine, then
follow the steps in 6b in the README:

https://bestpractical.com/docs/rt/4.2/README.html

(It’s good to read the whole README, but those are the key bits that are
different for upgrading an existing instance.)

The upgrade scripts will then upgrade your database to be compatible
with the new version of RT.

The serializer and importer tools are typically used in special cases
where a DB upgrade won’t work, like moving from one brand of DB to
another or doing other things like joining two RT’s together.

JimOn 2/10/16 10:48 AM, Lee Wiscovitch wrote:

Thanks, that looks like it could be an option too.

Digging through the docs more, I see that there are two utilities that
could be more useful:

rt-serializer
rt-importer

If I’m reading it correctly, I can use rt-serializer to export the
contents of the RT3.8 database and then take that and feed it into the
rt-importer on the RT4.2 instance.

But, it doesn’t look like they existed in RT3.8…So maybe not really
an option? I wonder if I could still point the RT4.2 rt-serializer to
the RT3.8 mysql database and still use it?

On 02/08/2016 04:44 PM, Matt Zagrabelny wrote:

On Mon, Feb 8, 2016 at 3:35 PM, Lee Wiscovitch lwiscovitch@monetra.com wrote:

There is no import/export feature that I can use right?
Backups - RT 4.2.17 Documentation - Best Practical

-m

RT 4.4 and RTIR Training Sessions
(http://bestpractical.com/services/training.html)

  • Hamburg Germany March 14 & 15, 2016