PostgreSQL->MySQL migration

Dear all,
we are using egw 1.0.009 on pgsql for a while. We are trying to:
-upgrade 1.0.009 on PostgreSQL to 1.2.x
-use the backup tool to generate a full backup.
-insert this backup into a fresh egw 1.2 on MySQL.

Has anyone tried this before?
Kind regards.
R.

Raul Araya

Raúl Araya Tauler raul.araya@star-group.net schrieb:

Dear all,
we are using egw 1.0.009 on pgsql for a while. We are trying to:
-upgrade 1.0.009 on PostgreSQL to 1.2.x
-use the backup tool to generate a full backup.
-insert this backup into a fresh egw 1.2 on MySQL.

It should work exatly this way.

–
Lars Kneschke
Metaways Infosystems GmbH
Pickhuben 4
20457 Hamburg
Germany

eGroupWare Training & Support ==> http://www.egroupware-support.net

E-Mail: mailto:l.kneschke@metaways.de
Web: http://www.metaways.de
Tel: +49 (0)40 317031-21
Fax: +49 (0)40 317031-81
Mobile: +49 (0)175 9304324


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642


eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users

It didn’t work for me. I need to upgrade from 1.0.009 to 1.2 and to
migrate from pgsql to mysql. Since we have 1.0.009 in a production
server, I need to test the upgrades and migration in a devel server.

Here’s a step-by-step breakdown of what I did. I think the poblems are
in the 1.0.009->1.2 upgrade, but still can’t prove it.

  1. In the production server, dump the database:
    pg_dump --no-owner --disable-triggers --data-only
    -f egroupware-data-date +%Y%m%d.sql egroupware

[code:1:323d9a0649]pg_dump --schema-only -f egroupware-schema-date +%Y%m%d.sql egroupware[/code:1:323d9a0649]
2. (In the devel server:) install egw from 1.0.007. Upgrade to
1.0.009. Had to do it this way, since I found out that if I didn’t, a
clean install fo 1.0.009 would put the wiki and other apps under
tables with ‘egw_’ prefix, and that wouldn’t let me restore the
schema and contents for the DB we have in the production server.
3. restore DB I got from the production server:

[code:1:323d9a0649]psql egroupware < egroupware-schema.sql
[/code:1:323d9a0649]

[code:1:323d9a0649]psql egroupware < egroupware-contents.sql
[/code:1:323d9a0649]
4. modify some config values so that this installation will work:

[code:1:323d9a0649]egroupware=# update phpgw_config set
config_value=’/~user/egwpostgres’ where config_app=‘phpgwapi’ and
config_name=‘webserver_url’;[/code:1:323d9a0649]

[code:1:323d9a0649]egroupware=# update phpgw_config set
config_value=’/home/user/egwpostgresfiles/’ where
config_app=‘phpgwapi’ and
config_name=‘files_dir’;[/code:1:323d9a0649]

[code:1:323d9a0649]egroupware=# update phpgw_config set
config_value=‘develserver’ where config_app=‘phpgwapi’ and
config_name=‘hostname’;[/code:1:323d9a0649]
5. upgrade from 1.0.009 to 1.2.
6. make a backup of 1.2 using the backup tool.
7. clean install of egw 1.2 on mysql DB.
8. restore backup of 1.2 on psql DB on the newly installed version on
mysql.
9. After restoring the backup, I had to modify again the values
modified in step 4.

I think that’s all. I have the following problems:
a) Trouble Ticket System: not working. In the production server we
have a working TTS configured so that all users can assign new
tickets to one user. I can see (from mysql) that the registers are
there, but cannot see all tickets in the new version.
b) Calendar: one of the users’ calendars gets all messed up. It’s an
admin user, so I suspect it has something to do with how acl
privileges are handled, either after the restoration of the DB or
after the upgrade, still have to carry out some tests though.

Your help would be greatly appreciated :wink:


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642


eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users

nubeiro wrote:

a) Trouble Ticket System: not working. In the production server we
have a working TTS configured so that all users can assign new
tickets to one user. I can see (from mysql) that the registers are
there, but cannot see all tickets in the new version.

TTS now supports ACLs, i.e. you have to grant people the right to
see the tickets.

hth,


Martin Schuster Martin.Schuster@centerpoint.eu.com
CenterPoint http://www.centerpoint.eu.com/


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642


eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users

Thanks for the info, but I had already done that on 1.0.009, and I
expected that the upgrade scripts would make all the necessary changes
so that everything would work fine.
If it is not possible to upgrade seamlessly from 1.0.009 to 1.2, then
someone should point that very clearly in the documentation, with
instructions on how to do overcome these little glitches. The user
manual is not clear about this, and the manual setup does not mention
anything about it either.
Maybe this info is already somewhere and I just could not find it? If
so, please, tell me where to find it. If it is not, I’m willing to help
and describe all the steps needed to solve the problem with ACLs and TTS.

Here’s my setup for egw:

  • I have everybody in a group named “company”.
  • The company people are divided into little groups. One of them is
    "tech support".
    In 1.0.009, I could let all users from “company” create and assign
    tickets to one person from “tech support” group.
    After the upgrade to 1.2, the person from “tech support” cannot see all
    tickets he had assigned.
    I have already enabled in the admin panel access to TTS for the
    "company" group, with read and assign rights. Then I log in as the “tech
    support” person and I cannot see all tickets.
    Any help?

Kind regards :wink:

Martin Schuster escribió:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

nubeiro wrote:

a) Trouble Ticket System: not working. In the production server we
have a working TTS configured so that all users can assign new
tickets to one user. I can see (from mysql) that the registers are
there, but cannot see all tickets in the new version.

TTS now supports ACLs, i.e. you have to grant people the right to
see the tickets.

hth,


Martin Schuster Martin.Schuster@centerpoint.eu.com
CenterPoint http://www.centerpoint.eu.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEX+0C8/HiHhT8phIRAugIAJ9gCQiuQyCaXcwodCmxW9OgccDYEgCghBnM
KTqZfiGnVyz4nXoo+i4kEzU=
=Redn
-----END PGP SIGNATURE-----


Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642


eGroupWare-users mailing list
eGroupWare-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/egroupware-users

–
Raul Araya