ADSM-L

Re: AW: [ADSM-L] migration doesn't seem to be ending

2006-02-01 13:12:59
Subject: Re: AW: [ADSM-L] migration doesn't seem to be ending
From: "Bos, Karel" <Karel.Bos AT ATOSORIGIN DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 1 Feb 2006 19:12:26 +0100
TSM 5.3.2.1 server. Why don't you use the new "migrate stg backuppool low=40 
dur=XX" option instead of the upd stg?

Regards,

Karel
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Timothy Hughes
Sent: woensdag 1 februari 2006 19:06
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: AW: [ADSM-L] migration doesn't seem to be ending

Thanks Thomas and Andy!

Andy Huebner wrote:

> Also, backups running during the migration time can prevent the pool from 
> reaching 0.  We use 1 to get around that problem.
>
> Andy Huebner
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Thomas Rupp
> Sent: Wednesday, February 01, 2006 8:41 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] AW: [ADSM-L] migration doesn't seem to be ending
>
> Hi,
>
> See http://people.bu.edu/rbs/ADSM.funcdir, keyword: MIGRATION
>                                         Occurs with one process per node
>                                         (regardless of the MIGPRocess value),
>                                         choosing the node with the largest
>                                         amount of data in the storage pool and
>                                         moving *all* of that node's data 
> before
>                                         embarking upon the same processing for
>                                         other nodes - or before again checking
>                                         the LOwmig value.
> When you change the LOWMIG value TSM waits till it has moved *all* 
> files of the node it is currently working on.
> So this might take some time if you have nodes with many, many files.
>
> HTH
> Thomas Rupp
>
> -----Ursprüngliche Nachricht-----
> Von: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] Im Auftrag 
> von Timothy Hughes
> Gesendet: Mittwoch, 01. Februar 2006 15:34
> An: ADSM-L AT VM.MARIST DOT EDU
> Betreff: [ADSM-L] migration doesn't seem to be ending
>
> Hello all,
>
> After viewing our Backup Disk Pool,  I noticed that migration doesn't 
> seem to be stopping. The below percentages don't seem right since I 
> have the following settings. Anyone else see this as odd or am I 
> missing something?  If so what could be causing this?
>
> Thanks for any suggestions, help!
>
> update stgpool backuppool highmig=0 lowmig=0
>
> update stgpool backuppool highmig=70 lowmig=40
>
> Disk storage pools : BACKUPPOOL
>
> Storage Pool Name BACKUPPOOL
> Storage Pool Type PRIMARY
> Device Class Name DISK
> Estimated Capacity 1013760.0
> Space Trigger Util 17.6
> Pct Util 17.6
> Pct Migr 16.3
> Pct Logical 100.0
> High Mig Pct 70
> Low Mig Pct 40
> Migration Processes 14
> Next Storage Pool H3592POOL
> Maximum Size Threshold -
> Access READWRITE
> Description Disk Backup Pool
> Overflow Location -
> Cache Migrated Files? NO
> Collocate? -
> Reclamation Threshold -
> Maximum Scratch Volumes Allowed -
> Number of Scratch Volumes Used -
> Delay Period for Volume Reuse -
> Migration in Progress? NO
> Amount Migrated (MB) -
> Elapsed Migration Time (seconds) 632871 Reclamation in Progress? - 
> Last Update Date/Time 2006-01-31 11:00:14.000000 Last Update by 
> (administrator) Reclaim Storage Pool - Migration Delay 0 Migration 
> Continue YES Storage Pool Data Format Native Copy Storage Pool(s) - 
> Continue Copy on Error? - CRC Data YES Reclamation Processes - Offsite 
> Reclamation Limit - Reclamation Type THRESHOLD
>
> TSM 5.3.2.1
> AIX 5.3
> RS/6000
>
> This e-mail (including any attachments) is confidential and may be legally 
> privileged. If you are not an intended recipient or an authorized 
> representative of an intended recipient, you are prohibited from using, 
> copying or distributing the information in this e-mail or its attachments. If 
> you have received this e-mail in error, please notify the sender immediately 
> by return e-mail and delete all copies of this message and any attachments.
> Thank you.

Attachment: Disclaimer.txt
Description: Text document