Mike Friedman wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 18 Aug 2006 at 12:21 (-0400), Helmuth Ramirez wrote:
Thanks Philip for the tip and thanks for writing up that article! (I
would have never figured out that binary tip on the db dump!)
I'm planning to move from RT 3.4.2 on one machine to 3.4.5 on a
different machine with a different OS. I understand that there were no
db changes from 3.4.2 to 3.4.5, so I was hoping I could dump the mysql
db on the first system, restore it on the new machine and just point to it.
Now, this thread has me wondering about the whole issue of mysql dumps.
Do I need to use the 'default binary' option also, not only when I do my
conversion, but even on my current nightly db backups? First of all, is
it necessary, and secondly, is there a downside to using that option?
Thanks.
Mike
_________________________________________________________________________
Mike Friedman IST/System and Network Security
[EMAIL PROTECTED] 2484 Shattuck Avenue
1-510-642-1410 University of California at Berkeley
http://socrates.berkeley.edu/~mikef http://security.berkeley.edu
_________________________________________________________________________
-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.8
iQA/AwUBROY1Ra0bf1iNr4mCEQJZpgCglE5NnYd0IWKOnnrOEPdH1mo2KfQAmwQF
UiKPRHj3upgqp/4k/hSDG7Bg
=RGPs
-----END PGP SIGNATURE-----
_______________________________________________
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
This is what I did when migrating from 3.0.9 to 3.6.1:
1: Set up the old version locally on my workstation (I use Red Hat WS 4
so it was an easy thing to do). If you are using Windows just install
RT to an intermediate server that you will use just for the migration
process.
2: We were using Postgres for our old setup so migrating involved using
the Postgres->MySQL script created by Jesse with some modifications.
However, it would appear that you are starting with a MySQL database.
So basically, all you need to do is create a dumpfile of the RT database
using mysqldump and copy it to the intermediate server.
3: Import the database dumpfile into your instance of the old RT version
you are migrating from on the intermediate server.
4: Install v3.6.1 with the 'make upgrade' build option using the
'--with-rt-database=' configure option pointing to the same database as
the old version.
5: Run all the scripts in the etc/upgrade directory of the untarred RT
directory (I'm not 100% on the name of that upgrade directory. It will
tell you what it is when 'make upgrade' is done). This will perform all
the upgrades on the database ultimately giving you a database with all
your old data but in a newer schema.
6: Create a dumpfile of the upgraded database using 'mysqldump' and copy
it to the new, permanent server.
7: After installing a fresh instance of v3.6.1, import the dumpfile you
created on the intermediate server using 'mysql -u root -p < dumpfile'
8: Log into RT and enjoy that Perl-y goodness.
I hope that was clear enough and will help you out. Good luck!
Mathew Snyder
_______________________________________________
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
