3.4.2 to 4.x

RT Users
1

Before I waste a bunch of time, is there any chance this
is likely to work?

  1. Dump all RT 3.4.2 data from MySQL 4.1 (database ‘rt3’)
  2. Stand up new server with RT 4.x and modern MySQL
  3. Import old data
2

Before I waste a bunch of time, is there any chance this
is likely to work?

  1. Dump all RT 3.4.2 data from MySQL 4.1 (database ‘rt3’)
  2. Stand up new server with RT 4.x and modern MySQL
  3. Import old data

Not with just those steps, but yes, of course you can upgrade from 3.4.2
to 4.0.4. Carefully read and follow the instructions in the
UPGRADING.mysql, UPGRADING-3.4, UPGRADING-3.6, UPGRADING-3.8, and
UPGRADING-4.0 documentation.

You have a large upgrade ahead of you, but it’s well documented and
fairly straightforward.
Upgrading to RT 4 — Best Practical Solutions is a gentle
introduction, but it does not try to cover all of the individual steps
you’ll need to take, just the general process.

Thomas

3

I recently went through upgrading/migrating to a new server and setting up
an upgrade from a 3.4.5 to 4.0.2. Let me know if you want the steps that I
went through to get it working…

KevinOn Thu, Dec 22, 2011 at 4:55 PM, Thomas Sibley trs@bestpractical.comwrote:

On 12/22/2011 03:45 PM, Jeff Blaine wrote:

Before I waste a bunch of time, is there any chance this
is likely to work?

  1. Dump all RT 3.4.2 data from MySQL 4.1 (database ‘rt3’)
  2. Stand up new server with RT 4.x and modern MySQL
  3. Import old data

Not with just those steps, but yes, of course you can upgrade from 3.4.2
to 4.0.4. Carefully read and follow the instructions in the
UPGRADING.mysql, UPGRADING-3.4, UPGRADING-3.6, UPGRADING-3.8, and
UPGRADING-4.0 documentation.

You have a large upgrade ahead of you, but it’s well documented and
fairly straightforward.
Upgrading to RT 4 — Best Practical Solutions is a gentle
introduction, but it does not try to cover all of the individual steps
you’ll need to take, just the general process.

Thomas

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

  • Boston March 5 & 6, 2012
4

I’ve read and re-read docs/UPGRADING*.

Things are going quite smoothly so far, as this is a
pretty stock old install of 3.4.2 heading to 4.0.4
on a totally different box.

Question:

Importing the old MySQL ‘rt3’ database as ‘rt4’

How? Edit the dump file?

Thanks for any further help!On 12/22/2011 4:55 PM, Thomas Sibley wrote:

On 12/22/2011 03:45 PM, Jeff Blaine wrote:

Before I waste a bunch of time, is there any chance this
is likely to work?

  1. Dump all RT 3.4.2 data from MySQL 4.1 (database ‘rt3’)
  2. Stand up new server with RT 4.x and modern MySQL
  3. Import old data

Not with just those steps, but yes, of course you can upgrade from 3.4.2
to 4.0.4. Carefully read and follow the instructions in the
UPGRADING.mysql, UPGRADING-3.4, UPGRADING-3.6, UPGRADING-3.8, and
UPGRADING-4.0 documentation.

You have a large upgrade ahead of you, but it’s well documented and
fairly straightforward.
Upgrading to RT 4 — Best Practical Solutions is a gentle
introduction, but it does not try to cover all of the individual steps
you’ll need to take, just the general process.

Thomas

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

  • Boston March 5& 6, 2012
5

Just (within MySql):
create database rt4;
Then, from the command line, using the dump from your current mysql server,
mysql -u -p rt4 < <name_of_sql_dump.sql>From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Jeff Blaine
Sent: Friday, December 23, 2011 2:00 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] 3.4.2 to 4.x

I’ve read and re-read docs/UPGRADING*.

Things are going quite smoothly so far, as this is a pretty stock old install of 3.4.2 heading to 4.0.4 on a totally different box.

Question:

Importing the old MySQL ‘rt3’ database as ‘rt4’

How? Edit the dump file?

Thanks for any further help!

6

Just (within MySql):
create database rt4;
Then, from the command line, using the dump from your current mysql server,
mysql -u -p rt4< <name_of_sql_dump.sql>

Thanks. That will override the ‘CREATE DATABASE’ in
the rt3 dump file?

7

This is the way I upgraded from 3.8 → 4.0.x. I think you could pipe the dump without creating the database first, but is seems like I had an issue with MySQL throwing an error back at me saying database rt4 does not exist. So, to answer your question, yes. If you have a database already created and you pipe the dump using the mysql -u root -p rt4 < mysqldump.sql command, it will put your dump into the database named rt4. Then you can go about the database upgrade procedures you have read in the UPGRADE_READMEs.

Hope this helps.From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Jeff Blaine
Sent: Friday, December 23, 2011 2:42 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] 3.4.2 to 4.x

Just (within MySql):
create database rt4;
Then, from the command line, using the dump from your current mysql
server, mysql -u -p rt4< <name_of_sql_dump.sql>

Thanks. That will override the ‘CREATE DATABASE’ in the rt3 dump file?

-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Jeff
Blaine
Sent: Friday, December 23, 2011 2:00 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] 3.4.2 to 4.x

I’ve read and re-read docs/UPGRADING*.

Things are going quite smoothly so far, as this is a pretty stock old install of 3.4.2 heading to 4.0.4 on a totally different box.

Question:

Importing the old MySQL ‘rt3’ database as ‘rt4’

How? Edit the dump file?

Thanks for any further help!

Before I waste a bunch of time, is there any chance this is likely
to work?

  1. Dump all RT 3.4.2 data from MySQL 4.1 (database ‘rt3’) 2. Stand
    up new server with RT 4.x and modern MySQL 3. Import old data

Not with just those steps, but yes, of course you can upgrade from
3.4.2 to 4.0.4. Carefully read and follow the instructions in the
UPGRADING.mysql, UPGRADING-3.4, UPGRADING-3.6, UPGRADING-3.8, and
UPGRADING-4.0 documentation.

You have a large upgrade ahead of you, but it’s well documented and
fairly straightforward.
Upgrading to RT 4 — Best Practical Solutions is a
gentle introduction, but it does not try to cover all of the
individual steps you’ll need to take, just the general process.

Thomas

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

  • Boston March 5& 6, 2012

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

  • Boston March 5& 6, 2012

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

  • Boston March 5& 6, 2012

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

  • Boston March 5 & 6, 2012
8

Just (within MySql):
create database rt4;
Then, from the command line, using the dump from your current mysql
server,
mysql -u -p rt4< <name_of_sql_dump.sql>

Thanks. That will override the ‘CREATE DATABASE’ in
the rt3 dump file?

mysqldump --opt xxx > xxx.dump.sql

This command doesn’t add create database or other instructions to
select database. You specify database to restore dump into when you
run mysql xxx < xxx.dump.sql.

Note that you’re using RT 3.4 on mysql 4.1 and newer, then you should
use binary charset during dumping and don’t forget to upgrade mysql
schema. It’s special step described in the documentation.

-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Jeff Blaine
Sent: Friday, December 23, 2011 2:00 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] 3.4.2 to 4.x

I’ve read and re-read docs/UPGRADING*.

Things are going quite smoothly so far, as this is a pretty stock old
install of 3.4.2 heading to 4.0.4 on a totally different box.

Question:

Importing the old MySQL ‘rt3’ database as ‘rt4’

How? Edit the dump file?

Thanks for any further help!

Before I waste a bunch of time, is there any chance this is likely to
work?

  1. Dump all RT 3.4.2 data from MySQL 4.1 (database ‘rt3’) 2. Stand up
    new server with RT 4.x and modern MySQL 3. Import old data

Not with just those steps, but yes, of course you can upgrade from
3.4.2 to 4.0.4. Carefully read and follow the instructions in the
UPGRADING.mysql, UPGRADING-3.4, UPGRADING-3.6, UPGRADING-3.8, and
UPGRADING-4.0 documentation.

You have a large upgrade ahead of you, but it’s well documented and
fairly straightforward.
Upgrading to RT 4 — Best Practical Solutions is a
gentle introduction, but it does not try to cover all of the
individual steps you’ll need to take, just the general process.

Thomas

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

  • Boston March 5& 6, 2012

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

  • Boston March 5& 6, 2012

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

  • Boston March 5& 6, 2012

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

  • Boston March 5 & 6, 2012

Best regards, Ruslan.

9

The RT 3.4 to RT 4.0.4 upgrade went fine.

Now with our data in MySQL 5.1.x, instead of the old
MySQL 4.1, and our new instance not in production yet,
we want to migrate to PostgreSQL 8.4.9, largely in
order to get performant full-text searching without
doing something hackish with MySQL and Sphinx nonsense.

That task, however, is turning out to be a nightmare.
The gory details are at the link below, but the short
story is that PostgreSQL does not like some of the
bytes (mostly when trying to INSERT into Attachments).

Cleaning the dump file of all non-ASCII characters,
then trying the data load again, bought me nothing (!!??).

If anyone has any advice, please share!

10

Hi Jeff,

I did an upgrade from mysql to postgres a few month back and it went
very smoothly. I used the rt-mysql2pg script available at
http://wiki-archive.bestpractical.com/view/rt-mysql2pg to convert the
data which performed seamlessly.

I have a bunch of notes I can share which might be helpful, I ran into a
few issues performing the update because of AssetTracker. Ping me
off-list and I’ll share them.On 12/28/2011 09:30 AM, Jeff Blaine wrote:

The RT 3.4 to RT 4.0.4 upgrade went fine.

Now with our data in MySQL 5.1.x, instead of the old
MySQL 4.1, and our new instance not in production yet,
we want to migrate to PostgreSQL 8.4.9, largely in
order to get performant full-text searching without
doing something hackish with MySQL and Sphinx nonsense.

That task, however, is turning out to be a nightmare.
The gory details are at the link below, but the short
story is that PostgreSQL does not like some of the
bytes (mostly when trying to INSERT into Attachments).

Cleaning the dump file of all non-ASCII characters,
then trying the data load again, bought me nothing (!!??).

mysql - No NULLs, yet invalid byte sequence for encoding "UTF8": 0x00 - Database Administrators Stack Exchange

If anyone has any advice, please share!

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

  • Boston March 5 & 6, 2012

Darin Perusich
Email: Darin.Perusich@ctg.com
Office: 716-888-3690
The information transmitted is intended only for the person or entity to which
it is addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any action
in reliance upon, this information by persons or entities other than the
intended recipient is prohibited. If you are not the intended recipient of this
message, please contact the sender and delete this material from this computer.

11

Hi Jeff,

I did an upgrade from mysql to postgres a few month back and it went
very smoothly. I used the rt-mysql2pg script available at
http://wiki-archive.bestpractical.com/view/rt-mysql2pg to convert the
data which performed seamlessly.

Hi Darin,

Oh jeez. I wish I’d known about that earlier!

It’s working fine so far. Chugging along.

12

As you go down this path. I want to let you (and the list) know that we upgraded to 4.0.4 recently and Monday I set up the indexing. The initial index took hours and increased the size of the database in postgres considerably (which was fine as it’s not too large). Yesterday we restarted the service and tested it and I have to say, it was incredible how fast content fulltext searching is. We have about 28000 tickets in our system and some obscure searches yielded results in seconds where before (on 3.8.7) would take a long time and make the system non-responsive in some cases.

An awesome addition to RT!!!

Only facet was in the update script I had to add the rt libs path to the script as we have a nonstandard installation path. The updates (hourly) take only seconds.

Just wanted to add my 2 cents.From: Jeff Blaine jblaine@kickflop.net
Sender: rt-users-bounces@lists.bestpractical.com
Date: Wed, 28 Dec 2011 12:27:47
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] 3.4.2 to 4.x

Hi Jeff,

I did an upgrade from mysql to postgres a few month back and it went
very smoothly. I used the rt-mysql2pg script available at
http://wiki-archive.bestpractical.com/view/rt-mysql2pg to convert the
data which performed seamlessly.

Hi Darin,

Oh jeez. I wish I’d known about that earlier!

It’s working fine so far. Chugging along.

I have a bunch of notes I can share which might be helpful, I ran into a
few issues performing the update because of AssetTracker. Ping me
off-list and I’ll share them.

The RT 3.4 to RT 4.0.4 upgrade went fine.

Now with our data in MySQL 5.1.x, instead of the old
MySQL 4.1, and our new instance not in production yet,
we want to migrate to PostgreSQL 8.4.9, largely in
order to get performant full-text searching without
doing something hackish with MySQL and Sphinx nonsense.

That task, however, is turning out to be a nightmare.
The gory details are at the link below, but the short
story is that PostgreSQL does not like some of the
bytes (mostly when trying to INSERT into Attachments).

Cleaning the dump file of all non-ASCII characters,
then trying the data load again, bought me nothing (!!??).

mysql - No NULLs, yet invalid byte sequence for encoding "UTF8": 0x00 - Database Administrators Stack Exchange

If anyone has any advice, please share!

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

  • Boston March 5& 6, 2012

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

  • Boston March 5 & 6, 2012
13

I have a bunch of notes I can share which might be helpful, I ran into a
few issues performing the update because of AssetTracker. Ping me
off-list and I’ll share them.

Darin,

I’d be interested in seeing any notes you would be willing to share
regarding the issues you faced with upgrading to Postgres because of AT.
I’m getting ready to upgrade to RT 4.0.4 and would like to take the
opportunity to migrate to Postgres.

Thanks,
Dustin