Paul,

I did a LOT of export/import when I reorganized the data in my TSM system
after adding our LTO library.  This is what I saw.

Yes, you can export selected filespaces.  You're right, the data in TSM is
not affected automatically.\
Then delete the filespace you want gone.
When you IMPORT the data, it will use the default management class for the
importing node.  In most cases, that will point to a disk pool, so that is
where the imported data will appear.  If by any chance that disk pool
migrates back to the pool originally exported from, you will  have made a
big circle.  So plan your incoming data paths carefully.
If you do not completely delete the exported filespace - like when I
exported "backups" but left "archives" alone - the imported filespace will
be renamed.
Export/import puts a big load on the TSM log; I saw mine quickly climb to
over 60% utilization and I'm running a 4.4 GB log.
Also, I did not get full tape drive performance - I did exports/imports to
DLT 8000 which is normally 8 MB/s, but export/import throughput was around
3 MB/s.

Hope this  helps and good luck.

Tab Trepagnier
TSM Administrator
Laitram Corporation









"Seay, Paul" <seay_pd AT NAPTHEON DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
10/09/2002 10:31 PM
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        Export/Import Question Related to MGMTClasses and 
Storage Pools


I have some filespaces that have part of their files that got stored in
the
wrong storage pools, apparently because of a copy group definition error.
The question I have now is, will the following fix/do what I want.  We do
not have V5 installed, we are at 4.2.2.12.

        Export the Node (This leaves the data on the server, right?)
        Delete the broken filespace (not the whole node)
        Import the filespace that was deleted for the node

Can you even do this without deleting the whole node?

How does the IMPORT know where to stick the data?  I presume it tries to
match the management class to a management class in the node that is
defined
on the server, or does it use the information exported, essentially
putting
the data back based on the management class definitions on the export
tape.
That is OK because the policy domain is correct now.