The mailing list for listmasters using Sympa

["Nagel, Reinhold" <address@concealed>]

Hi *,

I use this command to make a backup of the database (of course you should
use your own password there):
/usr/bin/mysqldump -u root --password=<passwd> --databases sympa --opt
--quote-names --allow-keywords --extended-insert=FALSE
--default-character-set=latin1 > /home/sympa/etc/dbsympa.sql

It gives me a file that I can look at in a text editor if I want to.

The backup consists of the following commands:
mysql -u root -p<passwd> --execute="drop database sympa;" 
mysql -u root -p<passwd> --execute="create database sympa;" 
mysql -u root -p<passwd> --database=sympa < /home/sympa/etc/dbsympa.sql

Hope that helps

Reinhold

-----Ursprüngliche Nachricht-----
Von: address@concealed [mailto:address@concealed] Im
Auftrag von Paul Nuffer
Gesendet: Montag, 19. Juli 2010 17:07
An: address@concealed
Betreff: Re: [sympa-users] Backing up a sympa server

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

Hi Tim,

The tool mysqldump does what you specify:
http://dev.mysql.com/doc/refman/5.0/en/mysqldump.html

To Pat: your method to copy /var/lib/mysql/sympa would work as well, but
mysqldump would put your database in a format that's more easily
recoverable between different versions of MySQL. I would recommend
looking into mysqldump for your DB backup needs.

This section of the MySQL manual may be helpful for this topic:
http://dev.mysql.com/doc/refman/5.0/en/backup-and-recovery.html

Hope that helps!

Paul

Tim Kuehn wrote:
> There should be a way to dump the sql data in an form that'll
> automagically create a file which'll create the target tables and load
> the pertinent data when it's run. I use 'Webmin" sql db backup tool
> for that and it works great. I also recommend webmin for making the
> overall administration process a lot easier.
> 
> Tim Kuehn
> 
> On Mon, Jul 19, 2010 at 9:41 AM, Allen, Pat <address@concealed> wrote:
>> Hi everyone,
>>
>>
>>
>> Here’s something that I can’t seem to find in the archive anywhere. I run
>> Sympa (6.0.3) in my office where nightly backups are not an issue. But I
>> also run it at home on my home network for a few non-profit mailing
lists.
>> There I’m running it in a VMware VM under Centos 5.5. I really want to
rsync
>> the important information off that VM to another system so that I have
some
>> basic backups. If something terrible happens with the VM then I think I
>> should be able to create a new VM, install the OS, install Sympa, and
then
>> copy the relevant information back from my backup. (Please correct me if
I’m
>> wrong there.) I’ll also take occasional backups of the entire VM but
that’s
>> not feasible on a nightly basis.
>>
>>
>>
>> Assuming that I can shut down the Sympa and mysql processes in the middle
of
>> the night to get a consistent state of the system, can somebody tell me
>> exactly what needs to be copied in the rsync process? There’s /home/sympa
>> for sure and the two files in /etc (sympa.conf and wwsympa.conf). But
what
>> about the mysql stuff? Would I be safe in just copying
/var/lib/mysql/sympa
>> or do I need more than that?
>>
>>
>>
>> Thanks!
>>
>> Pat
> 

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkxEagkACgkQGSnk2uvWQRdEzACbBVSD/DCQlI1nZrBlSYaFfphD
kssAn2fr3vdqlh+0sONRY1qVHHUEwse5
=+9fT
-----END PGP SIGNATURE-----

Attachment: smime.p7s
Description: S/MIME cryptographic signature