Release 0.5

• Keep old local snapper snapshots after backup is complete. Number algorithm is used for cleaning, and the description is such that a user can manually remove if desired.
• Make libnotify optional.
• Remote backup fixes (#58).
• Use readline to read stdin (#60).
• Detect if backup destination already exists (#54).
• Use subvolid of mounted btrfs disk, since a single disk can have multiple subvolumes mounted. This breaks current usage and causes snap-sync to skip over past backups. The subvolid is now output when snap-sync is run.

Users will need to manually add subvolid to the user data of snapper snapshots in order to not have a full backup run again. For example, if your last backup has the following line:

# snapper -c root list | grep "latest incremental backup"
single | 1319 |       | Fri 25 May 2018 02:42:16 PM EDT | root |          | latest incremental backup                                                   | backupdir=E5-575, uuid=7360922b-c916-4d9f-a670-67fe0b91143c

You need to modify it such that it has the subvolume id, keeping the rest of the entry the same:

# snapper -c  root modify -u "subvolid=5" 1319

Now the entry should be:

single | 1319 |       | Fri 25 May 2018 02:42:16 PM EDT | root |          | latest incremental backup                                                   | backupdir=E5-575, subvolid=5, uuid=7360922b-c916-4d9f-a670-67fe0b91143c

To get the subvolume id of your backup disk, mount the disk (for example to /mnt) and then do:

# btrfs subvolume show /mnt | awk '/Subvolume ID:/ { print $3 }'

Most likely if you are not specifying the subvolume or subvolume id when you mount the disk, it will be 5, which is the top level subvolume for the filesystem.