![]() Then the new hard link should present a smaller size then the old hard link. When I delete data in that file, it becomes smaller. So a hard link presents the same size as the file it points to. Yes, I found the answer to the first question: there’s a file excluded in the settings, and its size is 2.3 Gb, which makes up for the difference. Thanx sanmig, I only read your reply just now. Only the total size of two (or more) incremental backups will be smaller than the sum of both (or all), depending on the difference in the data files.īut when you create a new backup folder (in the Settings) and take a backup the source file will be copied again into the new back up folder, requiring the same space there, too. ![]() Each hard link is a perfect pointer to one and the same file, not ‘just a link’ … think of something more bidirectionally, similar to a mirror. ![]() unixlinux/) the incremental (hard) link presents the same file size as the first file to the OS, it is the same file. Yes, the backups are incremental, but because of using Rsync (hard links, see. Otherwise original and backup must have the same size! my foxclone test images require root permission to access - unfortunately Nemo offers “Copy” but fails to do it as standard user …). In my case, when using B.I.T as normal user, there are warnings and files missing because of deficient permissions (e.g. I can not explain but suspect not all files were backed up: Compare them using Nemo and check the log (menu "View"). Package: grsync Source: grsync (1.3.0-1) Version: 1.3.0-1+b1 Installed-Size: 657 Maintainer: Martijn van Brummelen Architecture: amd64 Depends: libc6 (> 2.4), libglib2.0-0 (> 2.35.9), libgtk-3-0 (> 3.0.0), libpango-1.0-0 (> 1.14. The first is the difference between 5.5 and 3.2 GB. Since Back in Time snapshots are incremental, I would expect the first snapshot to be larger than the second? So if you restore files without Back in Time, permissions could get lost. If the backup drive does not support permissions Back in Time will restore permissions from fileinfo.bz2. ![]() They can be browsed with a normal file-browser or in Terminal which makes it possible to restore files even without Back in Time.įiles ownership, group and permissions are stored in a separate compressed plain text file ( fileinfo.bz2). Same here, original files are rw-, snapshots are r-, to protect them I guess. I think the read only is an attempt to protect the backup’s integrity, as I haven’t seen data files with rw in the backup?Īlso all attributes are stored in an extra file so one could use a NTFS destination for the backup, with full rsync it requires the ext format. I tried Timeshift to go back before the backup and now my Mint will not login. Instead of writing to SSD it seems to have backed up into the single main drive and used up the entire 1TB. Then I tried to backup root to an external SSD. rw what was -r-, it would be useless otherwise. Following instructions I installed GRSYNC and it tested good. As you wrote, at restore all the permissions are restored, e.g. ![]()
0 Comments
Leave a Reply. |