Re: retrieving data

Hi,

I personally like using replication to have a "hot spare" of my main DB. That way if you have some bad hardware failure on the DB you at least have a working copy of the data on an already configured server.

On that replicated copy (slave as we call them here) you can make backups at your convenience since in that server you can lock all tables, make a clean copy/backup of the DB and then resume replication.

IMO, if you can afford even a small server to handle those tasks you should go for it. It's really worth it and let's you keep your valuable data in more than 1 location.

Regards,

Luis

----- Original Message ----
From: calypso <
feedback(at)epsam.com>
To: 
replication(at)lists.mysql.com
Sent: Monday, July 23, 2007 3:58:32 AM
Subject: retrieving data



Hi all,

I run a travel-agency, where most of my customers are internet users.
Lately, I experienced an increase number of online reservations through my
website. Though I use MYSQL database to store the orders and data gathered,
yet I have concerns about any possible loss of information. 

Is there any affordable solution that can prevent data loss?

Regards


-- 
View this message in context: 
http://www.nabble.com/retrieving-data-tf4128347.html#a11740038
Sent from the MySQL - Replication mailing list archive at Nabble.com.


-- 
MySQL Replication Mailing List
For list archives: 
http://lists.mysql.com/replication
To unsubscribe:    
http://lists.mysql.com/replication?unsub=al1629608@yahoo.com








       
____________________________________________________________________________________
Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games.
http://sims.yahoo.com/