- Moving RT database - Email found in subject

Hi Leon,

Yes, you should be able to export the database on to a new server but
you will need to make sure you set up the user permissions in the
database to allow the RT database user to connect from the remote host
and made any firewall/IP Tables changes to allow connections.

As for the code upgrade, I’ve done this in the past and it’s pretty
straight forward providing you make sure you have copied any changes in
the new RT_SiteConfig file to your existing one.

Good luck,

Nick-----Original Message-----
From: Leon Sonntag [mailto:leon@iwa-solutions.com]
Sent: 19 April 2004 23:29
To: rt-users@lists.bestpractical.com
Subject: [SPAM] - [rt-users] Moving RT database - Email found in subject

I am looking at:

  1. Moving my RT database to a different System. Both Os’s are RedHat 8
  2. Upgrading to RT 3.10 I am currently running 3.0.6

–Since the backend is a mySQL database, can I get away with simply
exporting the old DB and importing it on the newly created?
–I have seen several emails about going from earlier versions to
3.10. Any recommendations (beyond the README’s in the in the
Distribution)

Most anything is easy after you’ve done it successfully a few times

Leon Sonntag
Innovative Web Applications
leon at iwa-solutions dot com

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

RT Developer and Administrator training is coming to LA, DC and
Frankfurt this spring and summer.
http://bestpractical.com/services/training.html

Sign up early, as class space is limited.

This message is intended solely for the use of the individual or organisation to whom it is addressed and may contain confidential or copyrighted information. If you have received this message in error, please reply to the originator and delete it immediately. If you are not the intended recipient, you should not use, copy, alter, disseminate, print or disclose the contents of this message.

Information or opinions expressed in this message and/or any attachments are those of the author and are not necessarily those of EFSS Ltd. or its affiliates. EFSS Ltd. accepts no responsibility for loss or damage arising from its use, including damage from viruses.

Note: Internet e-mails are not necessarily secure. EFSS Ltd. does not accept responsibility for changes made to this message after it was sent.