- This topic has 2 replies, 2 voices, and was last updated 11 years, 8 months ago by
.
Viewing 3 posts - 1 through 3 (of 3 total)
Viewing 3 posts - 1 through 3 (of 3 total)
- You must be logged in to reply to this topic.
vinz.
vinzas far as I could see on my own databases, using mysqldump to backup a database or table will write-protects it during action.
Better ways to backup a big database are filesystem snapshot or volume manager snapshot (if you can use them)
or the program XtraBackup which does non-locking backups for InnoDB storage.
I found it referenced here:
https://en.wikipedia.org/wiki/MySQL#BACKUP
You could also replicate the database to another host and backup this.
Vinz
uRADMonitorMost likely when the cron called mysqldump backup script runs, some of the new entries are lost.
My plan was to archieve the old data periodically and keep a smaller DB on the run. This would have helped the backup process as well, yet some time would still have been used.
I will look on the alternatives you’ve indicated.
Thanks!
vinzthat’s it; what I wanted to say:
You must not use mysqldump for big production databases.
One way would be, to master-slave replicate the DB and dump the copy:
https://dev.mysql.com/doc/refman/5.0/en/replication-howto.html
Other way, the one I’d investigate in, would be XtraBackup.
Btw. Radu, could you install vim, screen and htop on the dev-server? This would enlighten my commandline-feeling.