{"action":"created","issue":{"url":"https://api.github.com/repos/bit-team/backintime/issues/9","labels_url":"https://api.github.com/repos/bit-team/backintime/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/bit-team/backintime/issues/9/comments","events_url":"https://api.github.com/repos/bit-team/backintime/issues/9/events","html_url":"https://github.com/bit-team/backintime/issues/9","id":110866225,"number":9,"title":"hardlinking doesnt work with schedule per included folder enabled","user":{"login":"Germar","id":2731999,"avatar_url":"https://avatars.githubusercontent.com/u/2731999?v=3","gravatar_id":"","url":"https://api.github.com/users/Germar","html_url":"https://github.com/Germar","followers_url":"https://api.github.com/users/Germar/followers","following_url":"https://api.github.com/users/Germar/following{/other_user}","gists_url":"https://api.github.com/users/Germar/gists{/gist_id}","starred_url":"https://api.github.com/users/Germar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Germar/subscriptions","organizations_url":"https://api.github.com/users/Germar/orgs","repos_url":"https://api.github.com/users/Germar/repos","events_url":"https://api.github.com/users/Germar/events{/privacy}","received_events_url":"https://api.github.com/users/Germar/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/bit-team/backintime/labels/Fix%20Released","name":"Fix Released","color":"ddffdd"},{"url":"https://api.github.com/repos/bit-team/backintime/labels/High","name":"High","color":"ffdddd"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":19,"created_at":"2015-10-11T16:28:49Z","updated_at":"2015-10-11T17:25:23Z","closed_at":null,"body":"Schedule per included folder is BUGGY, do NOT use it unless you want to do some debugging or if you have plenty of space (and computing power)!\n\nThe snapshots are too big, also without changing anything the snapshot size is the size of the folder, so hardlinking is not working. For the tasks with higher frequency the hardlinking fails: consuming the full space of all the folders that are scheduled for backup (also the ones with lower frequencies). The time to make the snapshot is incredibly long (exceeding 10 times the time to create a normal complete snapshot, which is logical as it recreates every single bit)\nThe lowest frequency tasks and manual backups behave normally\n\n"},"comment":{"url":"https://api.github.com/repos/bit-team/backintime/issues/comments/147223122","html_url":"https://github.com/bit-team/backintime/issues/9#issuecomment-147223122","issue_url":"https://api.github.com/repos/bit-team/backintime/issues/9","id":147223122,"user":{"login":"Germar","id":2731999,"avatar_url":"https://avatars.githubusercontent.com/u/2731999?v=3","gravatar_id":"","url":"https://api.github.com/users/Germar","html_url":"https://github.com/Germar","followers_url":"https://api.github.com/users/Germar/followers","following_url":"https://api.github.com/users/Germar/following{/other_user}","gists_url":"https://api.github.com/users/Germar/gists{/gist_id}","starred_url":"https://api.github.com/users/Germar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Germar/subscriptions","organizations_url":"https://api.github.com/users/Germar/orgs","repos_url":"https://api.github.com/users/Germar/repos","events_url":"https://api.github.com/users/Germar/events{/privacy}","received_events_url":"https://api.github.com/users/Germar/received_events","type":"User","site_admin":false},"created_at":"2015-10-11T17:25:21Z","updated_at":"2015-10-11T17:25:21Z","body":"(by borph)\nI think we have to be clear what BackInTime should be able to do and which kind of program it is..\n\nIt's nice that BiT can be run by any user, but as root you have more possibilities: you could use anacron or backup the whole system. Maybe this can be detected and BiT could behave different?\n\nShould BiT support FAT32 and be (quite) efficient on it? This would mean to have only folders in the snapshot directory, which are rsynced. But in the GUI, it's nice to see each snapshot as a full folder set, even if only one of them was rsynced. I mean a good example is: backup (almost) the whole system monthly, but a specified folder like /home/peter/documents every hour.\n\nOn FAT32, this takes a lot of space which is wasted absolutely senseless. On ext3/ext4, hardlinking solves this problem, but is still an overhead when it comes to a lot of files.\n\nIf you say goodbye to the a-snapshot-has-all-files approach, an hourly snapshot would contain only /home/peter/documents, the monthly all files and the \"latest_snapshot\" also (like I wrote under answers). But of course it can get much less convenient to look for a specific file, or a extra logic is needed to support the user. Actually, this extra logic could be a soft link! I will explain my idea:\n\nThere are more than one folder configured and they have different frequencies. Let's say \"/\" monthly and \"/home/peter/documents\" hourly.\n\nIn the backintime directory, there is a folder \"latest_snapshot\" which has always the latest status of files which got rsync'ed. Also there are the snapshots like 20090831-204000 or so. A cronjob will do like this:\n\nIf it's the monthly run, rsync including both folders mentioned using root and the \"latest_snapshot\". Then copy (cp -al) it to the snapshot (with the date in the name).\n\nIf it's the hourly run, rsync only including the \"/home/peter/documents\", also using \"latest_snapshot\". Then copy (cp -al) _this_ folder to the named snapshot.\n\nIt knows, which snapshot was with the next-lower frequency (here monthly) and does soft-links of the ignored folders into the current snapshot. Softlinks have a big disadvantage: we have to be carefull with removing snapshots! If we don't do the links, the new snapshot only contains 'documents', which is ok for me and saves space on FAT32.\n\nAbout the problem of non-disjoint folders: If the subfolder has a lower frequency, it can be excluded with \"--exclude\" and won't be rsynced. Don't do the softlinks in that case. If the subfolder has higher frequency, this shouldn't be a problem, as only the subfolder got rsynced and copied into the new snapshot.\n"}}