MB Software Solutions General Account wrote: > I've got a couple clients who have a VFP9 app that uses a MySQL5 > database as the backend in their shop. > > What advice would you give for creating a backup strategy so that the > database is regularly backed up to an offsite location to prevent > catastrophic loss of data due to fire/robbery/etc. ? I had thought of > creating a similar database on the web and adding a column called > "ibackup" to all tables (a number that represents the backup > event...stored in a simple table where the user/datetime is stored and > that resulting record's PK is the iNumber value) and then copying from > the local to the web database, but I don't like that idea as it would > take too long and is not a simple process to create. There's no RI at > the database level and I could change it so that there were no Primary > or Candidate keys, so that option wouldn't be impossible. I just > figured there's gotta be a better way. Perhaps doing a backup > programmatically locally, then FTPing that resulting file to the web? > (...Encrypted, of course.) > > > In my VFP9-backend apps, I had always created a backup database in a > different folder and then did a COPY TO series of commands to create the > 2nd (backup) database, then zipped it with encryption with 7zip and then > FTPed it to the web.
Back when happycookers.com was still alive, I used MySQL replication. Basically, every transaction commited to the database resulted in my replicants getting updated nearly simultaneously. I'd back up the data from one of the replicants. To make this work, IIRC, you need to enable binary logging and grant proper permissions to the replicants. This can also be used to distribute load, so that your read-only client accesses can query against the more local replicated copy, while writes to the database go to the master. Google for 'mysql replication' if interested. That will probably get you what you need. This was back in MySQL 3.23 days... perhaps it is known as something else now. -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
