<p dir="ltr"></p>
<p dir="ltr">On Nov 22, 2016 9:59 AM, "Chris Fowler" <<a href="mailto:cfowler@outpostsentinel.com">cfowler@outpostsentinel.com</a>> wrote:<br>
><br>
><br>
><br>
> ________________________________<br>
>><br>
>> From: "Jim Kinney" <<a href="mailto:jim.kinney@gmail.com">jim.kinney@gmail.com</a>><br>
>> To: "Atlanta Linux Enthusiasts" <<a href="mailto:ale@ale.org">ale@ale.org</a>><br>
>> Sent: Monday, November 21, 2016 4:38:51 PM<br>
>><br>
>> Subject: Re: [ale] MySQL array based snapshot<br>
>><br>
>> This sounds to me like a LVM snapshot of the database file space.<br>
>><br>
>> <a href="http://dev.mysql.com/doc/refman/5.7/en/backup-methods.html">http://dev.mysql.com/doc/refman/5.7/en/backup-methods.html</a><br>
>><br>
>> Snapshot _IS_ a backup as long as it is copied off the original machine. Loud google mouths are not always accurate. Dump your Google search cookie and see what comes up again.<br>
>><br>
>> There is a STUN event but it's pretty short. The key that I see is to lock the DB after a flush (see link) , make the LVM snapshot, then release the lock, copy out the snapshot as a backup. The performance drag happens during the copy of the snapshot but the copy can be 'nice 20' if things are on a decent drive subsystem and drive failure is not expected to be eminent.<br>
><br>
><br>
> I don't see them doing a LVM snapshot on the guest. They'll do it on the host. Maybe they intend to do it on the guest. Maybe VMWare does it for them.<br>
></p>
<p dir="ltr">That's even easier. From inside vm, sync and lock db, vm snapshot, unlock. Copy snapshot away. Flatten vm snapshot. Vmware and Ovirt/KVM will do this. </p>
<p dir="ltr">> _______________________________________________<br>
> Ale mailing list<br>
> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
> <a href="http://mail.ale.org/mailman/listinfo/ale">http://mail.ale.org/mailman/listinfo/ale</a><br>
> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> <a href="http://mail.ale.org/mailman/listinfo">http://mail.ale.org/mailman/listinfo</a><br>
></p>