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.
Is there a way to link/map/share a drive on one ReadyNAS unit directly to another ReadyNAS unit without having a computer between the two? I run SABNZBD on one of my units and I want it to put the downloaded file in a different location depending on what the file is. In SAB, you can filter the files by user defined category.
How can I map a drive from one unit to the other to make moving files easier?
That is how I was planning on handling the file destinations. But how would I map a drive from one readynas to the other? All the drives are network sharable but I can't find a way to do it readynas to readynas.
I can create a new share but that is only for that readynas. Not pointing to another.
Again, there are three ways. Let's assume that the destination share is called TV.
If you are using your own post-processing scripts you can just copy the file to the remote TV share. You could use smbclient or (probably better) rsync directly from the post-process script. No mapping is required. You can't do this from the web UI.
The second way is to go into the NAS with SSH and create a folder on the data volume (with mkdir) and mount the remote share using the linux mount command. This is "mapping". You can't do this from the web UI either.
The third way uses the frontview backup jobs - crude but simple. If the destination share is called TV, then create a local share called TV. Move the TV stuff to the local TV share, and regularly schedule a frontview backup job to copy the files to the destination. This isn't mapping, and it requires copying. But it can be done using the web ui tools.
Are you doing this with your own post-processing scripts? If so, I think you can write those scripts to copy the files to a destination network share using smbclient (deleting the local copy when done).
If you use ssh, it is also possible to create a folder on the data volume (not a share) that you can then use as an NFS mount point for a share on the destination NAS.
Yet another approach is to create parallel shares on both NAS, and update the destination NAS reasonably often (perhaps hourly) with a frontview backup job.
That is how I was planning on handling the file destinations. But how would I map a drive from one readynas to the other? All the drives are network sharable but I can't find a way to do it readynas to readynas.
I can create a new share but that is only for that readynas. Not pointing to another.
That is how I was planning on handling the file destinations. But how would I map a drive from one readynas to the other? All the drives are network sharable but I can't find a way to do it readynas to readynas.
I can create a new share but that is only for that readynas. Not pointing to another.
Again, there are three ways. Let's assume that the destination share is called TV.
If you are using your own post-processing scripts you can just copy the file to the remote TV share. You could use smbclient or (probably better) rsync directly from the post-process script. No mapping is required. You can't do this from the web UI.
The second way is to go into the NAS with SSH and create a folder on the data volume (with mkdir) and mount the remote share using the linux mount command. This is "mapping". You can't do this from the web UI either.
The third way uses the frontview backup jobs - crude but simple. If the destination share is called TV, then create a local share called TV. Move the TV stuff to the local TV share, and regularly schedule a frontview backup job to copy the files to the destination. This isn't mapping, and it requires copying. But it can be done using the web ui tools.
Gotcha. I didn't understand exactly how you were suggesting. I wasn't aware that you can actually call rsync from sab. I'll have to look into that and then see what I can figure out.
I am able to create a mount from one NAS to the other but I must be root to do it. Once I do that, I don't have permissions to right to the mapped directory due to permissions. I've tried changing the owner and that didn't work. How would I go about making the drive map every time with a normal user?
I'm somewhat familiar with mount and fstab but a quick test didn't auto-mount like I wanted.
I am able to create a mount from one NAS to the other but I must be root to do it. Once I do that, I don't have permissions to right to the mapped directory due to permissions. I've tried changing the owner and that didn't work. How would I go about making the drive map every time with a normal user?
I'm somewhat familiar with mount and fstab but a quick test didn't auto-mount like I wanted.
This approach is trickier than just using rsync. Does the owner/group of the destination share use the same UID/GID on the source NAS? You could also try allowing guest access for the destination share.
Though I know that automount on demand is possible, I've never needed to do it.
The configuration changes for automount might not survive a firmware update, so you should make sure you archive them somewhere (and also know how to reverse them).
I tried the rsync last night and it failed. I'm at work and have slept, but I believe this is the command I used last night.
rsync -a --remove-source-files --whole-file banner.jpg //192.168.1.80/Files
And ofcourse I can't remember the error it gave, but it was something that made me think it couldn't find the other box even though I was on it in a browser window. That's why I thought about using mount.
I tried the rsync last night and it failed. I'm at work and have slept, but I believe this is the command I used last night.
rsync -a --remove-source-files --whole-file banner.jpg //192.168.1.80/Files
Not the right syntax for sure. The remote system syntax is user@ip-address:folder. The user@ is optional. You need two dashes on both remove-source-files and whole-file.
