Well, the title says it all..
I tried to research on this subject, but didn't find anything conclusive to
me.
Can somebody explain that error? If the file on destination isnt there, why
not just copy it from source, why an error?
I did a backup with rsync -aH --linkdest=/path/to/linkdir
okay, here is an update:
I tried removing the -H option on the recovery part and I dont get the error
anymore...
so the files it was complaining about were all hard links... but I still
don't get it. Am i recovering to the exact same image as when the backup was
taken? For now, all my tries were
Here is the --stats output for both with and without --hard-links option:
Without -H option (hard links treated as independent files):
Number of files: 51531
Number of files transferred: 5884
Total file size: 5610758604 bytes
Total transferred file size: 602614412 bytes
Literal data: 0 bytes
Are you really using paths such as /path/to/original, or are you
trying to simplify things, thereby perhaps removing important details?
Please show the real commands as executed, not after editing.
Only change / remove really confidential things (but make clear exactly
what). Don't change
for backup:
rsync -aH --stats --link-dest=/home/backup/lastbackup/folder1
/mnt/device/folder1 /home/backup/device/currentbackup
for recovery
rsync -aH --stats --delete /home/backup/device/currentbackup/folder1/
/mnt/device/folder1/
/mnt/device/folder1 is the nfs mountpoint
backup creates
Ok, I think I got my answer...
The errors were due to the fact that i was doing a dry-run... So some
hardlinks couldnt be recreated..because the file didnt exist on the target
system or something like that... that's just my guess...
Without the dry-run option, no errors were encountered
So
