On Fri, 18 Jul 2014 13:56:58 Sam Bull wrote: > On ven, 2014-07-18 at 14:35 +1000, Russell Coker wrote: > > Ignoring directories in send/recv is done by subvol. Even if you use > > rsync it's a good idea to have different subvols for directory trees > > with different backup requirements. > > So, an inner subvol won't be backed up? If I wanted a full backup, I > would presumably get snapshots of each subvol separately, right? If you use btrfs send/recv then it won't get the inner subvol. If you use rsync then by default it goes through the entire directory tree unless you use the -x option. > > Displaying backups is an issue of backup software. It is above the > > level that BTRFS development touches. While people here can probably > > offer generic advice on backup software it's not the topic of the > > list. > > As said, I don't mind developing the software. But, is the required > information easily available? Is there a way to get a diff, something > like a list of changed/added/removed files between snapshots? Your usual diff utility will do it. I guess you could parse the output of btrfs send. > And, finally, nobody has mentioned on the possibility of merging > multiple snapshots into a single snapshot. Would this be possible, to > create a snapshot that contains the most recent version of each file > present across all of the snapshots (including files which may be > present in only one of the snapshots)? There is no btrfs functionality for that. But I'm sure you could do something with standard Unix utilities and copying files around. -- My Main Blog http://etbe.coker.com.au/ My Documents Blog http://doc.coker.com.au/ -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
