NASLite Network Attached Storage

After getting the NFS mount created on my client, I went for an rsync test drive.

I'm seeing these errors:


I'm now also seeing that the files DID transfer but have a uid/gid of 98 and that they the file permissions are set to 600, original perms on these files are 644.

Part of me using NASlite requires that file details remain intact. As best I can tell, the rsync options I used should have done this.
...........and why did the file permissions change?
Is there some way I can get the uid/gid values to be setup the same as MY linux client's files.....or do I need to change the client values??

tar/gzip your system conf files to a backup directory and then rsync that directory, all permissions will be intact when you untar.

Dude, you cant expect to set permissions on naslite. The users you have on your linux box will not be present on the nas so how do you expect to chown. That's out of context. Besides, what is the reason to preserve ownership on CD images

Everything on the nas will be UID=98/GID=98 thus avoiding permission issues. That way things are equally accessible through all protocols.

First, thanks for the reply and the concise explanation.

My reasoning for wanting to maintain permission values is due to my wanting to possibly backup more than my own documents and such. I'm interested in maybe backing up certain system config files on my boxes and would like to have the original permissions in case I can't otherwise know what they were set for.
In light of this though, I can manage with the way the NL box is going to deal with the backed-up files. It would just be 'cool' if the files owner/group and perms were maintained.

As for the CD images... I knew I should've picked a better example to post. That image was just some mudane image that I had laying around and used for a backup test. Should've known someone bring that up

In that case, use tar and move the archive to the nas. You can use something like this



Then you can ftp or rsync the archive over to the nas. People often script that and let cron launch it daily for a hands-off backup.