Hi, As suggested in another thread, I would like to know the reliability of the following backup scheme:
Suppose I have a subvolume of my homedirectory called @home. Now I am interested in making incremental backups of data in home I am interested in, but not everything, so I create a normal snapshot of @home called @home-w and delete the files/folders I am not interested in backing up. After that I create a readonly snapshot of @home-w called @home-r, that I sent to my target volume with btrfs send. After that is done, I do regular backups, by always going over the writeable snapshot where I remove always the same directories I am not interested and send the difference to the target volume with btrfs send -p @home-r @home-r-1| btrfs receive /path/of/target/volume. I do not like the idea of making subvolumes of all directories I am not interested in backing up. So what I would like to know now is the following: Could there be drawbacks of doing this resp. could I further optimize my backup strategy, as I experienced it takes a while for deleting large files in the writeable snapshot (What does it write there?) Could my method somehow lead to inefficiency in terms of the disk space used at the target volume (I mean, could the deleting cause a change, so that more is actually transferred as change, than in reality is?)? One last question would be: Is there a quick way I could verify the local read only snapshot used last time is the same as the one synced to the target volume last time? Thank you for your support and the great work! -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
