Enrique Sanchez Vela wrote:
Chris,
Replicating for the sake of backups is in general a
bad idea, since once you delete/update a record, it
will be automatically propagated to the slave server.
Replication, should be used to provide better
availabilty/load balancing but that would need to be
setup as part of a bigger plan to provide higher
availabilty to the service that you are providing.
One thing that you could do, is to setup a replicating
slave server, freeze the replication, perform backups
(to tape/disks etc), then re-enable the replication
activity, this way you provide a non-stop service
without compromising your data availabilty.
The reason I am wanting to use it as a backup is because it is easy
automatic and I don't have to do anything once it is set up. The backup
would be in case of disk failure not data corruption. I would probably
run local backups too. The replication I was planing on doing was going
to be between 2 servers at 2 different locations, which would allow for
the best backup in case of disaster that completely destroyed one location.
--
Chris W
KE5GIX
Gift Giving Made Easy
Get the gifts you want &
give the gifts they want
One stop wish list for any gift,
from anywhere, for any occasion!
http://thewishzone.com
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
