from 2.2.3 to a new 3.0.2
Moderator: crythias
-
- Znuny newbie
- Posts: 9
- Joined: 24 Nov 2010, 10:09
- Znuny Version: 3
- Real Name: Nicola
- Location: Europa
from 2.2.3 to a new 3.0.2
I'm trying to subsitute my old slackware 2.2.3 OTRS+FAQ server to a new Debian 5.0.6 with last release of OTRS on another computer.
Which is the correct procedure?
I would conserve only the historical database, I'll make the configuration ex-novo
Best regards,
TIA
Which is the correct procedure?
I would conserve only the historical database, I'll make the configuration ex-novo
Best regards,
TIA
-
- Znuny ninja
- Posts: 1029
- Joined: 13 Apr 2009, 12:26
- Znuny Version: 6.0.13
- Real Name: Wolfgang Fürtbauer
- Company: PBS Logitek GmbH
- Location: Pinsdorf
Re: from 2.2.3 to a new 3.0.2
Well, the UPGRADE document from the source tree explains what to do
Produktiv:
OTRS 6.0.13/ ITSM 6.0.13
OS: SUSE Linux (SLES 12, Leap), MySql 5.5.x, 5.6.x
Windows 2012 AD Integration (agents and customers), Nagios integration (incidents, CMDB), Survey, TimeAccounting
OTRS 6.0.13/ ITSM 6.0.13
OS: SUSE Linux (SLES 12, Leap), MySql 5.5.x, 5.6.x
Windows 2012 AD Integration (agents and customers), Nagios integration (incidents, CMDB), Survey, TimeAccounting
-
- Znuny newbie
- Posts: 9
- Joined: 24 Nov 2010, 10:09
- Znuny Version: 3
- Real Name: Nicola
- Location: Europa
Re: from 2.2.3 to a new 3.0.2
Thanks to the quick answer.
I red that,
but when I did it I already have tried backup/restore procedure that fails.
I asked the question because I don't know the correct procedure to backup database, that UPGRADING doesn't explain at all.
The db is MYSQL.
Can I use mysqldump for example?
TIA
I red that,
but when I did it I already have tried backup/restore procedure that fails.
I asked the question because I don't know the correct procedure to backup database, that UPGRADING doesn't explain at all.
The db is MYSQL.
Can I use mysqldump for example?
TIA
-
- Znuny ninja
- Posts: 1029
- Joined: 13 Apr 2009, 12:26
- Znuny Version: 6.0.13
- Real Name: Wolfgang Fürtbauer
- Company: PBS Logitek GmbH
- Location: Pinsdorf
Re: from 2.2.3 to a new 3.0.2
sure! mysqldump otrs > /somepath/somefile
then run the UPGRADE procedure and if anything fails restore
another way is to run the <OTRSHOME>/bin/backup.pl before upgrading, which saves everything
also it would be a good idea to my mind to export the config via the Admin area
then run the UPGRADE procedure and if anything fails restore
another way is to run the <OTRSHOME>/bin/backup.pl before upgrading, which saves everything
also it would be a good idea to my mind to export the config via the Admin area
Produktiv:
OTRS 6.0.13/ ITSM 6.0.13
OS: SUSE Linux (SLES 12, Leap), MySql 5.5.x, 5.6.x
Windows 2012 AD Integration (agents and customers), Nagios integration (incidents, CMDB), Survey, TimeAccounting
OTRS 6.0.13/ ITSM 6.0.13
OS: SUSE Linux (SLES 12, Leap), MySql 5.5.x, 5.6.x
Windows 2012 AD Integration (agents and customers), Nagios integration (incidents, CMDB), Survey, TimeAccounting
-
- Znuny newbie
- Posts: 9
- Joined: 24 Nov 2010, 10:09
- Znuny Version: 3
- Real Name: Nicola
- Location: Europa
Re: from 2.2.3 to a new 3.0.2
I already created new db ver 3.
Btw I'm not so confident in MySQL so I dumped this one also and dropped it:
mysqladmin drop otrs -p
So in the old server:
mysqldump --opt --database otrs > /backups/otrs2_dump_db.sql -u root -p
(--database is for inserting instructions to create the db)
In the new I wil do:
mysql < otrs -u root -p
Then I will run the UPGRADE procedure.
Is that correct?
TIA
Btw I'm not so confident in MySQL so I dumped this one also and dropped it:
mysqladmin drop otrs -p
So in the old server:
mysqldump --opt --database otrs > /backups/otrs2_dump_db.sql -u root -p
(--database is for inserting instructions to create the db)
In the new I wil do:
mysql < otrs -u root -p
Then I will run the UPGRADE procedure.
Is that correct?
TIA
-
- Znuny newbie
- Posts: 9
- Joined: 24 Nov 2010, 10:09
- Znuny Version: 3
- Real Name: Nicola
- Location: Europa
Re: from 2.2.3 to a new 3.0.2
Ni-Cola wrote:
In the new I wil do:
mysql < otrs -u root -p
Then I will run the UPGRADE procedure.
I had to write:
mysql < /pathto/backup/otrs2_dump_db.sql -u root -p
-
- Znuny ninja
- Posts: 1029
- Joined: 13 Apr 2009, 12:26
- Znuny Version: 6.0.13
- Real Name: Wolfgang Fürtbauer
- Company: PBS Logitek GmbH
- Location: Pinsdorf
Re: from 2.2.3 to a new 3.0.2
actually: noIs that correct?

backup is correct
then UPGRADE
no need to restore if everything goes well
Produktiv:
OTRS 6.0.13/ ITSM 6.0.13
OS: SUSE Linux (SLES 12, Leap), MySql 5.5.x, 5.6.x
Windows 2012 AD Integration (agents and customers), Nagios integration (incidents, CMDB), Survey, TimeAccounting
OTRS 6.0.13/ ITSM 6.0.13
OS: SUSE Linux (SLES 12, Leap), MySql 5.5.x, 5.6.x
Windows 2012 AD Integration (agents and customers), Nagios integration (incidents, CMDB), Survey, TimeAccounting
-
- Znuny newbie
- Posts: 9
- Joined: 24 Nov 2010, 10:09
- Znuny Version: 3
- Real Name: Nicola
- Location: Europa
Re: from 2.2.3 to a new 3.0.2
Sorry if I wasn't so clear.
I'm passing from a physical server to another physical server!
So how I pass the db from the old one to the newest?
TIA
I'm passing from a physical server to another physical server!
So how I pass the db from the old one to the newest?
TIA
-
- Znuny ninja
- Posts: 1029
- Joined: 13 Apr 2009, 12:26
- Znuny Version: 6.0.13
- Real Name: Wolfgang Fürtbauer
- Company: PBS Logitek GmbH
- Location: Pinsdorf
Re: from 2.2.3 to a new 3.0.2
in this case i would do it as follows
- <OTRS_HOME>/scripts/backup.pl
bring this file to new machine
- <OTRS_HOME>/scripts/restore.pl
(run both commands with -h to get parameter options for outfile, ....)
after restore, you will endup with an "old" OTRS on the new machine
run the fully UPGRADE procedure and you will end up with new OTRS and data from old system
Hope this helps
- <OTRS_HOME>/scripts/backup.pl
bring this file to new machine
- <OTRS_HOME>/scripts/restore.pl
(run both commands with -h to get parameter options for outfile, ....)
after restore, you will endup with an "old" OTRS on the new machine
run the fully UPGRADE procedure and you will end up with new OTRS and data from old system

Hope this helps
Produktiv:
OTRS 6.0.13/ ITSM 6.0.13
OS: SUSE Linux (SLES 12, Leap), MySql 5.5.x, 5.6.x
Windows 2012 AD Integration (agents and customers), Nagios integration (incidents, CMDB), Survey, TimeAccounting
OTRS 6.0.13/ ITSM 6.0.13
OS: SUSE Linux (SLES 12, Leap), MySql 5.5.x, 5.6.x
Windows 2012 AD Integration (agents and customers), Nagios integration (incidents, CMDB), Survey, TimeAccounting
-
- Znuny newbie
- Posts: 9
- Joined: 24 Nov 2010, 10:09
- Znuny Version: 3
- Real Name: Nicola
- Location: Europa
Re: from 2.2.3 to a new 3.0.2
In the new one in which otrs database was already present I'm doing
mysqladmin -u root -p drop otrs
mysqladmin -u root -p create otrs
/opt/otrs/scripts/restore.pl -b /pathto/date/ -d /opt/otrs
I'm searching to restore db only.
Then upgrade
mysqladmin -u root -p drop otrs
mysqladmin -u root -p create otrs
/opt/otrs/scripts/restore.pl -b /pathto/date/ -d /opt/otrs
I'm searching to restore db only.
Then upgrade