Mailing List Archive: Request Tracker: Devel

Re: [rt-users] Upgrade RT

Index | Next | Previous | View Threaded

vadud3 at gmail

Apr 28, 2009, 10:45 AM

Post #1 of 3 (537 views)
Permalink

Re: [rt-users] Upgrade RT

On Tue, Nov 18, 2008 at 6:33 AM, Tim Cutts <tjrc[at]sanger.ac.uk> wrote:

>
> On 17 Nov 2008, at 10:34 pm, Asif Iqbal wrote:
>
> Do I upgrade from RT 3.4.5 to RT 3.8.1 directly? Or there is a roadmap
>> somewhere?
>>
>
> You can do this in almost one go, yes. It's almost exactly what I'm doing
> with my production RT, where I'm going from 3.4.2 to 3.8.1
>
>
>> Do I upgrade the mysql 4.0.24 to 4.1 first before upgrading the RT?
>>
>
> Yes. Or at least, here's what I've tested, and seems to work quite well:
>
> 1) Set up a new RT box for your new server, so that you can always back
> out if this goes wrong. On this server, install the new version of MySQL
> you want to use, and install RT 3.8.1
>
> 2) Make a dump of your production MySQL instance, and load it into the new
> MySQL database.
>
> 3) Run the /opt/rt3/sbin/rt-setup-database --action upgrade command as
> detailed in the RT 3.8.1 README file, but only as far as version 3.8.0
>
> 4) Run the MySQL upgrade script, as detailed in UPGRADING.mysql, and apply
> the SQL statements it wants you to make. This can take a long time; the
> alter table statements are pretty slow-running.
>
> 5) Run the /opt/rt3/sbin/rt-setup-database --action upgrade thing again
> for the last small changes from 3.8.0 to 3.8.1
>

Ok now that upgrade completed on the test system, I now see 5000 more
tickets already
created on the production systems. Do I have to redo this whole thing? I
have binlog enabled
since the beginning of the original instance. How do I append those new 500
tickets?
I guess I am now on a catchup game :-)

>
> After that, it all seemed to work pretty well.
>
> Tim
>
>
> --
> The Wellcome Trust Sanger Institute is operated by Genome ResearchLimited,
> a charity registered in England with number 1021457 and acompany registered
> in England with number 2742969, whose registeredoffice is 215 Euston Road,
> London, NW1 2BE.
>

--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

vadud3 at gmail

Apr 28, 2009, 11:01 AM

Post #2 of 3 (497 views)
Permalink

Re: [rt-users] Upgrade RT [In reply to]

On Tue, Apr 28, 2009 at 1:53 PM, Tom Lahti <toml[at]bitstatement.net> wrote:

> > Ok now that upgrade completed on the test system, I now see 5000 more
> > tickets already
> > created on the production systems. Do I have to redo this whole thing? I
> > have binlog enabled
> > since the beginning of the original instance. How do I append those new
> 500
> > tickets?
> > I guess I am now on a catchup game :-)
>
> You're gonna have to shut down the production instance during the
> conversion. No way around it. Stay late and bring pizza and beer ;)

I am looking for a way to use the binlogs to add the new tickets to the test
server

That way I don't have to dump the whole database again and the import and
all that
from the beginning.

>
>
>
> --
> -- ============================
> Tom Lahti
> BIT Statement LLC
>
> (425)251-0833 x 117
> http://www.bitstatement.net/
> -- ============================
>

--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

tjrc at sanger

Apr 28, 2009, 11:07 AM

Post #3 of 3 (498 views)
Permalink

Re: [rt-users] Upgrade RT [In reply to]

On 28 Apr 2009, at 7:01 pm, Asif Iqbal wrote:

> On Tue, Apr 28, 2009 at 1:53 PM, Tom Lahti <toml[at]bitstatement.net>
> wrote:
>
>>> Ok now that upgrade completed on the test system, I now see 5000
>>> more
>>> tickets already
>>> created on the production systems. Do I have to redo this whole
>>> thing? I
>>> have binlog enabled
>>> since the beginning of the original instance. How do I append
>>> those new
>> 500
>>> tickets?
>>> I guess I am now on a catchup game :-)
>>
>> You're gonna have to shut down the production instance during the
>> conversion. No way around it. Stay late and bring pizza and beer ;)
>
>
>
> I am looking for a way to use the binlogs to add the new tickets to
> the test
> server
>
> That way I don't have to dump the whole database again and the
> import and
> all that
> from the beginning.

There's no simple way to do that because the schema has changed, so
your binary logs can't be applied to the new server. When I updated
our RT I did what the last person suggested; shut down the production
RT, dump, load, upgrade, bring up new production RT.

Tim

--
The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
_______________________________________________
List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com