Skip to contentSkip to conversation

'snapshot' target still experimental :-(

linux-lvm Kevin P. Fleming 4 participants 5 messages Feb 1, 2006

lore
Share & tools
lore
#0 lore raw

I noticed that this is still the case... but I want to use it :-)

I need to set up simple snapshot/rsync backups of XFS filesystems, so I'm wondering what the current thinking in the community is. Is it reliable enough to trust not to crash my server or do other nasty things?

#1 lore raw
Quoted 11 lines · Kevin P. Fleming

I noticed that this is still the case... but I want to use it :-)

I need to set up simple snapshot/rsync backups of XFS filesystems, so I'm wondering what the current thinking in the community is. Is it reliable enough to trust not to crash my server or do other nasty things?

_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/

I've been doing my home backups via rsync to an xfs via cron, and using rsync from whatever (mostly ext3 and UFS) to ext3 for one-off backups prior to making large administrative changes to systems. It seems to be working well so far, and also seems to give a very nice combination of single-file recovery ease and disaster recovery ease, which isn't astonishingly common.

It just maintains a series of hardlink trees, so any time a file is deleted or added, the actual disk usage increase is only due to the changes.

And, every backup after the first is both a fullsave and an incremental in a sense - but the network usage is far, far less than your typical fullsave.

http://dcs.nac.uci.edu/~strombrg/Backup.remote.html

#2 lore raw
Quoted 3 lines · Dan Stromberg

It just maintains a series of hardlink trees, so any time a file is deleted or added, the actual disk usage increase is only due to the changes.

Yes, this is quite a popular technique. To be clear though, a change in a file does not consume just the amount of the change in the file on the backup target, but it consumes the entire size of the new file. A not-so-insignificant amount for very large files. This is where a (block level or filesystem level) snapshotting scheme would excel as it would likely only consume an amount of space rounded up to the next "unit" size more even for changes within a file.

Indeed (and to keep quite on topic), perhaps rather than hardlink trees, LVM snapshots would be even more space efficient. Maybe that is what this thread has been about. I just jumped in. Apologies if it was.

b.

Signature · 3 lines
My other computer is your Microsoft Windows server.

Brian J. Murrell
#3 lore raw
Quoted 3 lines · Brian J. Murrell

Indeed (and to keep quite on topic), perhaps rather than hardlink trees, LVM snapshots would be even more space efficient. Maybe that is what this thread has been about. I just jumped in. Apologies if it was.

No, I'm using snapshots to make rsync backups onto removable drives (so the hardlink tree method won't work for me either).

#4 lore raw
In reply to Brian J. Murrell
Quoted 5 lines · Brian J. Murrell
Quoted 3 lines · Dan Stromberg

It just maintains a series of hardlink trees, so any time a file is deleted or added, the actual disk usage increase is only due to the changes.

Quoted 7 lines

Yes, this is quite a popular technique. To be clear though, a change in a file does not consume just the amount of the change in the file on the backup target, but it consumes the entire size of the new file. A not-so-insignificant amount for very large files. This is where a (block level or filesystem level) snapshotting scheme would excel as it would likely only consume an amount of space rounded up to the next "unit" size more even for changes within a file.

it depends.

assume u have a huge text file. u change 1 char, the snapshot is useful. u add one line at the beginning, the snapshot is useless here.

the offset shift.

some delta tech will be useful here.

Quoted 12 lines

Indeed (and to keep quite on topic), perhaps rather than hardlink trees, LVM snapshots would be even more space efficient. Maybe that is what this thread has been about. I just jumped in. Apologies if it was.

b.

_______________________________________________
linux-lvm mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/