[OSM-dev] MySQL backup
nick at nickhill.co.uk
Mon Jan 15 15:52:37 GMT 2007
What sort of overhead does LVM introduce to I/O?
We take backup snapshots for the database every Friday and Tuesday. The database
is off-line for around 4-6 minutes while this is done.
We could automate a process whereby the backup is copied to another machine then
a planet.osm made from it.
Steve, does the generation of planet files generally go smoothly, what is the
exact process you use to make planet dumps? Do you think it'll be a good idea to
automate the process on cron?
Andreas Brauchli wrote:
> i don't know if this is still an issue on osm but today i stumbled over
> this while reading freshmeat:
> mylvmbackup is a Perl script for quickly creating backups of a MySQL
> server's data files. To perform a backup, mylvmbackup obtains a read lock
> on all tables and flushes all server caches to disk, makes an LVM snapshot
> of the volume containing the MySQL data directory, and unlocks the tables
> again. The snapshot process takes only a small amount of time. When it is
> done, the server can continue normal operations while the actual file
> backup proceeds.
> could that be a viable option for backup and weekly-dump?
> you could then start the weekly dump from the backup from another box.
> dev mailing list
> dev at openstreetmap.org
More information about the dev