ADSM-L

Re: [ADSM-L] How are primary sequential storage pools allocated?

2010-04-09 09:25:27
Subject: Re: [ADSM-L] How are primary sequential storage pools allocated?
From: Lindsay Morris <lindsay AT TSMWORKS DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 9 Apr 2010 09:23:11 -0400
If I understand you, with "no members in the group", your
collocation-by-group acts like collocation-by-node.
So TSM will try to put each node's data (small) on a separate tape volume
(large), and you get the behavior you're seeing now.

Group collocation is what you want, to fill tapes fuller, but you have to
put nodes into collocation groups first.
See Allen Rout's excellent script from last week for a way to automate this
(or just make reasonable guesses).

Another note: try to only put ONE Tier-1 node into each collocation group.
That way, in a DR exercise, the won't compete for tape volumes and you have
a chance of restoring them all in parallel.

--------------------
Lindsay Morris
CEO, TSMworks
Tel. 1-859-539-9900
lindsay AT tsmworks DOT com


On Fri, Apr 9, 2010 at 9:14 AM, James Choate <jchoate AT chooses1 DOT com> 
wrote:

> TSM 5.5.4.1 On Windows 2003
>
> I have a primary disk storage pool that is 500GB called DISKPOOL and a
> primary sequential storage pool called ONSITE that is defined as the
> NEXTSTGPOOL for DISKPOOL.
>
>
>
> What I am noticing is that as I migrate data from DISKPOOL to ONSITE, the
> tapes are getting allocated to the ONSITE pool, but are not filling all the
> way up.   I was anticipating that as the migration would kick off, tapes
> would fill until it reached a full status, then the next tape would get
> allocated.  Collocation is set to group, but there aren't any members in the
> group.  Here is a snippet of the volumes, and I have also attached what the
> stgpool looks like.
> 000102L3                  OFFSITE      LTO3CLASS   762,938.0    1.5
>  Filling
> 000103L3                  ONSITE       LTO3CLASS   762,938.0    1.6
>  Filling
> 000104L3                  ONSITE       LTO3CLASS   762,938.0    0.9
>  Filling
> 000105L3                  ONSITE       LTO3CLASS   402,407.2  100.0    Full
> 000106L3                  ONSITE       LTO3CLASS   762,938.0   38.6
>  Filling
> 000107L3                  ONSITE       LTO3CLASS   762,938.0   37.2
>  Filling
> 000108L3                  ONSITE       LTO3CLASS   398,773.8  100.0    Full
> 000109L3                  ONSITE       LTO3CLASS   762,938.0   24.4
>  Filling
> 000110L3                  ONSITE       LTO3CLASS   762,938.0    0.7
>  Filling
> 000111L3                  ONSITE       LTO3CLASS   762,938.0    0.6
>  Filling
> 000112L3                  ONSITE       LTO3CLASS   762,938.0    0.5
>  Filling
> 000113L3                  ONSITE       LTO3CLASS   762,938.0    0.4
>  Filling
> 000114L3                  ONSITE       LTO3CLASS   387,116.8  100.0    Full
>
> ONSITE stgpool:
>
>               Storage Pool Name: ONSITE
>               Storage Pool Type: Primary
>               Device Class Name: LTO3CLASS
>              Estimated Capacity: 34,216 G
>              Space Trigger Util:
>                        Pct Util: 7.2
>                        Pct Migr: 28.0
>                     Pct Logical: 100.0
>                    High Mig Pct: 95
>                     Low Mig Pct: 90
>                 Migration Delay: 0
>              Migration Continue: Yes
>             Migration Processes: 1
>           Reclamation Processes: 1
>               Next Storage Pool:
>            Reclaim Storage Pool:
>          Maximum Size Threshold: No Limit
>                          Access: Read/Write
>                     Description: primary onstie storage pool
>               Overflow Location:
>           Cache Migrated Files?:
>                      Collocate?: Group
>           Reclamation Threshold: 100
>       Offsite Reclamation Limit:
>  Maximum Scratch Volumes Allowed: 50
>  Number of Scratch Volumes Used: 14
>   Delay Period for Volume Reuse: 0 Day(s)
>          Migration in Progress?: No
>            Amount Migrated (MB): 0.00
> Elapsed Migration Time (seconds): 0
>        Reclamation in Progress?: No
>  Last Update by (administrator): ADMIN
>           Last Update Date/Time: 04/09/2010 07:09:46
>        Storage Pool Data Format: Native
>            Copy Storage Pool(s):
>             Active Data Pool(s):
>         Continue Copy on Error?: Yes
>                        CRC Data: No
>                Reclamation Type: Threshold
>     Overwrite Data when Deleted:
>