|
| Question: | I have been looking for a good backup or sync program for Linux and have eventually found LuckyBackUp. So after the first couple of attempts I have a question?
On a simulation run there are no error messages, but on an actual run I get lots! eg from a sync attempt;
rsync: chown "/media/KINGSTON/Notes & addresses/." failed: Operation not permitted (1) rsync: chown "/media/KINGSTON/Notes & addresses/Copy of address(2009).hjt" failed: Operation not permitted
I cannot find out what they mean or what to do about these errors (I am a Linux newbie used only to GUI progs) - and as far as I can tell the 2 folders have been synced anyway!!
| |
| | Answer: | Hello
...and welcome to the opensource community :)
The simulation not working properly is actually an "rsync" issue.
rsync, is the powerful command line tool that LB uses to perform data transfer.
Sometimes when running simulation (dry-run) mode everything might seem ok, but when performing a real run errors might appear. These errors usually have to do with file permissions or ownership.
I know its not nice to blame something else, but I cannot do much at the time being for the real/dry run differences.
As for the errors, you need to have some background on data permissions and owneships.
To make a long story short, a file/directory is owned by a user which belongs to a group. This file/directory has different permissions (read/write) for the owner, the group and all the others.
eg a file might be owned by the user luckyb, who has read/write permissions. All other users just have read permission (they cannot alter or delete the file).
These attributes are not supported by all file systems (eg ntfs or FAT).
LB, when using the default options, will maintain the owner and all file permissions when transfering data.
so, for example, if you try to backup some files from an ext3 (linux) to an ntfs directory, the files will be copied over, but you will get errors that attributes could not be transfered !!
The error you are presenting has to do with LB (rsync) not being able to maintain the owner of the file from source to destination. That might be caused due to filesystem incompatibility or because the user that runs LB (you !!) does not have enough permissions.
If you run LB in super-user mode (there should be a link at your menu) might solve this issue
I hope I helped and did not confuse you more :)
Edit answer | |
|
Back to overview
Add comment
|
