Input those commands in a file i.e:

file changesn:
-----

show name: storage nodes
. type: nsr client; storage nodes: <old storage node>
print

----

Run nsradmin against the file.

nsradmin -s <networker> -i changesn

If the 'print' output is what you expect, then append:

update storage nodes:<NEWSN>

And run nsradmin against the file again.

Michael Filio
Data Services Engineering
Rackspace Hosting



Smith, Al wrote:

Is there a way to do a mass change? Say multiple clients at one time?

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Thierry FAIDHERBE
Sent: Wednesday, December 31, 2008 10:26 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Scripting question

Hello,

You can easily achieve such a storage node change using nsradmin:

nsradmin> show name;storage nodes
nsradmin> . type:nsr client; name:<client name>;
Current query set

nsradmin> print
                        name: <test>;
               storage nodes: nsrserverhost;

nsradmin>  update storage nodes:<NEWSN>
Update? y
updated resource id .............................

nsradmin> print
                        name: <test>;
               storage nodes: NEWSN;


HTH,

Th

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Smith, Al
Sent: mercredi 31 décembre 2008 15:30
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Scripting question

Hi,
  Got a question. I need to know how to script a storage node change.

I have about 50 unique clients that point to a particular storage node.
That storage node is no longer available and I was wondering how to go about
scripting the clients to point to a new storage node.

__________________________________________________
Thanks,

Al Smith
Network and Systems Administrator
Hewlett Packard Certified Systems

Administrator Red Hat Certified Technician

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type
"signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or via RSS at
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is 
prohibited.
If you receive this transmission in error, please notify us immediately by 
e-mail
at abuse AT rackspace DOT com, and delete the original message.
Your cooperation is appreciated.

To sign off this list, send email to listserv AT listserv.temple DOT edu and type 
"signoff networker" in the body of the email. Please write to networker-request 
AT listserv.temple DOT edu if you have any problems with this list. You can access the 
archives at http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER