Hi, i try to learn how rsync lock files for create a backup, but.. not find any on www. some can help me and give any HOWTO or FAQ or document ? Thanks! -------------- next part -------------- HTML attachment scrubbed and removed
On Thu 08 Mar 2007, Alejandro Feij?o wrote:> Hi, i try to learn how rsync lock files for create a backup, but.. not find > any on www.rsync does not lock files. Paul Slootman
mmm and is posible corrupt data??? for example if rsync is on file called A.txt and at same time mysql is read A.txt... whats happend? is that who i dont understand. 2007/3/8, Paul Slootman <paul@debian.org>:> > On Thu 08 Mar 2007, Alejandro Feij?o wrote: > > > Hi, i try to learn how rsync lock files for create a backup, but.. not > find > > any on www. > > rsync does not lock files. > > > Paul Slootman > -- > To unsubscribe or change options: > https://lists.samba.org/mailman/listinfo/rsync > Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html >-------------- next part -------------- HTML attachment scrubbed and removed
On Thu, Mar 08, 2007 at 12:08:55PM +0100, Alejandro Feij?o wrote:
| mmm and is posible corrupt data???
|
| for example if rsync is on file called A.txt and at same time mysql is read
| A.txt... whats happend? is that who i dont understand.
It can get mixed data. The file contents could appear corrupt to another
mysql running on the target. You can use rsync to backup database files
while mysql is running to get _MOST_ of the content transferred while the
database is running. Repeat rsync until very little change happens in a
shorter run. Then shut down mysql cleanly and do a final rsync to sync
the files in a non-corrupt way. At least mysql downtime is minimal this
way.
You may also want to employ methods of backup up data from within mysql
itself on a row/column basis as transactions update things, to a live
backup mysql engine running elsewhere that can take over serving clients
should the first die. This has the advantage of a hot failover AND you
could use that backup engine to do the rsync backups from, since only it
needs to be shutdown to do the final rsync syncronization. Just be sure
the in-mysql backups know how to re-syncronize everything that was changed
while the backup mysql was briefly down for the last rsync run.
/--> rsync copy to site 2
main mysql ==> backup mysql --> rsync copy to site 3
\--> rsync copy to site 4
--
|---------------------------------------/----------------------------------|
| Phil Howard KA9WGN (ka9wgn.ham.org) / Do not send to the address below |
| first name lower case at ipal.net / spamtrap-2007-03-08-0703@ipal.net |
|------------------------------------/-------------------------------------|