Re: Back-up Plan for Large Database

You could do that, if you have 5.5+ Still no guarantee that the slave matches the master 100%, even says so in the manual. In my opinion, you shouldn't pull backups from the slave. YMMV. On Mon, Dec 27, 2010 at 11:14 AM, Wagner Bianchi wrote: > *You have no guarantee the data on the slave match

Re: Back-up Plan for Large Database

*You have no guarantee the data on the slave matches the master 100%.* * * Try it with *semi-synchronous* replication. Best regards. -- Wagner Bianchi 2010/12/27 Johnny Withers > Might want to check out LVM snapshots: > > > http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-bac

[NEWS]

November 29, 2010 Extended Model Design and Runtime Capabilities in LINQ to SQL Compatible ORM Solution from Devart New version of LINQ to SQL compatible ORM solution with extended functionality and advanced Model-First support and Update model from database functionality. Devar

Re: Back-up Plan for Large Database

Might want to check out LVM snapshots: http://www.mysqlperformanceblog.com/2006/08/21/using-lvm-for-mysql-backup-and-replication-setup/ Using a slave to pull backups from is something I would not do.

Re: Back-up Plan for Large Database

Hello there, ZMANDA is a good tool to extract backups from MySQL databases. But, when subject is fault tolerant and keep databases on air 24x7, you need to think about replication to have a SLAVE server as a online copy of your environment, other SLAVE servers to permit you switch among servers in

Back-up Plan for Large Database

Dear all, Back-up is the most important thing that need special attention. We have a production Mysql Server of near about 200 GB data and expect to grow @ 50 GB per month. Our application continuously writes data in Mysql tables. I followed some Links but want some more thoughts to choose b