Hi Eric! Yes! Here are all settings for the storagepool: Storage Pool Name: DISKPOOL_LBU3_1 Storage Pool Type: Primary Device Class Name: DISK Estimated Capacity: 983 G Space Trigger Util: 12.9 Pct Util: 12.8 Pct Migr: 12.6 Pct Logical: 100.0 High Mig Pct: 5 Low Mig Pct: 0 Migration Delay: 0 Migration Continue: Yes Migration Processes: 10 Reclamation Processes: Next Storage Pool: DL_LBU3_STB_1 Reclaim Storage Pool: Maximum Size Threshold: No Limit Access: Read/Write Description: Overflow Location: Cache Migrated Files?: No Collocate?: Reclamation Threshold: Offsite Reclamation Limit: Maximum Scratch Volumes Allowed: Number of Scratch Volumes Used: Delay Period for Volume Reuse: Migration in Progress?: Yes Amount Migrated (MB): 2,668,083.67 Elapsed Migration Time (seconds): 55,786 Reclamation in Progress?: Last Update by (administrator): KLM35757 Last Update Date/Time: 10/02/2009 10:50:25 Storage Pool Data Format: Native Copy Storage Pool(s): Continue Copy on Error?: CRC Data: No Reclamation Type:
Kind regards, Eric van Loon KLM Royal Dutch Airlines -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Eric Vaughn Sent: vrijdag 2 oktober 2009 15:01 To: ADSM-L@VM.MARIST.EDU Subject: Re: Migration problem Do you have a high and low migration threshold set? Eric Vaughn Technical Administrator Stevenson University Office (443)334-2301 evau...@stevenson.edu >>> "Loon, EJ van - SPLXM" <eric-van.l...@klm.com> 10/2/2009 8:33 AM >>> Hi TSM-ers! Today I came in the office and customers complained about failing backups. I checked the TSM server and noticed that the diskpool was full. Migration was running, but only two processes at the same time. A migration starts, migrates a file an then completes successfully, another one starts, migrates one file and finishes again and so on. The storagepool has migproc=10 and the nextpool is not collocated, but only two are running and they keep on finishing after just migrating one file! I was able to lower the storagepool usage manually by issuing move data commands against the physical diskpool volumes. This way I was able to move all the data from them manually, but I don't understand why migration is behaving like this. Has anybody seen this before? Thank you very much for your reply in advance! Kind regards, Eric van Loon ********************************************************************** 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 ********************************************************************** ********************************************************************** 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 **********************************************************************
