[horde] Backing up horde databases

Aaron Segura Aaron.Segura at cabelas.com
Fri Dec 15 08:35:38 PST 2006

When I said "Running" database, I meant one where mysqld is running.

I'm not sure of the results if nobody is accessing it at the time,
though, as I'm not that much of a MySQL guru.  Try it and let me know
how it works out for you :)

-----Original Message-----
From: horde-bounces at lists.horde.org
[mailto:horde-bounces at lists.horde.org] On Behalf Of Eric
Sent: Friday, December 15, 2006 7:59 AM
To: horde at lists.horde.org
Subject: Re: [horde] Backing up horde databases

At 04:05 PM 12/14/2006, Aaron Segura wrote:

<AS>>>>>I should say, "Tarring up the raw files from a *running* 
database will only cause you to cry when/if you try to restore"<<<<<

Good morning, Aaron.

I have called up the link you provided and also am looking over the 
mysqldump man page.  Doesn't seem too hard.  :-)

Just to clarify one thing, though ... Does a "running" database imply 
that someone is accessing the database, or is a database "running" 
whenever mysqld is running, whether or not anyone is accessing it?

In other words, if I used the tarball method, and had a means for 
preventing access, would I still need to shut down mysqld first?

This is all somewhat hypothetical now that you've shown me the 
"right" way :-) but I was just curious what constitutes a "running"


Horde mailing list - Join the hunt: http://horde.org/bounties/#horde
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: horde-unsubscribe at lists.horde.org

More information about the horde mailing list