Wanda,
I understand your dilemma.  We are working on deploying dedup now, and are 
trying to figure this out too.  Like you, we want to have fast and slow pools, 
but we want a safety valve in case the fast pool fills up.  We haven't figured 
out how to do this, short of allocating extra space to try to ensure that a 
safety valve is never needed.

Let us know if you figure something out!

..Paul

At 12:18 AM 9/25/2012, Prather, Wanda wrote:
>Need some help understanding the mechanics here, TSM 6.3 on Windows server 
>with DEDUP.
>
>I have a TSM file pool called FASTDEDUP with deduplication on, and NEXTSTGPOOL 
>points to a second dedup filepool called SLOWDEDUP.
>DEDUPREQUIRESBACKUP is set to yes.
>
>So the first pool FASTDEDUP ran out of space, and BACKUP STGPOOL had not run, 
>so it couldn't run reclamation with dedup or migrate to SLOWDEDUP.  That I 
>understand.
>
>I tried a MOVE DATA from FASTDEDUP to SLOWDEDUP, and got ANR1534I (below).  I 
>figured out that's WAD, because the doc says move data does cause data 
>reduction, which is forbidden by DEDUPREQUIRESBACKUP until after the backup 
>stgpool has run.
>
>So then I tried a MOVE DATA from FASATDEDUP to a tapepool, and still got 
>ANR1534I.  Why is that?  I'm asking to move data that hasn't been deduped to a 
>non-dedup pool.   If this is WAD, can somebody explain the rationale?
>
>
>
>ANR1534I
>
>Process process ID skipped Num Files deduplicated files on volume Volume name 
>because copies of the files were not found.
>
>
>Wanda Prather  |  Senior Technical Specialist  | Wanda.Prather AT icfi DOT com 
> |  www.icfi.com
>ICF International  | 401 E. Pratt St, Suite 2214, Baltimore, MD 21202 | 
>410.539.1135 (o)


--
Paul Zarnowski                            Ph: 607-255-4757
CIT Infrastructure / Storage Services     Fx: 607-255-8521
719 Rhodes Hall, Ithaca, NY 14853-3801    Em: psz1 AT cornell DOT edu