Hey guys,
We finally have time and money to upgrade our RT system. We are moving
from an old machine running RT 2.0.13 on Postgres on RH71 to a new
machine running RHEL 4 and RT 3.4.1, and perhaps using mysql instead of
postgresql if possible.
Any advice on the best way to perform this upgrade? I’ve heard
references to a rt2-to-rt3 conversion tool, but I don’t see that in the
Contribution section anymore. Keeping our old tickets is essential.
–Andy
Hey guys,
We finally have time and money to upgrade our RT system. We are moving
from an old machine running RT 2.0.13 on Postgres on RH71 to a new
machine running RHEL 4 and RT 3.4.1, and perhaps using mysql instead of
postgresql if possible.Any advice on the best way to perform this upgrade? I’ve heard
references to a rt2-to-rt3 conversion tool, but I don’t see that in the
Contribution section anymore. Keeping our old tickets is essential.
Index of /pub/rt/devel
–Andy
Be sure to check out the RT Wiki at http://wiki.bestpractical.com
Best regards, Ruslan.
We finally have time and money to upgrade our RT system. We are moving
from an old machine running RT 2.0.13 on Postgres on RH71 to a new
machine running RHEL 4 and RT 3.4.1, and perhaps using mysql instead of
postgresql if possible.Any advice on the best way to perform this upgrade? I’ve heard
references to a rt2-to-rt3 conversion tool, but I don’t see that in the
Contribution section anymore. Keeping our old tickets is essential.
Based on some earlier messages on this list I got the impression
that you have to install RT 3.2.3 to import the files dumped
by the rt2-to-rt3 tool, then upgrade that to 3.4.x applying
the database updates as described in the README to get to
the current schema.
There is a script in:
http://download.bestpractical.com/pub/rt/contrib/3.0/Conversion/
to convert from pg to mysql, but I’m not sure exactly when
you should use it. After pulling into 3.2.3 on pg might be
the best match.
Les Mikesell
les@futuresource.com
We finally have time and money to upgrade our RT system. We are moving
from an old machine running RT 2.0.13 on Postgres on RH71 to a new
machine running RHEL 4 and RT 3.4.1, and perhaps using mysql instead of
postgresql if possible.Any advice on the best way to perform this upgrade? I’ve heard
references to a rt2-to-rt3 conversion tool, but I don’t see that in the
Contribution section anymore. Keeping our old tickets is essential.Based on some earlier messages on this list I got the impression
that you have to install RT 3.2.3 to import the files dumped
by the rt2-to-rt3 tool, then upgrade that to 3.4.x applying
the database updates as described in the README to get to
the current schema.
yes, this may be the case.
There is a script in:
download.bestpractical.com/pub/rt/contrib/ gone
to convert from pg to mysql, but I’m not sure exactly when
you should use it. After pulling into 3.2.3 on pg might be
the best match.
No, you don’t need to use this. You can dump from Pg and import to
MySQL with rt2-to-rt3 util.
–
Les Mikesell
les@futuresource.com
Best regards, Ruslan.
Les Mikesell wrote:
Based on some earlier messages on this list I got the impression
that you have to install RT 3.2.3 to import the files dumped
by the rt2-to-rt3 tool, then upgrade that to 3.4.x applying
the database updates as described in the README to get to
the current schema.
If you grab the latest rt2-to-rt3 code from the repository, it should
let you successfully upgrade from 2.0.x to 3.4 (or even 3.5). No
promises, but a first past test using data from rt.cpan.org looked to be
successful. I’d try it out and see if it works for you.
One thing to watch out for, make sure the mysqld variable
max_packet_size is set to a suitably high value or else your
import/export might die early.
Cheers,
Tom