I think if you do a MOVE NODEDATA to migrate data from one primary pool to another, the data in the copy pool stays intact. I don't think there is a way to expire it other than through the normal node-prompted expiration.
On 12/05/2012 11:20 AM, Ehresman,David E. wrote: > I'm running TSM 6.2.4.0 on AIX. > > How can a node have more files in the copy storagepool (nr-ofl) then in the > primary storagepool (nr-pvl)? > > tsm: ULTSM>q occ idmtest5 > > Node Name Type Filespace FSID Storage Number of Physical Logical > Name Pool Name Files Space Space > Occupied Occupied > (MB) (MB) > ---------- ---- ---------- ----- ---------- --------- --------- --------- > IDMTEST5 Bkup / 3 NR-OFL 141,877 7,498.54 6,189.31 > IDMTEST5 Bkup / 3 NR-PVL 141,877 7,498.54 6,187.91 > IDMTEST5 Bkup /boot 4 NR-OFL 70 84.64 80.92 > IDMTEST5 Bkup /boot 4 NR-PVL 70 84.64 80.91 > IDMTEST5 Bkup /u02 11 NR-OFL 45,576 7,317.32 6,744.50 > IDMTEST5 Bkup /u02 11 NR-PVL 45,575 7,315.12 6,741.28 > IDMTEST5 Bkup /u03 10 NR-OFL 8,003 1,082.73 938.76 > IDMTEST5 Bkup /u03 10 NR-PVL 8,001 1,082.20 937.93 > IDMTEST5 Bkup /u04 9 NR-OFL 55,928 38,242.34 37,251.88 > IDMTEST5 Bkup /u04 9 NR-PVL 55,865 38,242.29 37,250.60 > -- -- Skylar Thompson (skyl...@u.washington.edu) -- Genome Sciences Department, System Administrator -- Foege Building S048, (206)-685-7354 -- University of Washington School of Medicine