Moving eGW to a different server?

Jason_Byrns 2006-09-28 18:46:58 UTC #1

Good afternoon, all!

I was just working on our primary eGroupWare server, and copying that
installation to a test server. We have a simple database module I made
using the eTemplate tool, along with the basic eTemplate tutorial.

But there is an odd thing with the migration. When I move this
installation to my test server, it comes up with the previous version of
my custom eTemplate app, and not the current version. (There were a
couple of extra fields I added, that’s about the only difference)

I migrated in what seemed like the simplest way:

Tar up /var/lib/mysql from production server
Tar up /var/www/html/egroupware from production server

3a) Stop MySQL on test server
3b) Untar /var/lib/mysql onto test server
3c) Start MySQL on test server

Untar egroupware tarball to /var/www/html/egroupware on test server

…What am I missing here? How did I somehow get a slightly older
version of the eTemplate app using this method? Is there something
obvious I should know, or what?

In other words, where does eTemplate store the templates you create?
How should those be copied from one system to another?

I’d sure appreciate any advice that can be offered! Thanks!

–Jason Byrns

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net’s Techsay panel and you’ll get the chance to share your
opinions on IT & business topics through brief surveys – and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

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

ralfbecker_dr 2006-09-28 18:52:16 UTC #2

Hi Jason,

you probably missed to make a new [dump4setup] on the old install. When
you copied the sources to the new box, the etemplate.inc.php was touch
and reloaded to the database, overwriting your current, not yet dumped
changes.

Ralf

Jason Byrns schrieb:

Good afternoon, all!

I was just working on our primary eGroupWare server, and copying that
installation to a test server. We have a simple database module I made
using the eTemplate tool, along with the basic eTemplate tutorial.

But there is an odd thing with the migration. When I move this
installation to my test server, it comes up with the previous version of
my custom eTemplate app, and not the current version. (There were a
couple of extra fields I added, that’s about the only difference)

I migrated in what seemed like the simplest way:

Tar up /var/lib/mysql from production server

Tar up /var/www/html/egroupware from production server

3a) Stop MySQL on test server
3b) Untar /var/lib/mysql onto test server
3c) Start MySQL on test server

Untar egroupware tarball to /var/www/html/egroupware on test server

…What am I missing here? How did I somehow get a slightly older
version of the eTemplate app using this method? Is there something
obvious I should know, or what?

In other words, where does eTemplate store the templates you create?
How should those be copied from one system to another?

I’d sure appreciate any advice that can be offered! Thanks!

–Jason Byrns

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net’s Techsay panel and you’ll get the chance to share your
opinions on IT & business topics through brief surveys – and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

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

–
eGroupWare Training & Support ==> http://www.egroupware-support.de
1.2 Release Offer: 250Euro for a Standard Update or Installation
including 1h Telefonsupport und ein gedrucktes deutsches Handbuch

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

Oscar_Manuel_Gomez_S 2006-09-29 09:59:59 UTC #3

Jason Byrns jason-sourceforge@microlnk.net escribió:

Good afternoon, all!

I was just working on our primary eGroupWare server, and copying that
installation to a test server. We have a simple database module I made
using the eTemplate tool, along with the basic eTemplate tutorial.

But there is an odd thing with the migration. When I move this
installation to my test server, it comes up with the previous version of
my custom eTemplate app, and not the current version. (There were a
couple of extra fields I added, that’s about the only difference)

I migrated in what seemed like the simplest way:

Setup mysql, apache, etc (out of egw scope) and have those services
started. At least, make sure the user you specified for egw db has the
necessary privileges (the db can be blank or not exist). You can find this
info in the header.inc.php. If you change it, you’ll need to enter header /
Admin later to change accordingly.

Tar up /var/lib/mysql from production server

Perform a backup from /setup. If you use LDAP, use ldap tools for backup
LDAP data (taking that you want to migrate it, too).

Tar up /var/www/html/egroupware from production server
2b) Tar up any sites (duplicates of sitemgr-site tree) you may have.

Tar up your data directory (usually /var/lib/egroupware)

Untar egroupware tarball to /var/www/html/egroupware on test server

Just add that the path is an apache setting, not a fixed one, and depends on
the operating system or distro and personal needs about how to access
egroupware. Also, make sure the webserver owns the tree. As last point, if
some core change or upgrade (for instance, higher php o mysql versions) has
taken place in the new server, you might need to enter Header / Admin to
update th0se settings before going on.

Untar data tarball to /var/lib/egroupware (and make sure the webserver
owns the files, though tar keeps ownerships).
5b) Restore additional sites accordingly, together with LDAP, if used.
Restore the last backup from /setup
Go to config in /setup and check the settings (FQDN, ip, path, etc) match
the new server needs. If the config changes here, perform a new backup so
you have a working backup for this new server.

I’d say it’s about 95% true, and enough for you to go on.

Regards.

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

Jason_Byrns 2006-09-29 13:47:49 UTC #4

you probably missed to make a new [dump4setup] on the old install.

Yes, that did it. I’m sure you aren’t surprised, but thank you!

When
you copied the sources to the new box, the etemplate.inc.php was touch
and reloaded to the database, overwriting your current, not yet dumped
changes.

I’d like to understand this better. I figured I’d get all important
information by grabbing my entire MySQL directory as well as the entire
eGroupWare directory. And yet, this was somehow not the case with
regards to eTemplate.

Where on Earth was that information being stored, if not in either the
eGroupWare folders or in the database? I mean, I get that you’re saying
the etemplate file was reloaded from the database, but again, where were
the not-yet-dumped changes being stored??

Pardon me if I sound confused, but I’m worried that my nightly backups
won’t be getting things like eTemplate changes! (I rarely make changes,
but still)

P.S. I’m still on 1.0.0.009, as I got a few weird error messages from
my eTemplate module, when I tried to move to the 1.2 series of
eGroupWare. I’ll try to follow up with questions about that later
today, as I’d still like to complete that migration.

Thanks again!

–Jason Byrns

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

Jason_Byrns 2006-09-29 13:52:07 UTC #5

Setup mysql, apache, etc (out of egw scope) and have those services
started. At least, make sure the user you specified for egw db has the
necessary privileges (the db can be blank or not exist). You can find this
info in the header.inc.php. If you change it, you’ll need to enter header /
Admin later to change accordingly.

For this test server, I just shut down MySQL on the production server
for a moment, and tarred up the entire /var/lib/mysql. That got me all
relevant databases, users, permissions, etc.

Just add that the path is an apache setting, not a fixed one, and depends on
the operating system or distro and personal needs about how to access
egroupware.

Yeah, I just follow (one) Redhat convention for using /var/www/html to
store Apache files.

Also, make sure the webserver owns the tree. As last point, if
some core change or upgrade (for instance, higher php o mysql versions) has
taken place in the new server, you might need to enter Header / Admin to
update th0se settings before going on.

Basics like proper file ownership are in my own eGW setup docs. And I
have, in the past, missed the possible need to change the header stuff
when migrating an eGW install.

5b) Restore additional sites accordingly, together with LDAP, if used.

Not using LDAP yet, but experimenting with it now. (The open-sourced
Fedora Directory Server – anyone have better suggestions than that for
LDAP?)

Restore the last backup from /setup

Since this install is still 1.0.0.009, I don’t think I have a backup
option yet.

Thanks again, guys!

–Jason Byrns

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

ralfbecker_dr 2006-09-29 16:52:10 UTC #6

Hi,

if your filesystem backup had been a real backup and not just a copy,
everything would have worked. Because you copied the
$app/setup/etemplate.inc.php file, it got a new timestamp and was
imported again into the database AND as you propably are not using
version-numbers it overwrote your newer template.

Ralf

Jason Byrns schrieb:

you probably missed to make a new [dump4setup] on the old install.

Yes, that did it. I’m sure you aren’t surprised, but thank you!

When
you copied the sources to the new box, the etemplate.inc.php was touch
and reloaded to the database, overwriting your current, not yet dumped
changes.

I’d like to understand this better. I figured I’d get all important
information by grabbing my entire MySQL directory as well as the entire
eGroupWare directory. And yet, this was somehow not the case with
regards to eTemplate.

Where on Earth was that information being stored, if not in either the
eGroupWare folders or in the database? I mean, I get that you’re saying
the etemplate file was reloaded from the database, but again, where were
the not-yet-dumped changes being stored??

Pardon me if I sound confused, but I’m worried that my nightly backups
won’t be getting things like eTemplate changes! (I rarely make changes,
but still)

P.S. I’m still on 1.0.0.009, as I got a few weird error messages from
my eTemplate module, when I tried to move to the 1.2 series of
eGroupWare. I’ll try to follow up with questions about that later
today, as I’d still like to complete that migration.

Thanks again!

–Jason Byrns

Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net’s Techsay panel and you’ll get the chance to share your
opinions on IT & business topics through brief surveys – and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

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

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