Moving to new server instance [SOLVED]

[nbacon]

We are currently running OTRS 3.1.6 in production, and have been for several years. Recently, we began researching ITSM and thus, have a different instance of OTRS/ITSM running in which we want to migrate to. I am trying to come up with the best/safest plan to do this. I have upgraded our new instance to OTRS 3.2.9 and ITSM 3.2.7 and made several configuration changes to it, on the ITSM side that I want to keep in place (Change templates, state changes, etc). How can I get all of the ticket data off of the existing OTRS instance and moved safely onto the new instance?

I had planned on upgrading our current instance from 3.1.6 to 3.2.9, so that they are at the same level. After that point, I'm looking for pointers.

Any help would be much appreciated.

[nbacon]

I did actually find this post in the lists...............

http://lists.otrs.org/pipermail/otrs/20 ... 39466.html

This may answer all my questions, except:

4) Schedule an outage of the old OTRS server, shut it down and take a backup of the database.

****after backing up the database, where are the database files located?

5) Import the database backup into the new OTRS machine

*****how do I import these files into the new instance database (commands)?

I'm sure I will answer these questions with further research of MySQL.

Thanks

[nbacon]

If I copy the database from our old (existing) server into the new instance.....will all of the changes that I made to ITSM in the new instance be wiped or will they coincide?

[crythias]

****after backing up the database, where are the database files located?

if you use mysqldump, they tend to be in the current folder or the one you specify.

*****how do I import these files into the new instance database (commands)?

you should read up on database backup and restore from MySQL.

[nbacon]

Hello and thanks for the response. Would you foresee any problems with exporting ONLY the tables with ticket data from the old instance and importing them into the new instance?

Would it work to import the below tables only?

| ticket |
| ticket_flag |
| ticket_history |
| ticket_history_type |
| ticket_index |
| ticket_lock_index |
| ticket_lock_type |
| ticket_loop_protection |
| ticket_priority |
| ticket_state |
| ticket_state_type |
| ticket_type |
| ticket_watcher |

[jojo]

no, you need the full database

[nbacon]

Ok, thanks. I guess what I'll have to do is update the current OTRS to 3.2.9, then install ITSM. Then backup that database as per the instructions and move everything over and import to the new instance (which will wipe out all of my modifications). Then manually recreate the templates, custom text fields, ldap setup, modified email notifications and event notifications. What a headache. Or is there an easier way to move ticket history from one system to another?