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 Sorry.. no SuSE 9.1 rpm for 1.2.3 Last time I did this kind of migration of otrs data it was between two different SuSE v8.x boxes ... Have done the upgrade on 9.0, but not with 9.1. otrs is no longer on the SuSE distribution CD for v9.1, and I suspect the YaST support no longer exists. However, I do not see any immediate reason why a SuSE 9.0 otrs rpm should not install on a 9.1 box. There is a possible alternative approach to migrating than installing an older copy of otrs and upgrading. Things are a bit different between SuSE 9.0 and SuSE 9.1. 9.0 defaults to a 2.4.x kernel with an option of 2.6.x (for the adventurous). 9.1 is 2.6.x by default. This does cause some issues, but none that I would expect to effect otrs. Purely copying the database files as suggested below could open a somewhat different can of worms, and is probably only safe when source and target configurations are exactly the same (SuSE 9.0 and SuSE 9.1 also run slightly different mysql and apache builds as well as run different kernels so do not fit this criterion). The otrs backup set can be compressed and with larger databases means there should be less to copy to the new target or to media. In theory one could restore the database from the backup set without the pre-requisite of installing otrs and using the appropriate restore script, by creating the database and then applying the backup sql script directly to mysql. One would also need to create the local mysql otrs account and give it the rights to otrs database. The relevant commands are in the restore.sh script, (which could be modified so that it did not use otrs configuration information info to pass to those commands). The Backup set also includes the Config.pm file, which could be copied into a subsequent otrs installation hence bypassing the need to run the installer. On Thu, 2004-11-04 at 16:23, Chris Salter wrote:

I recently moved our system to a new box and took the opportunity to upgrade from 1.1.3 to 1.3.1.

All I did was copy the database files to the new system, restart MySQL, and run the

database upgrade scripts. As far as I can tell, there were no problems that resulted,

and we've been using the new machine for a few weeks now. That was on Windows machines,

so it's possible that it'll work differently on Linux.

-- Chris Salter Software Engineer ZANTAZ, Inc.

-----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Marshall28 Sent: November 4, 2004 11:03 AM To: User questions and discussions about OTRS. Subject: RE: [otrs] Installing 1.3.2 and Restoring 1.2.3 DBase

Thank you so much for taking the time to post and help me out.

I will try and upgrade this way. I'm curious if you have a copy of the older version of OTRS 1.2.3

for SuSE 9.1? I have it for SuSE 9.0 but not 9.1.

thanks marshall

-----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org]On Behalf Of Graham Smith Sent: Thursday, November 04, 2004 6:09 AM To: otrs@otrs.org Subject: Re: [otrs] Installing 1.3.2 and Restoring 1.2.3 DBase

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: [ Stuff Deleted] -- Meum est propositum In tabernum mori,

Graham Smith _______________________________________________ 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/

_______________________________________________ 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/

_______________________________________________ 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 _______________________________________________ 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/

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? marshall