Lars Monsees pisze:

Hi,

...

I need, to transfer my acctual OTRS installation, to the new server. Previously the OS on the otrs machine was Debian. Now It's CentOS. Alternatively I can use tthe other Debian machine, but it's as a last resort.

So.. what do you suggest, how to do it without problems? Mabe I need

to

...

do a new install of otrs, and rsync few files and the database?

can you install the exact same version on the new machine? It would be better to transfer data between the same version of OTRS and update later if necessary.

Then make a sql dump that you import on the new machine and copy the config files. Also, make sure to copy adapted files (e.g. modified templates) and ticket attachments (in case you store them in the filesystem)

hth, Lars

Hi, Thanks for repling. I think that the best is to install new otrs and then sync the files. I've made many changes in configuration of otrs. For example create clients,groups,roles, queues, autoresponds. and the Sysconfig options. I don't remember all of them, and I don;t wont to configure it from the beginnig. My version of otrs is: otrs-2.3.4. I saw that the newest version is: otrs-2.4.4. Could I safely install the new version and sync only my files - templates/remaked configs, and insert old database? I can import/export the old database. But which files exacly I need to copy? Could you list them? -- Regards Grzegorz Dajuk

Lars Monsees pisze:

...

I think that the best is to install new otrs and then sync the files. I've made many changes in configuration of otrs. For example create clients,groups,roles, queues, autoresponds. and the Sysconfig options.

I

clients, etc. is stored in the DB, so syncing the files would have no effect.

...

don't remember all of them, and I don;t wont to configure it from the beginnig.

The config is stored in: /opt/otrs/Kernel/Config.pm /opt/otrs/Kernel/Config/Files/ZZZAuto.pm

...

My version of otrs is: otrs-2.3.4. I saw that the newest version is: otrs-2.4.4. Could I safely install the new version and

sync

...

only my files - templates/remaked configs, and insert old database?

no, you have to update your database structure and the old templates are not compatible with the new OTRS version.

Mh... I think that I'm too new to otrs, to make upgrade without any system crashes :)) It;s a production envirement so I can't make any mistake. I suppose, that it's better to me, to make a fresh install of otrs and copy only tickets. Don;t you think so? How can I copy only the tickets? -- Regards Grzegorz Dajuk

Only problem with the transfer is that the databases structure may change from version to version.  The upgrade scripts are one way (upgrade). You'd have to custom a downgrade script and it would potentially cause problems. It would be far easier to maintain consistent versions across each system.  All that would be needed then is to run the backup/restore process via the back-up script. If you have followed OTRS rule for system mods this will cover all needed files for backup. LQ

Hey, I would suggest you to realy take a fresh installation of OTRS but to take the Database of your running OTRS system. You can make an SQL dump of your Database and import it on your new System with your fresh installed OTRS. Take into account that you´ll have to migrate the struktrue of the Database anyway and take some config steps again, but that is due to the fact that you want to use an other system like before. 'mysqldump -u root -p otrs > /root/db_dump.sql' <- this is how to make your dump of the 'otrs' Database copy with scp from this "server" to your new server and import it to your Database, but be aware that you´ll have to drop the pre cofigured database created by the new OTRS System. Login into mysql : 'mysql -u root -p' Provide the password needed and then drop and recreate the database. 'drop database otrs;' 'create database otrs;' Now you can import the files into your Database. 'source /root/db_dump.sql;' As I think that you want to upgrade your otrs in one go you´ll have to run the DBUpdate-to-2.x.mysql.sql, DBUpdate-to-2.x.pl, DBUpdate-to-2.x-post.mysql.sql. You´ll receive some error during the second script, but it doesn´t realy matter as the DB will be migrateted and will be runnig smoothly ;) If you have any more questions just write to the mailinglist :D Mit freundlichen Grüßen / Kind regards Markus Moj Technik TimoCom Soft- und Hardware GmbH In der Steele 2 D-40599 Düsseldorf Tel: +49 211 88 26 80 14 Fax: +49 211 88 26 70 14 eMail: MMoj@TimoCom.com www.TimoCom.com Geschäftsführer: Jens Thiermann, Gunther Matzaitis Amtsgericht Düsseldorf, HRB 34489 From: "Lars Monsees" To: "User questions and discussions about OTRS." Date: 04.09.2009 09:33 Subject: Re: [otrs] Otrs ticketsystem transfer to other server Sent by: otrs-bounces@otrs.org

Mh... I think that I'm too new to otrs, to make upgrade without any system crashes :)) It;s a production envirement so I can't make any mistake.

In that case, testing the upgrade on a local machine that is not connected to the internet would be a good idea.

I suppose, that it's better to me, to make a fresh install of otrs and copy only tickets. Don;t you think so?

How can I copy only the tickets?

Do you mean copying only tickets from the DB and not agents and stuff? That´s no good idea as tickets rely on other tables in your DB. Lars --------------------------------------------------------------------- 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 NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW! http://www.otrs.com/en/support/enterprise-subscription/