[rt-users] RT internals

[Asanka Gunasekera]

Hi Tim thanks for the reply, the upgrade path that you have explain seem fairlly simple though consumes bit more time then in-place upgrade I believe but its safe to have the upper hand on fall back to the original system just in case if something to go wrong.

Thank you again Best Regards

Asanka




________________________________
 From: Tim Cutts <tjrc at sanger.ac.uk>
To: Asanka Gunasekera <asanka_gunasekera at yahoo.co.uk> 
Cc: "rt-users at lists.bestpractical.com" <rt-users at lists.bestpractical.com> 
Sent: Tuesday, 11 September 2012, 14:58
Subject: Re: [rt-users] RT internals
 
On 11/09/2012 06:48, Asanka Gunasekera wrote:
> Hi Tim, thank you for the reply, bigest problem that I have not been a
> perl programer, hope you don't mind me asking bit more clarifications
> 
> I am using Oracle as my database and I could not make head or tail of
> the relations :) guess need to sit by this and real go through the DB

I can't help you with the Oracle stuff - MySQL is the only database I
really know in any detail.

>> 3. if I need to migrate to a new installation (with out upgrade) how
>> would I go about this task (would it be as just to create the new
>> instance and configure all the plugins as per the current and just do a
>> backup and restore on the db)
> 
> Yes.  I've done that before.  As long as you're not changing the
> software versions, just copying to a new system, it should be fine.
> 
> Asanka => so this is not the way to do an upgrade? is it because there
> could be DB changes in the new release?

There quite frequently are database updates in new releases.  When
performing a major new release, what I do is:

Preamble:  Disable incoming web requests and queue email to the RT
server (you don't want to lose any ticket transactions during the upgrade)

1)  Shut RT down and copy the database to a new server (which is easy
for me since I run the database in a virtual machine and can just clone
the VM)

2)  Do the same for the web server, if it's on a separate machine from
the database.

3)  Perform the upgrade procedure, including any database updates
required, on the new copy, and test it, in particular any local
customisations you have in /opt/rt4/local.

4)  If everything's working, shut down the old servers, and re-enable
the web and email traffic, pointing to the new servers.

This is a fairly complex way of performing an upgrade, but it has the
advantage that you can easily back out of it if it goes wrong, and go
back to your old system, which is not simple if you do an in-place
upgrade of the live system.

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. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20120911/0b427163/attachment.htm>