Re: Moving data storage pool

Having to perform the work in the CLI doesn't bother me, but the lack  
of a means to do it "safely" does.   Ah well, it was just a pipe  
dream.  I have attempted to reorganize our storage to make it easier  
to deal with long term.   As a library we have a continually growing  
set of data that we need to store forever.  Volume expansion seems  
like a great thing until you need to phase out obsolete hardware.  At  
that point you need to have the resources to buy enough storage to  
hold the entire volume at one time.   To top it all, you need to have  
the time to wait for all of the data to copy.

Thanks for the responses.

David

p.s. - We do actually have a mirrored backup copy of the archive I am  
referring to.  It is simply located at a remote site, which takes even  
*longer* to copy between than a local volume to volume copy.



On Jul 14, 2009, at 12:18 PM, David S. Long wrote:

> Correct. It's not something done in the GUI but in the CLI. Apple  
> doesn't "support" shrinking a volume and concur with Charles'  
> statement that it would be tedious to do, though I have never  
> attempted it for obvious reasons.
> On Jul 14, 2009, at 8:26 AM, mathieu mauser wrote:
>
> > On 14-Jul-09, at 4:19 AM, David Michael Bryson wrote:
> >
> > > However, I am intrigued to know that it is possible to remove a  
> > > storage pool from a Volume.
> >
> > There's no official way to do this that I know, other than hacking  
> > at the config file. But I would never bother with it, trusting only  
> > the "move files to new storage / recreate Xsan volume" method  
> > instead.

Developer, MSU Digital Evolution Laboratory
http://programerror.com    ...press any key to continue.




_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xsan-Users mailing list      (Xsan-Users@xxxxxxxxxxxxxxx)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xsan-users/maillists%40codeha.us

This email sent to maillists@xxxxxxxxx