e-sata daisy chains of NAS devices
A few years back, we purchased a Tandberg Data NAS device, DPS 2140 to send back up jobs to from the network. It has been working wonderfully, but we have out grown it. It was decided to use it for off site storage of server and critical workstation back ups.
I replaced it with another Tandberg Data unit, this one a BizNas 408. Again, nice stuff, works well. Then the other shoe dropped.
Both devices have a variety of both USB and e-sata ports. Pictures attached for you to observe. I assumed, wrongly according to Tandberg, that I could plug one device into the other via either e-sata or USB and transfer data that way rather than Ethernet. Tandberg insists that there are two ways to accomplish this data transfer. One is with a host PC between the two units, the other, the purchase of something called an RDX drive that is hot pluggable into the 408 device.
Having two NAS devices in hand, it didn't make much sense to buy yet another piece of hardware, so I figured I'd just get the applicable cable(s) and do it that way. Simple? No. Either I am describing what I need incorrectly, or the cables do not exist. The USB ports on the units are of the "back of the PC" variety and not the "dog house" connector every other USB device has. The e-sata ports are also the same paradigm, and I'm getting quoted large prices for proprietary cables that "might" work.
Common sense dictates that these devices would not be manufactured with all these ports if indeed, (especially in the USB sense) they are useless. So what am I missing here? I was thinking just e-sata to e-sata, zoom, zoom.
As you will see in the third attachment that is the interface, (web based Debian Linux kernel), there IS a provision to manage attached disks to the 408 device.
So I guess the question is pretty simple for the hardware savvy? What kind of cable do I need to utilize e-sata to e-sata device communication as shown independent of an Ethernet connection or host PC connection as indicated by the pictures?
Frankly, it burns my britches when something that should be fairly see Spot run becomes a major pain in the patookus! Thanks...
20130711-082646.jpg
20130711-082704.jpg
external.jpg
I replaced it with another Tandberg Data unit, this one a BizNas 408. Again, nice stuff, works well. Then the other shoe dropped.
Both devices have a variety of both USB and e-sata ports. Pictures attached for you to observe. I assumed, wrongly according to Tandberg, that I could plug one device into the other via either e-sata or USB and transfer data that way rather than Ethernet. Tandberg insists that there are two ways to accomplish this data transfer. One is with a host PC between the two units, the other, the purchase of something called an RDX drive that is hot pluggable into the 408 device.
Having two NAS devices in hand, it didn't make much sense to buy yet another piece of hardware, so I figured I'd just get the applicable cable(s) and do it that way. Simple? No. Either I am describing what I need incorrectly, or the cables do not exist. The USB ports on the units are of the "back of the PC" variety and not the "dog house" connector every other USB device has. The e-sata ports are also the same paradigm, and I'm getting quoted large prices for proprietary cables that "might" work.
Common sense dictates that these devices would not be manufactured with all these ports if indeed, (especially in the USB sense) they are useless. So what am I missing here? I was thinking just e-sata to e-sata, zoom, zoom.
As you will see in the third attachment that is the interface, (web based Debian Linux kernel), there IS a provision to manage attached disks to the 408 device.
So I guess the question is pretty simple for the hardware savvy? What kind of cable do I need to utilize e-sata to e-sata device communication as shown independent of an Ethernet connection or host PC connection as indicated by the pictures?
Frankly, it burns my britches when something that should be fairly see Spot run becomes a major pain in the patookus! Thanks...
20130711-082646.jpg
20130711-082704.jpg
external.jpg
ASKER
So it is wrong of me to think that a RAID 5 NAS device should be able to communicate with a RAID 5 NAS device from the same manufacturer across the factory installed interfaces on the devices? The only differences between devices are size and age. File system and O/S are the same.
If I had a dollar every time a vendor told me the only solution was to spend more money...
If I had a dollar every time a vendor told me the only solution was to spend more money...
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
I've requested that this question be deleted for the following reason:
(Edit: Off-topic content removed - Modulus_Twelve)
(Edit: Off-topic content removed - Modulus_Twelve)
The question was answered in #39318193. These interfaces do not support target<--->target data transfer.
The question was asked and answered.
(Edit: Edited for consistency - Modulus_Twelve)
The question was asked and answered.
(Edit: Edited for consistency - Modulus_Twelve)
Put me down as a vote in support of dlethe's explanation.
Think of it this way -- just because you have two guns, it doesn't mean you can transfer bullets between the two by putting them barrel-to-barrel and pulling the trigger on one.
Think of it this way -- just because you have two guns, it doesn't mean you can transfer bullets between the two by putting them barrel-to-barrel and pulling the trigger on one.
Think of it this way. Most phones have a USB adapter. Do you expect that you could plug your phone into the NAS and then read/write to it? Same thing.
They told you it wont work. So use ethernet to do the transfer.