Wanda,

Yes, that will, with the exception that if archives are retained after the
export, they will "lock" the filespace name.  I am going through such a
evolution right now, and that is what happened with a node whose backup
data was exported, deleted, and imported; but whose archive data was never
touched.  I ended up with a "\d$" and a "\d1" both of which contain real
data.

Tab Trepagnier
TSM administrator
Laitram Corporation







"Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU>@VM.MARIST.EDU> on 11/14/2001
11:46:30 AM

Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>

Sent by:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To:   ADSM-L AT VM.MARIST DOT EDU
cc:
Subject:  Re: Need to move old/misdirected backups of a filespace from one
      tape storage pool to another


But that won't get rid of the COPYPOOL copies, will it?  Relocating the
primary copy of backups from one primary pool to another doesn't affect the
copies already in the copy pool.

What about this:


1) EXPORT the node, by filespace if you want, specify FILEDATA=YES.
2) DELETE the filespaces.  That eliminates both the primary copy and the
COPYPOOL copies.  Careful to specify TYPE so that you delete only the
BACKUP
data if these nodes also have archive data.
3) IMPORT the node again, specify a DOMAIN with all the same management
classes as the original, but all pointing to the proper pool.

Will that do it?