Problem migrate existing Windows installations into the appliance
Moderator: crythias
Problem migrate existing Windows installations into the appliance
I have followed the instructions that are here http://otrs.github.io/doc/manual/admin/ ... ndows.html , but when I do cloneDB there are errors like the picture in the file attachment.
What's the problem to my server?
I have 2 servers : windows otrs appliance 3.3.11 migrate to appliance linux 3.3.11
rgds
What's the problem to my server?
I have 2 servers : windows otrs appliance 3.3.11 migrate to appliance linux 3.3.11
rgds
You do not have the required permissions to view the files attached to this post.
Re: Problem migrate existing Windows installations into the appliance
anyone can help me, to solve this problem?
Re: Problem migrate existing Windows installations into the appliance
Hello ardli,
I can't really help you, because I have a problem likewise yours. The same constallation: 3.3.11 on windows (MS SQL DB) migrate to 3.3.11 appliance (Postgresql) with clonedb. I spent several time to clone the database, but every time it fails.
I have already uninstalled ALL Feature Add-Ons like FAQ, MasterSlave, Support, iPhone etc.; only CloneDB is installed. And YES - everytime I drop and recreate the postgresql DB before I run cloneDB.
When cloneDB stops, the Postgresql DB has a size of 1472 MB. Is there defined a limit? Do or can I exclude anything, before I run cloneDB?
I can't really help you, because I have a problem likewise yours. The same constallation: 3.3.11 on windows (MS SQL DB) migrate to 3.3.11 appliance (Postgresql) with clonedb. I spent several time to clone the database, but every time it fails.
I have already uninstalled ALL Feature Add-Ons like FAQ, MasterSlave, Support, iPhone etc.; only CloneDB is installed. And YES - everytime I drop and recreate the postgresql DB before I run cloneDB.
When cloneDB stops, the Postgresql DB has a size of 1472 MB. Is there defined a limit? Do or can I exclude anything, before I run cloneDB?
You do not have the required permissions to view the files attached to this post.
OTRS: 4.0.8
OS: OTRS Appliance
DB: PostgreSQL
OS: OTRS Appliance
DB: PostgreSQL
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Problem migrate existing Windows installations into the appliance
Just a heads up that images are not readable or searchable.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: Problem migrate existing Windows installations into the appliance
Thanks for your reminder crythias.crythias wrote:Just a heads up that images are not readable or searchable.
So, is there any other way/best practice/manual to migrate from OTRS windows to appliance?
thx
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Problem migrate existing Windows installations into the appliance
Best practice? Don't really know. If you don't have custom code, it probably should be simple (ish):
Windows:
mysqldump otrs database
sftp sql dump to appliance
Appliance:
Load sql dump into mysql (as a new database).
Set Config.pm to point to the imported database.
upgrade versions according to docs (3.0.x -> 3.1.latest -> 3.2.latest -> 3.3.latest ->4.0.latest).
If you have changed to FileSystem storage of attachments, they'll also need to be moved as well as the files listed in Upgrading (for settings).
You'll also need to upgrade any modules.
Windows:
mysqldump otrs database
sftp sql dump to appliance
Appliance:
Load sql dump into mysql (as a new database).
Set Config.pm to point to the imported database.
upgrade versions according to docs (3.0.x -> 3.1.latest -> 3.2.latest -> 3.3.latest ->4.0.latest).
If you have changed to FileSystem storage of attachments, they'll also need to be moved as well as the files listed in Upgrading (for settings).
You'll also need to upgrade any modules.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: Problem migrate existing Windows installations into the appliance
Whether there will be no compatibility issues database structure? because otrs windows using mysql and appliance using postgre
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Problem migrate existing Windows installations into the appliance
data structure? Generally no, but mysql -> postgres is something covered outside this forum.
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
Re: Problem migrate existing Windows installations into the appliance
error when importing DB from mysql to postgre
Code: Select all
psql:dumpdb.sql:3148: FEHLER: Syntaxfehler bei »`«
LINE 1: LOCK TABLES `smime_signer_cert_relations` WRITE;
^
psql:dumpdb.sql:3151: FEHLER: Syntaxfehler bei »UNLOCK«
LINE 1: UNLOCK TABLES;
^
psql:dumpdb.sql:3157: FEHLER: Syntaxfehler bei »`«
LINE 1: DROP TABLE IF EXISTS `standard_attachment`;
^
psql:dumpdb.sql:3177: FEHLER: Syntaxfehler bei »`«
LINE 1: CREATE TABLE `standard_attachment` (
^
psql:dumpdb.sql:3184: FEHLER: Syntaxfehler bei »`«
LINE 1: LOCK TABLES `standard_attachment` WRITE;
^
psql:dumpdb.sql:3187: FEHLER: Syntaxfehler bei »UNLOCK«
LINE 1: UNLOCK TABLES;
^
psql:dumpdb.sql:3193: FEHLER: Syntaxfehler bei »`«
LINE 1: DROP TABLE IF EXISTS `standard_template`;
^
psql:dumpdb.sql:3213: FEHLER: Syntaxfehler bei »`«
LINE 1: CREATE TABLE `standard_template` (
^
psql:dumpdb.sql:3220: FEHLER: Syntaxfehler bei »`«
LINE 1: LOCK TABLES `standard_template` WRITE;