<html><body><div style="color:#000; background-color:#fff; font-family:times new roman, new york, times, serif;font-size:12pt">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.<br><br>Thank you again Best Regards<br><br>Asanka<br><div><span><br></span></div><div><br></div> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div style="font-family: times new roman, new york, times, serif; font-size: 12pt;"> <div dir="ltr"> <font face="Arial" size="2"> <hr size="1"> <b><span style="font-weight:bold;">From:</span></b> Tim Cutts <tjrc@sanger.ac.uk><br> <b><span style="font-weight: bold;">To:</span></b> Asanka Gunasekera <asanka_gunasekera@yahoo.co.uk> <br><b><span style="font-weight:
bold;">Cc:</span></b> "rt-users@lists.bestpractical.com" <rt-users@lists.bestpractical.com> <br> <b><span style="font-weight: bold;">Sent:</span></b> Tuesday, 11 September 2012, 14:58<br> <b><span style="font-weight: bold;">Subject:</span></b> Re: [rt-users] RT internals<br> </font> </div> <br>On 11/09/2012 06:48, Asanka Gunasekera wrote:<br>> Hi Tim, thank you for the reply, bigest problem that I have not been a<br>> perl programer, hope you don't mind me asking bit more clarifications<br>> <br>> I am using Oracle as my database and I could not make head or tail of<br>> the relations :) guess need to sit by this and real go through the DB<br><br>I can't help you with the Oracle stuff - MySQL is the only database I<br>really know in any detail.<br><br>>> 3. if I need to migrate to a new installation (with out upgrade) how<br>>> would I go about this task (would it be as just to create the new<br>>> instance and
configure all the plugins as per the current and just do a<br>>> backup and restore on the db)<br>> <br>> Yes. I've done that before. As long as you're not changing the<br>> software versions, just copying to a new system, it should be fine.<br>> <br>> Asanka => so this is not the way to do an upgrade? is it because there<br>> could be DB changes in the new release?<br><br>There quite frequently are database updates in new releases. When<br>performing a major new release, what I do is:<br><br>Preamble: Disable incoming web requests and queue email to the RT<br>server (you don't want to lose any ticket transactions during the upgrade)<br><br>1) Shut RT down and copy the database to a new server (which is easy<br>for me since I run the database in a virtual machine and can just clone<br>the VM)<br><br>2) Do the same for the web server, if it's on a separate machine from<br>the
database.<br><br>3) Perform the upgrade procedure, including any database updates<br>required, on the new copy, and test it, in particular any local<br>customisations you have in /opt/rt4/local.<br><br>4) If everything's working, shut down the old servers, and re-enable<br>the web and email traffic, pointing to the new servers.<br><br>This is a fairly complex way of performing an upgrade, but it has the<br>advantage that you can easily back out of it if it goes wrong, and go<br>back to your old system, which is not simple if you do an in-place<br>upgrade of the live system.<br><br>Tim<br><br><br><br>-- <br> The Wellcome Trust Sanger Institute is operated by Genome Research <br> Limited, a charity registered in England with number 1021457 and a <br> company registered in England with number 2742969, whose registered <br> office is 215 Euston Road, London, NW1 2BE. <br><br><br> </div> </div> </div></body></html>