Thanks for the response. We are using MySQL too so i'll look at that information.
Aaron On Mon, Oct 20, 2008 at 4:13 PM, Helmuth Ramirez < [EMAIL PROTECTED]> wrote: > We recently performed this upgrade. What we ended up doing was > installing 3.8.1 on the new server, dumping db from 3.6 server, importing it > to 3.8 server, ran the db scripts to get it up to date. In our case, we're > running MySQL, it is VERY important you follow the MySQL upgrade > instructions, otherwise you'll end up with garbled attachments. > > > > As far as just dumping your 3.6 db into 3.8. Yes, it'll allow you to view > your tickets (I was able to), but attachments didn't work out too well > (refer to MySQL upgrade docs). > > > > Good luck > > > > *From:* [EMAIL PROTECTED] [mailto: > [EMAIL PROTECTED] *On Behalf Of *Aaron Zuercher > *Sent:* Monday, October 20, 2008 4:59 PM > *To:* [email protected] > *Subject:* [rt-users] move to new server and upgrade > > > > Hello, > I've been using RT 3.6.0 for awhile in my organization with great success. > I'd like to move it to a new box and at the same time upgrade to lastest > version. Can someone advise me on the best method for doing this? I assume > I can't take data out of my 3.6 database and import directly into the 3.8 > database? > > So would it be best to upgrade to 3.8 before export or intall 3.6 on new > server adn then upgrade after importing? > > Thanks, > Aaron >
_______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [EMAIL PROTECTED] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
