Upgrading OTRS 3.2.2 to 3.3.x in Windows

[pushreply]

Hi,

I tried to understand the upgrade steps provided in the Youtube video (v. 2.2 to 2.4) and wrote them here:

Pre-condition:
OTRS standard installation (not manual), upgrading from 3.2.2 to 3.3.5 (or latest). All Backup (SQL and complete OTRS folder) are saved separately as ZIP file, in case the upgrade is not successful.

Backup:
0. stop services
1. backup sysconfig
2. backup otrs database:
mysql -u root -prootpassword otrs > otrs_version_date.sql
(full structure and data, or only data?)
3. backup Config.pm
4. Uninstall OTRS

Restore:
1. install new version (and not going into web installation process?)
2. copy old Config.pm from previous version
3. create user otrs (because we are not going into the web installer?)
4. mysql: create database otrs character set utf8
5. grant user otrs:
mysql -uroot -e "GRANT all ON otrs.* TO 'otrs'@'localhost' identified by 'some-pw'" && mysql -uroot -e "FLUSH PRIVILEGES"
6. restore DB dump
7. DB upgrade import *.sql
8. DB upgrade execute perl *.pl
9. DB upgrade import *-post.sql
10. Repeat steps 7-8-9 for next version
11. login root, restore sysconfig


QUESTIONS:
1. Do we have to iterate the upgrade from 3.2.2 to 3.2.3 to 3.2.4...3.2.11...3.3.1...3.3.5? Because the video does iterate the version upgrade for DB version 2.2, 2.3, 2.4.

2. On the Restore step 6 and 7-8-9: Which one come first: the 7-8th or the 6th step?

3. DB SQL Backup (sql dump): full structure and data (with drop table if exists) or only the data?

4. The steps described above is also close to this manual:
http://doc.otrs.org/3.2/en/html/upgrade ... aller.html

There is currently no in-place upgrade tool available for OTRS installations that were done with the Windows Installer. The upgrade process basically consists of backing up the database and the filesystem, uninstalling OTRS, installing the new version, restoring the database and running the upgrade procedure if needed.

(Unfortunately, this link http://faq.otrs.org/otrs/public.pl?Acti ... ItemID=351 is down.)

But:
http://doc.otrs.org/3.3/en/html/upgrade ... aller.html

"It is possible to upgrade seamlessly by downloading the new Windows Installer and running it. The installer will automatically detect the OTRS installation and perform an upgrade on it."

Which one should I follow for upgrading version 3.2.2 to 3.3.x ?
I did the automatic installation, as described in
http://doc.otrs.org/3.3/en/html/upgrade ... aller.html
but how about the Restore steps 7-8 ? Do we have to execute it?

5. I tried the automatic installation, then the Restore steps 6-7-8th, but all the tickets title on the Dashboard are not shown up. What did I do wrong?

6. In the folder OTRS\scripts, there are "DBUpdate-to-3.2.mysql.sql" and "DBUpdate-to-3.2.pl" (OTRS 3.2.2, 3.2.3 ... 3.2.11....), respectively for Version 3.3.x.
According to the manual:

"Minor upgrades (from OTRS 3.2 to OTRS 3.3) take a little more time as there is also a database upgrade step involved. The installer will detect this and will automatically perform the upgrade for you. After installation you should still perform steps 12, 13 and 14 of the 'regular' upgrading section."

Does it mean that the steps 7-8 will be covered in the "automatic upgrade" ?

7. Youtube video showed that he did not go through the web-installation process, because he create and grant the user manually, import database and so on. How about version 3.3 ?

That is all for now
Some questions are redundant. I have problem to organize the information right now because I already 4 days on upgrade process. Every help is highly appreciated. Thank you.

EDIT:
I forgot to tell you that we had the ADD-ONS "Time Accounting" and "FAQ" installed.
Then I read in this forum that after the newer version of OTRS installation, we should first login as root@localhost, install the modules AND THEN restore the database.
(which means the web-installation must have to be done first, and therefore the youtube video and the whole 'manual installation' is NOT useful in this case)
I tried to restore database before upgrading modules, but the OTRS Admin area > package manager does not respond.


Mainly, I am getting confused between upgrading after "using web-installer" or not using web-installer and do "manual upgrade" instead.

[wurzel]

Hi,

I tried to understand the upgrade steps provided in the Youtube video (v. 2.2 to 2.4) and wrote them here:

Pre-condition:
OTRS standard installation (not manual), upgrading from 3.2.2 to 3.3.5 (or latest). All Backup (SQL and complete OTRS folder) are saved separately as ZIP file, in case the upgrade is not successful.

Very good. You should not use the youtube videos (espacially the old ones) you should stick stricktly to the doc.otrs.org for your versions.

Backup:
0. stop services
1. backup sysconfig
2. backup otrs database:
mysql -u root -prootpassword otrs > otrs_version_date.sql
(full structure and data, or only data?)
3. backup Config.pm
4. Uninstall OTRS

Restore:
1. install new version (and not going into web installation process?)
2. copy old Config.pm from previous version
3. create user otrs (because we are not going into the web installer?)
4. mysql: create database otrs character set utf8
5. grant user otrs:
mysql -uroot -e "GRANT all ON otrs.* TO 'otrs'@'localhost' identified by 'some-pw'" && mysql -uroot -e "FLUSH PRIVILEGES"
6. restore DB dump
7. DB upgrade import *.sql
8. DB upgrade execute perl *.pl
9. DB upgrade import *-post.sql
10. Repeat steps 7-8-9 for next version
11. login root, restore sysconfig

Step 1 Yes without web installer
Yes. On Step2 - do not restore your Config.pm from previous, but edit the new one with your own configuration.
Step 3 - on Windows you won't need a otrs user, it is a IIS User or something. (I am not 100%ig sure)

QUESTIONS:
1. Do we have to iterate the upgrade from 3.2.2 to 3.2.3 to 3.2.4...3.2.11...3.3.1...3.3.5? Because the video does iterate the version upgrade for DB version 2.2, 2.3, 2.4.

read the documenation carefully.

2. On the Restore step 6 and 7-8-9: Which one come first: the 7-8th or the 6th step?

read the documenation carefully. It is structured correctly.

3. DB SQL Backup (sql dump): full structure and data (with drop table if exists) or only the data?

complete.

Which one should I follow for upgrading version 3.2.2 to 3.3.x ?

You should stick on the documentation if you are unsure. On the documenation of the version you are upgrading to.

But the safe way is: do the upgrading manually without the .exe upgrading.

Perhaps that'll help you.

Florian

[pushreply]

Hi Florian,

we are still using Apache - Strawberry Perl - MySQL in Windows XP, because we need to demo the system with live ticket and do the upgrade processes flawlessly.

Thank you to confirm that the youtube video is "obsolete" that helps alot

So, let us narrow down the information: use the otrs documentation.

Backup:
0. stop services
1. backup sysconfig
2. backup otrs database:
mysql -u root -prootpassword otrs > otrs_version_date.sql
(full, structure and data)
3. backup Config.pm
4. Uninstall OTRS

Restore:
1. install new version (NOT going into web installer)
2. edit the new Config.pm with my own configuration from previous version
3. create user otrs (because it is a MySQL on Windows XP)
4. MySQL: create database otrs character set utf8
5. grant user otrs:
mysql -uroot -e "GRANT all ON otrs.* TO 'otrs'@'localhost' identified by 'some-pw'" && mysql -uroot -e "FLUSH PRIVILEGES"
6. restore DB dump
7. DB upgrade import *.sql
8. DB upgrade execute perl *.pl
9. Repeat steps 7-8-9 for next version
10. login root, restore sysconfig

the last question is about upgrading the ADD-ONS..

Thank you.

[crythias]

Btw, mysqldump is for output (>) / backup
mysql is for input (<)

[pushreply]

Btw, mysqldump is for output (>) / backup
mysql is for input (<)

yes, I know

currently I am finished with editing config.pm, create user 'otrs', set host, set password.
I would like to continue to the step "restore DB dump" (addons are not installed and configured yet), but last time I did that, the package manager is not responding at all.....

[crythias]

yes, I know

:) OK. I just didn't want someone who was reading this thread to follow it verbatim because it was wrong at least 3 times.

[wurzel]

Hi,

we are still using Apache - Strawberry Perl - MySQL in Windows XP, because we need to demo the system with live ticket and do the upgrade processes flawlessly.

In this case, I would recommend just focus on the mysql database. That means:
Don't use the existing strawberry/Perl/OTRS installation.

Just Dump your database and make a backup of configuration.
And the documentation: use this steps http://doc.otrs.org/3.3/en/html/upgrading.html and adapt them for your windows.

Backup:
0. stop services
1. backup sysconfig
2. backup otrs database:
mysql -u root -prootpassword otrs > otrs_version_date.sql
(full structure and data, or only data?)
3. backup Config.pm
4. Uninstall OTRS

2: it is 'mysqldump' not just mysql
3: Backup all data mentionend in the doc.otrs.org:

Kernel/Config.pm
Kernel/Config/GenericAgent.pm
Kernel/Config/Files/ZZZAuto.pm
var/*

.. as well your own configs.

I would recommend to disconnect the existing server from network and built a complete new one with an running 3.3.x.
But this would be a different story.

Restore:
1. install new version (NOT going into web installer)
2. edit the new Config.pm with my own configuration from previous version
3. create user otrs (because it is a MySQL on Windows XP)
4. MySQL: create database otrs character set utf8
5. grant user otrs:
mysql -uroot -e "GRANT all ON otrs.* TO 'otrs'@'localhost' identified by 'some-pw'" && mysql -uroot -e "FLUSH PRIVILEGES"
6. restore DB dump
7. DB upgrade import *.sql
8. DB upgrade execute perl *.pl
9. Repeat steps 7-8-9 for next version
10. login root, restore sysconfig

3: the step 5 will create the database user. Step 3 in your steps refers to a linux otrs user. You don't need it on a windows system.
Step 10 should be done after 6.

6: restore Database
7: restore Sysconfig (ZZZAuto.pm)
8 do your upgrading scripts.

the last question is about upgrading the ADD-ONS..

If you do a correct restore (as it is described in doc.otrs.org) the Add Ons are migrated correctly.

And: I don't know why I write this...

it is all in doc.otrs.org. ALL of it!

Flo

[pushreply]

Flo, thanks

so, I have completed the upgrade.
I forgot to explain, that the installation was not really an upgrade, but rather "installing newer version and restoring old database and backup files".
I have a DB dump from version 3.2.2, and all needed backup, BUT the OTRS system is uninstalled.

What took it so long?
1. because the previous version is uninstalled (deleted from windows OS)
2. because "regular" upgrade from previous installed version (before it was uninstalled) did not get updated properly to the newer version, and the scheduler is not properly started.
3. because the windows installer is "really" easy, but I had thought that I have to execute DBUpdate-to-3.3.pl and DBUpdate-to-3.3.mysql.sql, which then display only the ticket number, other information are gone.

http://doc.otrs.org/3.3/en/html/upgrade ... aller.html
Minor upgrades (from OTRS 3.2 to OTRS 3.3) take a little more time as there is also a database upgrade step involved. The installer will detect this and will automatically perform the upgrade for you. After installation you should still perform steps 12, 13 and 14 of the 'regular' upgrading section.

According to the information above, I did not do execute DBUpdate-to-3.3.pl and DBUpdate-to-3.3.mysql.sql.
last time I did that, all tickets title are gone.

actually, if I am doing this correctly, the upgrade is very easy (in Windows, with Apache-Mysql-StrawberryPerl).
like Florian said, it's all documented in doc.otrs.com, but there are conditions have to be met! (which I did not, because I was confused with the "obsolete" information/documentation/youtube.)

The steps are:
1. reinstall 3.2.2, we need the installed version
2. use the web-installer
3. login root@localhost
4. update+install addons on admin > package-manager
5. backup/export sysconfig
6. restore db (note: This is still in version 3.2.2!)
7. backup config.pm, ZZZAuto.pm

Upgrading to 3.3.5:
8. stop services: mysql, apache, cronw
9. Install 3.3.5
10. login as admin
11. import/restore the sysconfig file
12. upgrade (not reinstall!) the addons in package-manager
13. run the upgrade script: perl OTRS\scripts\DBUpdate-to-3.3.pl
14. that is all.

Thank you for your help!

Update:

all good now.