On 04/23/2016 08:41 PM, Tim Bishop wrote:
Does this help?
http://www.tldp.org/HOWTO/LVM-HOWTO/snapshots_backup.html
I've not tried it myself, but that's how I understand CoW filesystems
work and it's as Graham described.
Tim.
Ah. I can finally see what I've been mistaken about. What goes i
On Sat, Apr 23, 2016 at 08:03:33PM +0100, John wrote:
> On 04/23/2016 07:22 PM, Graham Percival wrote:
> > What I'm suggesting is this:
> >
> > filesystem RW -+--> (RW, run SQL, emails, etc) ---> filesystem RW
> >|--> snapshot RO --> run tarsnap --> delete snapshot
> >
> >
> > Essen
On 04/23/2016 09:17 PM, Scott Wheeler wrote:
> On Apr 23, 2016, at 9:03 PM, John wrote:
>
> You don't have to copy the whole data set -- that's the whole notion
> behind "copy-on-write". LLVM (or any copy-on-write system) only has
> to note the inode tree in the snapshot and then store the live
On Apr 23, 2016, at 9:03 PM, John wrote:
>
> But the second, it seems to me, requires a partition (or filesystem, or tree
> portion) to be copied to a large enough temporary space to hold the full
> dataset which is to be archived, before the next update can be accepted and
> the backup starte
On 04/23/2016 07:22 PM, Graham Percival wrote:
Hmm. I suspect there's two different ideas about snapshots and backups here.
I'm not an expert in this field (actually, I've never used snapshots at all!),
but it sounds like you might be doing this:
[best viewed in a fixed-width font]
filesystem
On Sat, Apr 23, 2016 at 08:50:22AM +0100, John wrote:
> I'd have thought my problem was commonplace. The machine is a
> server. It has to remain available continuously and can be updated
> at any moment. It handles, for example, SQL updates and email, I
> can't just switch it to read-only for the d
Thank you Graham and Florian,
I'd have thought my problem was commonplace. The machine is a server. It
has to remain available continuously and can be updated at any moment.
It handles, for example, SQL updates and email, I can't just switch it
to read-only for the duration of the backup.
Th
