]
Subject: Re: Copy Pool expiration conundrum
>I tried this once, and the 'move nodedata' processes terminated
immediately,
>reporting successful completion but not moving any data. It turns out
that
>'move nodedata' for copy storage pools requires mounting the copy
storage
>I tried this once, and the 'move nodedata' processes terminated immediately,
>reporting successful completion but not moving any data. It turns out that
>'move nodedata' for copy storage pools requires mounting the copy storage
>pool volumes containing the data to be moved; it will not obtain inpu
> Copy Storage Pool, delete node data You cannot directly delete a node's
data
>
> from a copy storage pool; but you
can
> circuitously effect it by using MOVe
> NODEdata to s
...
>However, on some nodes I've used the move nodedata thinking that as
>primary pools were backed up to copy pools and data was no longer
>present in the primary the copy pool data would expire, but this has not
>been the case.
...
Jim - Copy storage pools are tenacious... which is to say that t
So, I had been eagerly awaiting the move nodedata capabilities in 5.x
(5.1.7.3 in our case) to facilitate a migration of data from 3490
storage pools to 3590 storage pools. I have reassigned a number of
clients to some new policy domains and ran as many scheduled selective
backups as I could, all w
