Yes, 
you are right

the license is different for a storage node and a dedicated storage node.

A dedicated storage node can be checked on the device-resource.

For your information : 

How networker selects a volume for writing :

After a backup starts and the Networker server determines what pool the save 
set should be written to, it’s now necessary to determine what volume within 
the pool to use.

5 categories in order of priority : (each requiring the volume available on an 
appropriate storage node)

        - mounted, appendable volume from the required pool
          Not currently mounted ? Server sends an Alert “Volume not immediately 
available” and
          continues search.
        - unmounted, appendable volume from the required pool
        - unmounted, recyclable volume from the required pool
        - unmounted recyclable volume from a different pool  (disabled by 
default) 

        Now it depends if “Auto media management “ is enabled or not.
                - not enabled : volume request Is not cleared from Alerts and 
administrator
                                  must manually provide a volume
                - enabled : networker looks for 1 more category

        - unmounted, unlabeled volume (any volume without a Networker or EDM 
(EMC 
          Datamanager) label.








-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Michael Leone
Sent: Thursday, August 30, 2012 2:12 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Pool volumes with available space being ignored - why?

> Tony
> 
> Thanks for the reply.  I try and update the storage node list using 
> the
GUI:
> 
> clients->globals 2 of 2 -> Storage Nodes
> 
> I enter:
> backup-old
> nsrserverhost
> but cannot save the changes getting the following message:
> 'storage nodes' contains name of remote dedicated storage node
'backup-old'
> 
> Am I editing the list in the wrong place?  Any ideas how I can update 
> the storage node list?

A "dedicated" storage node can only backup itself, no other clients. 
Sounds like you need to look at the configuration of your storage node 
"backup-old". I don't recall offhand, but I think the license is different for 
a dedicated v non-dedicated storage node, too.