I'm very curious to hear other responses/experiences, but if it were me I would 
shift the old 3.x onto the new hardware and then go through the upgrade 
procedures to bring it up to 4.x.
Maybe not necessary(?), but it would make me feel better that the database gets 
all the required changes made to it.



-----Original Message-----
From: rt-users [mailto:rt-users-boun...@lists.bestpractical.com] On Behalf Of 
Rob Sullivan
Sent: Friday, November 20, 2015 4:51 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] migrate 3.8.9 to current

I have a very old instance of RT running on ancient hardware. I'd like to port 
it over to a new server and current version. I've got a vanilla install of 
4.2.12 on the new server with a mysql database, and I've exported/imported the 
rt3 database from the old server to the new one. I'm looking for a 
recommendation on the best way to run through the database upgrade procedure on 
the new server. 

- shut down apache, change the database name in RT_SiteConfig.pm to rt3? 
- drop vanilla rt4 database and import the rt3 database with name rt4, then run 
make upgrade-database as one normally would?
- other, much smarter option?

Thanks,

Rob Sullivan
Manager of Systems Engineering
Peerless Network Inc
312-506-0948


Reply via email to