This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
But the log says it is. I think they are being copied into Backup Pictures/Pictures because you have no trailing forward slash after the destination directory name.
You could try setting "schedule full backup" on the options page back to "never" and then try again. That won't copy over files that are already on the destination.
Giving this a go....but logically it doesn't make sense...? 🙂
Shouldn't a full backup copy everything across? And an Incremental one then only copies the things that have changed?
One other bit of info...I did, at some point (cannot recall when) move a few directories around on the source. But what I was expecting would happen (and having looked at the destination directories, believe it did) was that rsync would copy the files that were moved to their new location (as they essentially become "new" files on the source) and leave them alone in their old location on the destination (as I'm not deleting anything on the destination when it is removed from source).
The Never suggestion returned a success notification, but only took 1m6secs...checked the directories and they're still not fully sync'd 😞
Try looking in the full log zip file of both systems, and see if you can find any issues in either. Look in system.log, kernel.log, and systemd-journal.log.
What OS version are you running? There was a known bug some versions back, though this doesn't really seem to be that since it does appear to be copying at least some files.
But the log says it is. I think they are being copied into Backup Pictures/Pictures because you have no trailing forward slash after the destination directory name.
Not so much an idiot, as the lack of the trailing slash is the default and the way the backup jobs do this isn't well documented. You have to actually go in and edit the destination after creation to add the slash.
Here is why it does what it does: Say you have ThisStuff and ThatStuff directories to backup with different backup jobs. If you back them both up to Backup and it put everything at top level, it'd get all mixed in. That would be especially a problem if you have it set up to delete files in the backup that are deleted on the source -- each job would delete the files of the last. So, it backs them to Backup/ThisStuff and Backup/ThatStuff. Of course, each job doesn't know if others exist, so it always backs up to a sub-directory named after the source. A trailing slash can be added to eliminate that, but you have to expressly do it, to assure that's what you really want.
Your first backup was likely by some other means (maybe drag-and-drop), so the files and directories you currently have at top level are very old (but a lot are probably duplicates). But their presence confused you as to where the newest stuff should be.
Originals were definitely put there with rSync, but a long time ago (and I have moved things around on the source since). I must have inadvertently changed something at some point. Just glad you pointed me in the right direction 🙂
