Dump to rt3

Hi rt-users,

I want to migrate rt2.0.15 to rt3.4.1. It’s actually an easy thing
but it does not work absolut correctly.
The database from the rt2 instance has about 20 users, 5 queues and 1000
tickets.
With the rt2-to-rt3-1.22 perl script the database will be dumped without
errors,
the import of the data has only a couple of non-standard scrip errors.
My Problems are a few tickets in seperate queues which will be
created without history anyhow.

What can I do to create the history of these tickets correctly?

Many Thanks

Markus Schï¿œpfer

Markus Schï¿œpfer wrote:

Hi rt-users,

I want to migrate rt2.0.15 to rt3.4.1. It’s actually an easy thing
but it does not work absolut correctly.
The database from the rt2 instance has about 20 users, 5 queues and
1000 tickets.
With the rt2-to-rt3-1.22 perl script the database will be dumped
without errors,
the import of the data has only a couple of non-standard scrip errors.
My Problems are a few tickets in seperate queues which will be
created without history anyhow.

AFAIK, that only works to dump into an RT 3.2.x install. So install
3.2.x, import the data, then upgrade to 3.4.1.

What can I do to create the history of these tickets correctly?

Many Thanks

Markus Schï¿œpfer


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

Drew Barnes
Applications Analyst
Raymond Walters College
University of Cincinnati

Drew Barnes schrieb:

Markus Schï¿œpfer wrote:

Hi rt-users,

I want to migrate rt2.0.15 to rt3.4.1. It’s actually an easy thing
but it does not work absolut correctly.
The database from the rt2 instance has about 20 users, 5 queues and
1000 tickets.
With the rt2-to-rt3-1.22 perl script the database will be dumped
without errors,
the import of the data has only a couple of non-standard scrip errors.
My Problems are a few tickets in seperate queues which will be
created without history anyhow.

AFAIK, that only works to dump into an RT 3.2.x install. So install
3.2.x, import the data, then upgrade to 3.4.1.

What can I do to create the history of these tickets correctly?

Many Thanks

Markus Schï¿œpfer


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Be sure to check out the RT Wiki at http://wiki.bestpractical.com

merci,
i will try it…

You might try my modifications to the dumpfile-to-rt-3.0 script. I did
the same upgrade to rt-3.4.1 just a few weeks ago on a very large
database. Some of the changes had to do with the new database
structure, but there were also a lot of changes related to cleaning up
old cruft in the database.

One thing you should be careful of: just last week I found out that the
script (both the original or with my mods) doesn’t properly set the
Parent field of Attachment records. (I haven’t got around to fixing
that.) Also, avoid doing an incremental import if you have any custom
fields (keywords), because it doesn’t copy those over properly.
Otherwise, it seems to work very well.

– TrevinOn Tue, 2005-05-31 at 15:28 +0200, Markus Schüpfer wrote:

Hi rt-users,

I want to migrate rt2.0.15 to rt3.4.1. It’s actually an easy thing
but it does not work absolut correctly.
The database from the rt2 instance has about 20 users, 5 queues and 1000
tickets.
With the rt2-to-rt3-1.22 perl script the database will be dumped without
errors,
the import of the data has only a couple of non-standard scrip errors.
My Problems are a few tickets in seperate queues which will be
created without history anyhow.

What can I do to create the history of these tickets correctly?

Many Thanks

Markus Schüpfer

dumpfile-to-rt-3.0 (31.3 KB)

Trevin Beattie schrieb:

You might try my modifications to the dumpfile-to-rt-3.0 script. I did
the same upgrade to rt-3.4.1 just a few weeks ago on a very large
database. Some of the changes had to do with the new database
structure, but there were also a lot of changes related to cleaning up
old cruft in the database.

One thing you should be careful of: just last week I found out that the
script (both the original or with my mods) doesn’t properly set the
Parent field of Attachment records. (I haven’t got around to fixing
that.) Also, avoid doing an incremental import if you have any custom
fields (keywords), because it doesn’t copy those over properly.
Otherwise, it seems to work very well.

– Trevin

Hi rt-users,

I want to migrate rt2.0.15 to rt3.4.1. It’s actually an easy thing
but it does not work absolut correctly.
The database from the rt2 instance has about 20 users, 5 queues and 1000
tickets.
With the rt2-to-rt3-1.22 perl script the database will be dumped without
errors,
the import of the data has only a couple of non-standard scrip errors.
My Problems are a few tickets in seperate queues which will be
created without history anyhow.

What can I do to create the history of these tickets correctly?

Many Thanks

Markus Sch�pfer

…it works …

thanks Trevin

Markus Sch�pfer MULTA MEDIO Informationssysteme AG