> >>    
> >>
> >
> >I usually just copy the complete DB directory from one 
> computer to another
> >one. With fast ethernet it takes around 5-10 minutes (30 
> minutes if I have
> >to backup the table where I store images). Only thing is 
> that mysql can't
> >write to the table currently being copied. But that's not 
> much of a problem,
> >since I do the copy in the wee hours of the night, when 
> almost no one uses
> >the server.
> >  
> >
> 
> 
> If you are copying the data from one computer to the other, why not 
> installing a little mysql on the backup machine and replicate to that 
> mysql? With only inserts/deletes/updates done on the replication 
> machine, there is no high load to be expected and you have an 
> up-to-date 
> copy all the time.
> 
> 


This 'manual' copy is for the drive I take home. To provide a backup in case
the office burns down or someone decides to 'remove' the server. 
Also, replication does not provide cover for human mistakes, done with
intention or just by being clueless. A "delete from table.this" is just as
devestating on both master and slave.

Going to buy this one soon:
http://www.allmediait.com/html/araid.html
Just to test out how to do an easy and complete systembackup.

Also replication does not take care of the backup needed of all the other
data and programs on the server.


erlend stromsvik

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to