Be careful using nsrstage if you have cloned any of the savesets on these 
devices.

If you use the command "nsrstage -b pool -m -S ssid", then all of the existing
copies of the saveset are removed from the media database after staging has
completed. Not just the copy which was moved, but all copies including your
clones.

You must use "nsrstage -b pool -m -S ssid/cloneid" to ensure that your cloned
copies of the saveset are not removed from the media database.

On Tue, 6 May 2003 20:35:38 +0200, Itzik Meirson <imeirson AT MBI.CO DOT IL> 
wrote:
>You could use "nsrstage" after defining a pool that has as the eligible
>device the file device you want to move the savesets to.
>Itzik
>
>-----Original Message-----
>From: Robert L. Harris [mailto:Robert.L.Harris AT RDLG DOT NET]
>Sent: Tuesday, 06 May, 2003 15:11
>To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
>Subject: [Networker] Moving SSID's from one file device to another.
>
>
>I have a machine which needs a filesystem rebuild from one huge 2TB
>array to four 512GB arrays.  There is currently 1.2TB on the machine and
>I need to spread it across 3 other file devices.  I looked at nsrclone
>but it doesn't seem to give the ability to specify target devices which
>could potentially cause problems if it tried to copy to a volume
>different than I was hoping to get populated.  Is there a better way of
>doing this move?  Networker 6.1.2 on a Linux server.
>
>Robert

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=