RT2 to RT3 migration tool v1.8

Now available from:

http://bestpractical.com/pub/rt/devel/rt2-to-rt3.tar.gz

This release should improve the stability and accuracy of the import
process.

http://www.bestpractical.com/rt – Trouble Ticketing. Free.
rt-announce mailing list
rt-announce@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-announce

Is there an rt1-rt3 db conversion, or do I need to do it in 2 steps? Do I
need to install all of v2 before going to v3?

–Justin ClaytonOn Wed, 9 Apr 2003, Jesse Vincent wrote:

Now available from:

http://bestpractical.com/pub/rt/devel/rt2-to-rt3.tar.gz

This release should improve the stability and accuracy of the import
process.

Justin Clayton
VLSI Research System Administrator
University of Washington
Electrical Engineering Dept
justincl@u.washington.edu
206/543.2523 EE/CSE 307E

Hi All,

Okay, this mentions the import process taking around 24 hours for a
large db (is 35,000 considered large ?) … however is this supposed to
be total time for import and export, or just import.

I only ask because I have started the export process going and it seems
to be taking about 6-7 seconds per ticket which equates to about 58
hours for me.

Any clues or suggestions ?

mysql Ver 12.18 Distrib 4.0.12, for pc-linux (i686)
perl, v5.8.0 built for i686-linux

Cheers,

Simon.

Hi All,

Okay, this mentions the import process taking around 24 hours for a
large db (is 35,000 considered large ?) … however is this supposed to
be total time for import and export, or just import.

I only ask because I have started the export process going and it seems
to be taking about 6-7 seconds per ticket which equates to about 58
hours for me.

Times are incredibly dependent on processor and ram and database tuning.
Please see the section of the importer’s readme about incremental
upgrades. It’s designed to deal with just the sort of issue you’re
having.

Any clues or suggestions ?

mysql Ver 12.18 Distrib 4.0.12, for pc-linux (i686)
perl, v5.8.0 built for i686-linux

Cheers,

Simon.


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Have you read the FAQ? The RT FAQ Manager lives at http://fsck.com/rtfm

http://www.bestpractical.com/rt – Trouble Ticketing. Free.

Hi Jesse,

Times are incredibly dependent on processor and ram and database tuning.
Please see the section of the importer’s readme about incremental
upgrades. It’s designed to deal with just the sort of issue you’re
having.

Yeah, I figured that, but the box spec is alright, and isn’t exactly busy.

True, MySQL is straight out of the box v4 … any tuning suggestions
anyone could make would be much appreciated.

(Box : 1Ghz Athlon, 512MB RAM, running Linux 2.2)

I did look at incremental’s and will be using them … just wondered if there
was anything else I could do to speed things up.

Cheers,

Simon.

Hi Jesse,

Times are incredibly dependent on processor and ram and database tuning.
Please see the section of the importer’s readme about incremental
upgrades. It’s designed to deal with just the sort of issue you’re
having.

Yeah, I figured that, but the box spec is alright, and isn’t exactly busy.

True, MySQL is straight out of the box v4 … any tuning suggestions
anyone could make would be much appreciated.

The mysql docs at mysql.com should have plenty of tuning examples.

(Box : 1Ghz Athlon, 512MB RAM, running Linux 2.2)

I did look at incremental’s and will be using them … just wondered if there
was anything else I could do to speed things up.

Cheers,

Simon.

http://www.bestpractical.com/rt – Trouble Ticketing. Free.