NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Mapping readynas to readynas
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?
CDitty wrote:
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.
13 Replies
Replies have been turned off for this discussion
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.
CDitty wrote:
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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
