Seeing no-one else has commented I will make some observations as I have been through a similar process in the past ...
On Wed, 2004-11-03 at 20:47, Marshall28 wrote: > If I'm installing OTRS 1.3.2 from scratch on a new system do you recommend > me going through all of these steps and then restoring my 1.2.3 database? > What order should things be done, in order to successfully Install 1.3.2 and > restore my 1.2.3 database bringing me up to par with my current 1.2.3 OTRS > database? I just want to make sure I have the most up to date database with > all the new features of OTRS 1.3.2. > > 1. Install the latest OTRS-RPM for SuSE Linux (http://otrs.org/) and all > required > software packages (if needed, Apache, MySQL, ...) with YaST or "rpm -i > otrs-xxx.rpm". > Err No... The tables in the 1.2.3 version will be in different format from the 1.3.2 tables, you will probably need to ... 1) Backup old 1.2.3 on old server ... 2) Install 1.2.3 version of otrs on new server ... 3) Restore 1.2.3. version of data to new server ... 4) Follow instructions for upgrading from 1.2.3 to 1.3.2... as a safe route. One might get away with restoring between versions but it is probably not worth the additional excitement :-) This will only deal with data ... modified scripts and dtl files will need to be updated manually as required... > 2. Start SuSEconfig If you are using YaST this will be taken care of... You will probably only need to do this if the rpm route is used. > > 3. Restart the webserver (rcapache restart) > > 4. Setup the database via "http://yourhost/otrs/installer.pl"; (just for > MySQL) > > 5. restart the whole OTRS system (rcotrs restart-force) Restarting the webserver forces a reload of modified perl scripts. rcotrs effectively checks MySQL and apache are running and loads them if not. It also gracefully manages otrs cron jobs and the otrs Postmaster scripts, if you are not running any of these you should not need to run rcotrs. One potential problem is that by default rcotrs on SuSE refers to apache, if there is a preference to use apache2 this can be fixed by modifying the /etc/sysconfig/otrs file. However if you wish to use apache2 and if you also wish define the load of otrs via the YaST runlevel editor (at least on 9.0) another tweak is required, the simplest way to do this is to ensure that /etc/init.d/apache links to /etc/init.d/apache2. > 6. Installation finished, login ("http://yourhost/otrs/index.pl";) as user > "[EMAIL PROTECTED]" > with password "root" If you have updated the database your passwords, usernames and queues should revert to whatever they were on the old otrs system. Last time I did this the old mail response and mail address information also migrated across and some of this did need modification. > > --> goto AdminArea and set some config settings (UserAdd, Queues, ...). > > thanks > marshall > > _______________________________________________ > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs > Support oder Consulting für Ihr OTRS System? > => http://www.otrs.de/ -- Meum est propositum In tabernum mori, Graham Smith <[EMAIL PROTECTED]> _______________________________________________ OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs Support oder Consulting für Ihr OTRS System? => http://www.otrs.de/
