On Thu, 2004-11-11 at 17:09, Jesse Shumaker wrote:
Graham Smith wrote:
I decided to look at this a little closer, and have come to the conclusion that a 1.2.3 install is probably not required for a move from 9.0 to 9.1.
If you ....
a) backup the database on the old server using the /opt/otrs/scripts/backup.sh script.
b) Copy backup files to new server.
c) Install 1.3.2 on new server
d) restore using the /opt/otrs/scripts/restore.sh script on new server.
Then apply the upgrade as described in the UPDATE text file from the line ....
*) Update the database changes with
NB You made need to edit Config.pm to reflect changes in server name , before you start otrs. (likewise for any system mail addresses within otrs when otrs is started)
then you should end up with a functional copy of your database on 1.3.2.
The next stage would be sorting out any modified scripts and your procmail configuration if this the latter is used.
On Fri, 2004-11-05 at 20:14, Marshall28 wrote:
Graham,
It seems that the 1.2.3 upgrade is more outlined for me and would provide me with better instructions than the alternative way you mentioned. I would need more instruction in order for me to get it working with a straight 1.3.2 install. I'm not too familiar with mysql and therefore if you could provide me with more detailed instructions on restoring OTRS with version 1.3.2 I would consider trying it that way.
If I go with the 1.2.3 install and then upgrade to 1.3.2, how much would I have to configure version 1.2.3 before I could upgrade to 1.3.2? Would I go through setting up the database with installer.pl? How far would I have to install and configure 1.2.3 before upgrading to 1.3.2?
thanks marshall
-----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org]On Behalf Of Graham Smith Sent: Friday, November 05, 2004 6:58 AM To: User questions and discussions about OTRS. Subject: RE: [otrs] Installing 1.3.2 and Restoring 1.2.3 DBase
[Stuff deleted] _______________________________________________ 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/
so you have tried this and know it works this way? Also, I saw how you mentioned that I would have to update the Config.pm file to update new changes in the server name etc. The Config.pm is part of the restore.sh scripts process. Therefore it should restore when I run that script. Shouldn't it?
If the new server is to replace the old there is no problem. There may be a problem if you wish to run both. One thing I forgot ... Before running the restore.sh script create the MySQL otrs account with the same password as used in the old Config.pm. Entering ... mysql -u root -p -e "grant all privileges on otrs.* to otrs@localhost identified by '<password>'"; should do trick.
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 fr Ihr OTRS System? => http://www.otrs.de/
--
Meum est propositum
In tabernum mori,
Graham Smith