I am not quite sure whether i understood your question.
Except for certain configurations you never needed remote storage nodes. Even if you added such licenses, you could just attach all devices to the NW server. But do you really want such configuration with respect to redundancy/load balancing ?
Today, as the servers are much more powerful, you could add much more load to the NW server, especially if you with Client Direct as these clients can use an AFTD/DDBOOST device directly. This means that you potentially could setup a scenario without remote storage nodes ... as long as you use B2D. But whether this is feasible for your environment needs a much deeper view into your configuration.
brandong08
16 Posts
0
March 13th, 2014 12:00
This would be in a pure 8.x environment. I know the networker server itself works as a storage node, but I meant extra storage nodes.
bingo.1
2.4K Posts
0
March 13th, 2014 12:00
You still have storage nodes where the devices have to be configured.
Even the backup server itself is working as a (local) storage node as well for its local attached devices.
Also do not forget that client direct is only available for NW clients running 8.0+ .
There are a bunch of other reasons but IMHO these are the most important ones.
bingo.1
2.4K Posts
1
March 13th, 2014 13:00
I am not quite sure whether i understood your question.
Except for certain configurations you never needed remote storage nodes. Even if you added such licenses, you could just attach all devices to the NW server. But do you really want such configuration with respect to redundancy/load balancing ?
Today, as the servers are much more powerful, you could add much more load to the NW server, especially if you with Client Direct as these clients can use an AFTD/DDBOOST device directly. This means that you potentially could setup a scenario without remote storage nodes ... as long as you use B2D. But whether this is feasible for your environment needs a much deeper view into your configuration.