![]() Besides, this solution works on all systems, not just windows.Īnd, finally, it is also more generic, i.e. IMHO, the “exclude if folder contains file named xyz” is much more elegant and fits well in the overall approach of duplicacy of storing all information locally and transparently. So, while I would personally be fine with this, I’m not sure it’s the most elegant solution. The only problem is that its use would be counter intuitive because you would have to check “Folder is ready for archiving” to indicate the exact opposite (I’m ignoring the fact that backups are not really archives, obviously): But regardless of its intention, this actually makes it usable for the purpose of exclusion. The only way I can make sense of this is that the original idea of setting the archive bit for a folder is to say “backup this folder even when it is empty”. And, also in contrast to files, moving the folder or even adding files to it, doesn’t re-set the bit. What is strange, though, is that in contrast to how it works with files, the archive bit of folders is cleared by default. I wasn’t even aware that folders also have archive bits. So there might be some very specific use cases for using this as an exclude trigger, but it’s not what I had in mind.Īs for 2, can’t you also set the archive bit of the folder to exclude it from backup? You can manually clear it but as soon as the file is written again, it will be re-set. Moving it is apparently enough to trigger the archive bit. Well, that’s nice to hear, but I now realize that this smart idea of mine doesn’t seem to work because the way the archive bit works is that it is set (by windows) whenever the file is written. I think 1 is ok – we can add an option to the backup command which will skip files with the archive bit set (or not set?).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |