Based on what you and Tilghman have said (and I am reiterating in my own words to make sure I am understanding), the VMware snapshot is an excellent tool for things like taking a picture of your server once it is set up and ready to use in production, but not for incremental backup.
It sounds like I would want to keep a snapshot around simply to make setup easier should disaster happen but rely on a script running on a schedule to backup the daily changes. Restoration in the event of a disaster would then be a two set process: restore the snapshot then reload the data from the most recent backup. Joe Swann Education Technology Robertson County Schools On Apr 10, 2014, at 8:25 AM, Kent Perrier wrote: > You vmware snapshot may or may not be good enough to get your database back > in a consistent state. You should definitely put that mysqldump backup in > cron if you are going to use the snapshots. At my previous job we used VMWare > snaphots to back up our virtual environment. Took the snapshot, copied it off > the host (the backup agent used changed block tracking to only backup up the > stuff that was new since the last backup) and then removed the snapshot (VERY > IMPORTANT! :)). -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
