NASLite Network Attached Storage

Hello,
purchased a copy of Naslite2. I have 2 servers running Linux I would like to backup to Naslite using rsync.
Problem: I cant seem to connect to the Naslite server, get Permission denied (13), error at IPC code (code 14)
Rsync is set to rear-write on naslite.
I created a folder called mailbackup on naslite.

My prior command I was using from linux to another linux backup server was:

rsync -azv -e ssh /home/ 192.168.88.4:/mailbackup

Trying the same command to the Naslite box, gets me:

Any ideas what I'm doing wrong?

I think I'm not mapping correctly somehow.

Peter

also tried:

rsync -azv -e /home/ 192.168.88.4:/Disk-0/mailbackup

still nothing

errors are: Failed to execute, permission denied....

I assume 192.168.88.4 is the NASLite-2 IP. First, if you are going to write to NASLite via rsync, make sure rsync is set to RW via the admin console. You can confirm the state using the status screens.

Next, at the client check what modules are exported by issuing the following:
rsync 192.168.88.4::

That should get you going...

Tony
Thanks for the quick reply...

Yes, naslite rsync is set to RW

Naslite is using the .4 address

From my mail server, Im trying:
rsync -azv /home/ Naslite-2/Disk-0/mailbackup

and getting error: failed, no such directory...
but I do have a mailbackup directory

Questions:

OK, nevermind, from the Mailserver [that Im trying to backup]
#rsync 192.168.88.4::

I get..
Shares All Shares READ-Write
Disk-0 Share Disk-0 (Read-Write)
Disk-1 Share Disk-1 (Read-Write
Remote Share Remote (Read-Write)
Status Share Status (read-Write)


Here's the whole error Im getting:
[root@mail samba]# rsync -azv /home/ Disk-0/mailbackup
building file list ... done
rsync: mkdir "/etc/samba/Disk-0/mailbackup" failed: No such file or directory (2)
rsync error: error in file IO (code 11) at main.c(509) [receiver=2.6.8]
rsync: connection unexpectedly closed (8 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [sender=2.6.8]
[root@mail samba]#


now what???

P


Peter

Seems like no matter what variation of rsync I type, I get some type of different error, all of which basically say I cant connect:

[root@mail /]# rsync -azv /home/ 192.168.88.4:/Disk-0/mailbackup
ssh: connect to host 192.168.88.4 port 22: Connection refused
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [sender=2.6.8]

[root@mail /]# rsync /home/ 192.168.88.4:/Disk-0/mailbackup
ssh: connect to host 192.168.88.4 port 22: Connection refused
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [sender=2.6.8]

[root@mail /]# rsync /home/ Disk-0/mailbackup
skipping directory /home/.
rsync: push_dir#3 "/Disk-0" failed: No such file or directory (2)
rsync error: errors selecting input/output files, dirs (code 3) at main.c(545) [receiver=2.6.8]
rsync: connection unexpectedly closed (8 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(463) [sender=2.6.8]

[root@mail /]# rsync 192.168.88.4::
Shares All Shares (Read/Write)
Disk-0 Share Disk-0 (Read/Write)
Disk-1 Share Disk-1 (Read/Write)
Remote Share Remote (Read/Write)
Status Share Status (Read/Write)


[root@mail /]# rsync -azv /home/ 192.168.88.4::/Disk-0/mailbackup
ERROR: The remote path must start with a module name not a /
rsync error: error starting client-server protocol (code 5) at main.c(1296) [sender=2.6.8]
[root@mail /]#

Found this on an older blog, it works, bit shouldn't I be able to rsync directly to the Naslite box without using smbfs?

P

If you are looking to use rsync over samba and not over ssh (which is faster and more secure) then you will need to mount the windows share on the linux box and then run rsync as if it was a local directory:
mount -t smbfs //ip.of.win.box/share /mnt/share
rsync -va /path/to/src /path/to/dst

This software works, but only over SMBFS from Linux.

Given that is has absolutely no security, I wont be using it in my environment.

If one day someone implements some type of security, both for drives and file transfers [ssh], I may revisit it again.

It's ok for home use, or if you dont care about security.

P

Not so pkuczyns

All you have to do is permanently mount the Naslite drives using NFS, dd a file say 30G on the remote NAS drive, mount that file as a loop device and do what you want with it.

You can format it to any file system you want, encrypt it, assign permissions that match the linux client permissions, etc. You can take a look at TrueCrypt as a possible fit.

Just kicking out some ideas.

Ok;-)
Im barely hanging onto what you're saying. We'll try it over the weekend

I may need some more help..

P