Re: [ADSM-L] TSM 7.1.3 and Directory-container storage pools

Hi Mike!
On the TSM Symposium in Dresden last month IBM stated that the MOVE DATA option 
to a container pool is a high priority for IBM and it's a candidate for the 
first half of 2016. If it's a priority for you, you should tell your IBM 
contact. If more people find this important, it will get a higher priority.
Kind regards,
Eric van Loon
AF/KLM Storage Engineering

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Ryder, Michael S
Sent: woensdag 7 oktober 2015 16:39
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM 7.1.3 and Directory-container storage pools

Hello Deirdre --

Can you comment on when we might see a better way to migrate existing 
storagepools into directory-container storagepools?  Perhaps an adjustment of 
"move data" or a new command, that doesn't require multiple steps hopping 
through a replication server?  It sounds like this is a needed feature that 
some of us can't get to without this functionality.

Best regards,

Mike <http://rbbuswiki.bbg.roche.com/wiki/ryderm_page:start>, x7942 RMD IT 
Client Services <http://rmsit.dia.roche.com/Pages/default.aspx>

On Tue, Oct 6, 2015 at 5:52 AM, Erwann SIMON <erwann.simon AT free DOT fr> 
wrote:

> Hi,
>
> As previously said by Deirdre, see the FAQ :
>
> https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki
> /Tivoli%20Storage%20Manager/page/Directory-container%20storage%20pools
> %20FAQs
>
> --
> Best regards / Cordialement / مع تحياتي Erwann SIMON
>
> ----- Mail original -----
> De: "Robert Ouzen" <rouzen AT UNIV.HAIFA.AC DOT IL>
> À: ADSM-L AT VM.MARIST DOT EDU
> Envoyé: Mardi 6 Octobre 2015 11:47:12
> Objet: Re: [ADSM-L] TSM 7.1.3 and Directory-container storage pools
>
> Hi to all
>
> Today in my V7.1.3 test environment , tried to move data from old stg 
> fashion (file) to  directory container storage without any success
> Tried with commands:   move nodedata and move data
>
> Here output
>
> tsm: TSMTEST>move nodedata test from=tsmstg1 to=stg_dir ANR3385E MOVE 
> NODEDATA: The operation is not allowed for container storage pools.
>
> tsm: TSMTEST>move data C:\MOUNTPOINTS\STORAGE_1\STG1\00000267.BFS
> stg=stg_dir
> ANR3385E MOVE DATA: The operation is not allowed for container storage 
> pools.
>
> I tried too , to do a nextstg
> TSMTEST>upd stg tsmstg1 nextstg=stg_dir
> ANR2399E UPDATE STGPOOL: Storage pool STG_DIR is not a sequential pool.
>
> I of course define stg with stgtype=directory (stg_dir) and after it 
> define stgpooldirectory
>
> Anybody know a way to move old stg to new stg with stgtype=directory  ????
>
> Regards
>
> Robert
>
>
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Stefan Folkerts
> Sent: Friday, September 18, 2015 9:49 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: [ADSM-L] TSM 7.1.3 and Directory-container storage pools
>
> I believe you can "move data" data into the container pools, you just 
> can't get the data out with traditional methods at the moment but only 
> via TSM node replication.
> I like the new pool type but they are only suitable to a specific type 
> of setup, the good news is that this setup covers a lot of the new 
> type of TSM deployments we are doing!
>
> On Wed, Sep 16, 2015 at 9:24 PM, Sergio O. Fuentes <sfuentes AT umd DOT edu>
> wrote:
>
> > This question is relevant.  How do I move from a file devclass 
> > stgpool to a directory-container pool.  And what's the impact on the 
> > DB if I do
> this?
> >  I already had multi-site configured for our environment with the 
> > tools that exist in versions <7.1.3.  I'm not getting another 200TB 
> > array to move data to new directory-container pools.
> >
> > Thanks!
> >
> > SF
> >
> > On 9/16/15, 10:49 AM, "ADSM: Dist Stor Manager on behalf of Ryder, 
> > Michael S" <ADSM-L AT VM.MARIST DOT EDU on behalf of 
> > michael_s.ryder AT ROCHE DOT COM>
> wrote:
> >
> > >I am very interested in directory-container storage pools.
> > >
> > >But...
> > >
> > >If Migration or Move Data are not options, then how does one 
> > >transition data from existing primary storage pools to a 
> > >directory-container storage pool?
> > >
> > >Mike
> > >
> > >Best regards,
> > >
> > >Mike <http://rbbuswiki.bbg.roche.com/wiki/ryderm_page:start>, x7942 
> > >RMD IT Client Services 
> > ><http://rmsit.dia.roche.com/Pages/default.aspx>
> > >
> > >On Wed, Sep 16, 2015 at 9:23 AM, Rick Adamson 
> > ><RickAdamson AT segrocers DOT com>
> > >wrote:
> > >
> > >> 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/welco
> > me
> > .ht
> > >>ml
> > >>
> > >> 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
> > >>
> >
>
********************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its 
employees shall not be liable for the incorrect or incomplete transmission of 
this e-mail or any attachments, nor responsible for any delay in receipt. 
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch 
Airlines) is registered in Amstelveen, The Netherlands, with registered number 
33014286
********************************************************