All,
We have been running RT V3.6.6 for the last five years, with no
upgrades due to customer (and management) paranoia.
We are now starting a new contract with the same customer, and a new
installation is at hand. Clearly, we would like to run the up to date
product, as V3.6.6 is now an unsupported release.
Does anyone have any recommendations as to the best practice for an
upgrade path to V4.0.9? We need to keep the old data, of course.
Best Regards,
Camron
Camron W. Fox
Hilo Office
High Performance Computing Group
Fujitsu Management Services of America, Inc.
E-mail: cwfox@us.fujitsu.com
We have been running RT V3.6.6 for the last five years, with no
upgrades due to customer (and management) paranoia.
We are now starting a new contract with the same customer, and a new
installation is at hand. Clearly, we would like to run the up to date
product, as V3.6.6 is now an unsupported release.
Does anyone have any recommendations as to the best practice for an
upgrade path to V4.0.9? We need to keep the old data, of course.
Have you reviewed UPGRADING-3.6 UPGRADING-3.8 UPGRADING-4.0 shipped in
RT4’s docs/ directory and also available on
http://docs.bestpractical.com ? They provide our recommended upgrade
path. Step 2 and 6b of the README also lay out similar information
and pointers.
There’s also a blog post laying out pointers to the information
provided in all of those documents.
-kevin
We have been running RT V3.6.6 for the last five years, with no
upgrades due to customer (and management) paranoia.
We are now starting a new contract with the same customer, and a new
installation is at hand. Clearly, we would like to run the up to date
product, as V3.6.6 is now an unsupported release.
Does anyone have any recommendations as to the best practice for an
upgrade path to V4.0.9? We need to keep the old data, of course.
Have you reviewed UPGRADING-3.6 UPGRADING-3.8 UPGRADING-4.0 shipped in
RT4’s docs/ directory and also available on
http://docs.bestpractical.com ? They provide our recommended upgrade
path. Step 2 and 6b of the README also lay out similar information
and pointers.
There’s also a blog post laying out pointers to the information
provided in all of those documents.
Upgrading to RT 4 — Best Practical Solutions
-kevin
Kevin,
As all of the equipment is new, I would like to, if at all possible, to
install 4.0.9 from scratch on one of the new machines and import the DB
data from the old 3.6.6 installation.
I'd rather not migrate the 3.6.6 installation to a new machine and then
have to upgrade to the 4.0.9 version on that machine. Seems like we
should be able to simplify the procedure.
Best Regards,
Camron
Camron W. Fox
Hilo Office
High Performance Computing Group
Fujitsu Management Services of America, Inc.
E-mail: cwfox@us.fujitsu.com
We have been running RT V3.6.6 for the last five years, with no
upgrades due to customer (and management) paranoia.
We are now starting a new contract with the same customer, and a new
installation is at hand. Clearly, we would like to run the up to date
product, as V3.6.6 is now an unsupported release.
Does anyone have any recommendations as to the best practice for an
upgrade path to V4.0.9? We need to keep the old data, of course.
Have you reviewed UPGRADING-3.6 UPGRADING-3.8 UPGRADING-4.0 shipped in
RT4’s docs/ directory and also available on
http://docs.bestpractical.com ? They provide our recommended upgrade
path. Step 2 and 6b of the README also lay out similar information
and pointers.
There’s also a blog post laying out pointers to the information
provided in all of those documents.
Upgrading to RT 4 — Best Practical Solutions
-kevin
Kevin,
As all of the equipment is new, I would like to, if at all possible, to
install 4.0.9 from scratch on one of the new machines and import the DB
data from the old 3.6.6 installation.
I’d rather not migrate the 3.6.6 installation to a new machine and then
have to upgrade to the 4.0.9 version on that machine. Seems like we
should be able to simplify the procedure.
we’ve just done this and it was completely painless. Just follow
Updating.sql. I think the only thing that wasn’t automatically scripted
was changing the table types from MyISAM to INNODB.
Best Regards,
Camron
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.
As all of the equipment is new, I would like to, if at all possible, to
install 4.0.9 from scratch on one of the new machines and import the DB
data from the old 3.6.6 installation.
I’d rather not migrate the 3.6.6 installation to a new machine and then
have to upgrade to the 4.0.9 version on that machine. Seems like we
should be able to simplify the procedure.
Nothing in the docs claims you have to migrate the old installation,
just the old data. What you describe wanting is a very normal upgrade
process for RT.
As all of the equipment is new, I would like to, if at all possible, to
install 4.0.9 from scratch on one of the new machines and import the DB
data from the old 3.6.6 installation.
I’d rather not migrate the 3.6.6 installation to a new machine and then
have to upgrade to the 4.0.9 version on that machine. Seems like we
should be able to simplify the procedure.
As noted later in the thread, nothing in the docs or in my blog
post imply that you have to upgrade to 4.0 before copying to the
new box. What you’ve described (copying the 3.6 db to the new 4.0
box) is standard.
If you find official documentation suggesting otherwise, please let us
know so it can be fixed.
-kevin
we’ve just done this and it was completely painless. Just follow
Updating.sql. I think the only thing that wasn’t automatically scripted
was changing the table types from MyISAM to INNODB.
Iain,
What DB did you create on the far side? I'm dumping a DB called rt3 and
upgrading to rt4. Should I create a DB called rt3 or rt4?
mysql> CREATE DATABASE rt4 DEFAULT CHARACTER SET Latin1;
Best Regards,
Camron
Camron W. Fox
Hilo Office
High Performance Computing Group
Fujitsu Management Services of America, Inc.
E-mail: cwfox@us.fujitsu.com
we’ve just done this and it was completely painless. Just follow
Updating.sql. I think the only thing that wasn’t automatically scripted
was changing the table types from MyISAM to INNODB.
Iain,
What DB did you create on the far side? I’m dumping a DB called rt3 and
upgrading to rt4. Should I create a DB called rt3 or rt4?
mysql> CREATE DATABASE rt4 DEFAULT CHARACTER SET Latin1;
You can use the sbin/rt-setup-database tool to create the database and
grant privileges correctly:
/opt/rt4/sbin/rt-setup-database --action create,acl --prompt-for-dba-password
This will only create the database and grant privileges. It won’t create any
tables or insert any default starting data, since you’ll be importing those
from your rt3 db that you intend to upgrade.
When I moved from rt3 to rt4 I cloned my rt3 database to rt4 and then upgraded that DB in place.
Yes, that’s totally reasonable. However, a common method of “cloning”
is using a dump + load. That doesn’t preserve the database itself or
the RT user for the database server. Hence my suggestion.