I may be wrong but from reading the 7.1.3 doco new container approach combined 
with the inline dedup eliminate the need for some of these processes. Also, 
where traditionally a "copy" storage pool was used they now refer to it as a 
"protect" storage pool which has the ability to be replicated to another 
"onsite" or "offsite" container storage pool.

Remember that with deduplicated data many of the processes you mentioned 
required that the data be rehydrated to be performed. An added benefit is if in 
fact these processes are no longer required it will free up system resources 
and as a result lower storage costs and increase scalability.

Fortunately, there are some good resources for additional information:
IBM you tube channel: https://www.youtube.com/channel/UCGkjRNkO0AQNyQbWhS1tTzw 
IBM knowledge center for 7.1.3: 
http://www-01.ibm.com/support/knowledgecenter/SSGSG7_7.1.3/tsm/welcome.html 

I will be installing it on two systems today to begin testing, hopefully I'll 
be able to comment more soon......


-Rick Adamson
 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
James Thorne
Sent: Wednesday, September 16, 2015 5:41 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TSM 7.1.3 and Directory-container storage pools

Hi Karel.

That's the conclusion we came to too.

James.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Karel Bos
Sent: 16 September 2015 10:17
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM 7.1.3 and Directory-container storage pools

Hi,

So we get a new type of storage pools, the directory-container storage pools. 
These enable TSM to do in flight dedup. But you cannot use any of the following 
functions with directory-container storage pools:

   - Migration
   - Reclamation
   - Aggregation
   - Collocation
   - Simultaneous-write
   - Storage pool backup
   - Virtual volumes

So having in flight dedupe removes any way of doing bck stg other than use node 
replication to get the data in a second place. Pretty bad limitation in my 
opinion or am I missing something?

Kind regards,

Karel