On Mon, Jun 02, 2003 at 01:36:12PM +0100, Wilcox, Andy wrote: > I found that you can't do a move nodedata against a copypool.
You can, but you can't move files out of one copypool into another. This is documented. > You have to > move the data from the onsite pool to another onsite pool and copy this to a > different copypool. The data in the old copypool is then inconveniently left > around (although existing copy group expiration value will apply). You are describing a different phenomenon, but it would be nice if there were a way to address this. Even a DELETE NODEDATA would be handy. :-) Although... what would happen in the following scenario: - NODE_A is backed up to primary pool PRIM01. - PRIM01 gets backed up to COPY01. - The TSM admin does a MOVE NODEDATA NODE_A FROM=PRIM01 TO=PRIM02 - After that, PRIM02 gets backed up to COPY02. - All copypool-volumes are taken offsite - A disaster strikes and the DR procedure is started. - In a new TSM server, NODE_A is being restored directly from copypool-volumes. Which volumes will the server choose? This could be relevant, since COPY01 might be noncollocated while COPY02 is collocated. This can make a large difference during DR. -- Jurjen Oskam PGP Key available at http://www.stupendous.org/
