Emmanuel, Thanks a bunch. I don't have any local things but I did install Asset Tracker which is used a lot on this system.But at least I can go through this and not blow up my working system
Thanks again. >>> Emmanuel Lacour <[email protected]> 1/4/2011 4:48 PM >>> On Tue, Jan 04, 2011 at 04:38:28PM -0500, John BORIS wrote: > I am currently running RT 3.6.6. I want to go to the newest release. I > am setting up another Virtual machine to run through this upgrade so I > can do this swap overnight and keep the system available to my users. I > plan to install and get working the latest version of RT and then load > in the data from the old system. Or is it better to build a 3.6.6 system > and then upgrade that one to the latest version. I have a lot of info > in the 3.6.6 version. > something like this should give you time to test and count the needed downtime. - install your 3.8.8 on your new VM, but don't create the DB - put your old local modifications, RT configuration in RT 3.8.8 with needed adjustement if any - do a first SQL import of your 3.6.6 DB in the 3.8.8 VM - run the rt-setup-database --action upgrade to upgrade your DB (and any DB related update written in the UPGRADING doc (especially if you are using MySQL) - measure the time for the two previous steps, this will be your future downtime to switch your production to 3.8.8 - test your new system then to really upgrade your production system to your new VM using rt 3.8.8: - stop your old RT - drop the DB on the new RT - import the DB and run again the upgrade procedure - start your new RT and adjust mail routing/dns so it is now used in place of old one (or just change the IP)
