On 01/06/2011 09:44 PM, Carl Cook wrote:
On Thu 06 January 2011 12:07:17 C Anthony Risinger wrote:
as for the DB stuff, you definitely need to snapshot _before_ rsync. roughly:
) read lock and flush tables
) snapshot
) unlock tables
) mount snapshot
) rsync from snapshot
ie. the same as whats needed for LVM:
http://blog.dbadojo.com/2007/09/mysql-backups-using-lvm-snapshots.html
to get the DB file on disk consistent prior to archiving.
I'm a little alarmed by this. Running a mysql server for MythTV database. Do
these operations need to somehow be done before rsync? Or Else?
I don't understand what you're saying.
If you take a snapshot and back that up, the consistency of the data
will be the same as you would expect it to be if you just yanked the
power plug on the machine. Some databases tolerate this better than
others, depending on how you have them configured. The date will be
recoverable, but you will likely use no more than the transactions that
were in-flight when it happend.
If you just rsync the data without taking a snapshot first, the data in
your backup will likely be completely hosed and unusable unless you're
lucky and the machine was idle at the time.
Gordan
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
