You can upgrade the whole way. The upgrading scripts will bring you current.
Then you just need to hook up your new RT instance to the old database
(or, copy the database to your new machine first).
My database isn’t on the RT machine so it makes it easier. We generally
build completely new RT machines for each major version, or when the OS
needs an upgrade (RT 3.6.x to 3.8.x, RHEL 4 to RHEL 5, etc).On 8/10/10 8:41 AM, Mike Johnson wrote:
Is there anywhere on the wiki that documents which releases can be
upgraded to from each?
I guess basically what I"m looking for is the shortest line from 3.2.1
Is there a general rule of thumb? like every 3.x I should look at the
UPGRADING? or would I have to dig into the point point releases?
Thanks for the insight. I attempted to search the wiki, but I had a
hard time even trying to figure out what that is called…
On Tue, Aug 10, 2010 at 9:33 AM, Kevin Falcone <firstname.lastname@example.org mailto:email@example.com> wrote:
On Tue, Aug 10, 2010 at 09:09:21AM -0400, Mike Johnson wrote:
> I'm sitting here with a clean 3.8.8 RT install, and I have
our current 3.2.1 that is in use...
> I want to be kind to my users, and migrate data... but I
don't want to spend too much
> time/resources doing so...
> Would a backup of the rt database in 3.2.1 and a restore onto
You want to have a look at the UPGRADING files.
The database structure is not compatible and you will need to run the
various scripts described in UPGRADING.
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com
Northern Ontario School of Medicine
955 Oliver Road
Thunder Bay, ON P7B 5E1
Phone: (807) 766-7331
Email: firstname.lastname@example.org mailto:email@example.com
College of ACES ITCS
University of Illinois at Urbana-Champaign