This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| encrypted_backups_to_the_cloud [15.08.2017 08:01] – [the script] Pascal Suter | encrypted_backups_to_the_cloud [15.08.2017 08:44] (current) – [the script] Pascal Suter |
|---|
| </code> | </code> |
| === Known Issues === | === Known Issues === |
| For some reason gocryptfs seems to generate some files like '' gocryptfs.longname.Cnv-KyJz-BTOGdV96qyc17DKcLWvWW6Yl6xPFwzOgvc.name'' that are there when rsync scans the directory but disappear once rsync wants to sync them. this leads to rsync complaining about vanished files. however, if I mount the encrypted backup and run an rsync --dry-run to verify the completeness of the backup it finds no missing files, so all is fine. So far i'll just live with that. the script accepts exit code 24 (vanished files) as successful ending of rsync. | For some reason gocryptfs seems to generate some files (two in my case) like '' gocryptfs.longname.*.name'' that are there when rsync scans the directory but vanish before rsync can sync them. this leads to rsync complaining about vanished files. when i mount the backup with gocryptfs (forward) and then compare the unencrypted backup with the original through rsync --dry-run i find a single file to be missing in my encrypted backup. It has a very long filename: ''xxxx/xxxx/vlc-shares/public/images/fsthumbs/thumbs/MjovVFYvQWxhcm0gZnVyIENvYnJhIDExIC0gRGllIEF1dG9iYWhucG9saXplaSAtIFNlYXNvbiAxLTEyL0NvYnJhIDExIFN0YWZmZWwgMDEvQ29icmEgMTEgUzAxIEUwMDYgKERlciBBbHRlIHVuZCBkZXIgSnVuZ2UpLmF2aQ==.jpg''. the script accepts exit code 24 (vanished files) as successful ending of rsync for now until I have time to further investigate and either file a bug at gocryptfs or work around it somehow. |
| |
| ===== Restoring Files ===== | ===== Restoring Files ===== |