Re: Storage Pool Migration and Mediawait question/problem
Hello Tab, Thank you for your reply, you are absolutely wright ! A few days ago we changed our diskpool from 1 volume of 16 Gb. to 16 volumes of 1 Gb. This gives a whole lot of difference !! I watched the backup (quite interesting) the whole night (didn't go to sleep), and saw that no Media Wait occured. According the advice from somebody else in this newsgroup we lowered the high mig threshold to 50 %. Now the backuppool gets to a maximum of 80 % Util. Regards, Wouter. -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]Namens Tab Trepagnier Verzonden: vrijdag 25 januari 2002 2:14 Aan: [EMAIL PROTECTED] Onderwerp: Re: Storage Pool Migration and Mediawait question/problem Wouter, You didn't provide info on your disk pool setup, but a few months back on the forum there was a discussion on whether it was better to use one big volume or carve up the disks into multiple smaller volumes. If you encounter media wait status during migrations at the low migration thresholds you have set, either the next file won't fit in the remaining space and all downstream tape drives are in use, or you have only one or two disk volumes and the client can't get a lock on another volume to use while the migration is running. I personally subscribe to the theory that more volumes (within reason) are better. Most of my disk pools consist of many 1000 MB volumes. I have migration threshold set to 75% and I NEVER see waiting for mount messages in the backup logs. And my disk pools are too small by TSM best practice standards. Good luck. Tab Trepagnier TSM Administrator Laitram Corporation Wouter V [EMAIL PROTECTED]@VM.MARIST.EDU on 01/18/2002 05:21:27 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Storage Pool Migration and Mediawait question/problem Why does the migration process cause a (large) delay for my backups (mediawait) ? I don't understand why backup can't continue while TSM is migrating the data from disk to tape ? There is still enough place in the diskpool ! Can anybody give me any hints are recommandations ? Thank you in advance !! Wouter V. Storage Device EstimatedPctPct High Low Next Stora- Pool NameClass NameCapacity Util Migr Mig Mig ge Pool (MB) Pct Pct --- -- -- - - --- --- ARCHIVEPOOL DISK 0.00.00.090 70 BACKUPPOOL DISK 16,720.0 63.3 57.160 30 PTAPE_POOL PTAPE_POOL TAPE_CLASS 1,907,340.4.6 100.0 1000 0 SPACEMGPOOL DISK 0.00.00.090 70 Process Process Description Status Number -- --- 31 MigrationDisk Storage Pool BACKUPPOOL, Moved Files: 42790, Moved Bytes: 1,297,846,272, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 2,043,904 Current output volume: 13. 32 MigrationDisk Storage Pool BACKUPPOOL, Moved Files: 6854, Moved Bytes: 1,225,912,320, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 14,446,592 Current output volume: 06. Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - - 11,683 ShMem IdleW 22.6 M 1.7 K 1.1 K Node AIX BWB_ONT 11,684 ShMem Run 0 S 18.7 K 6.2 G Node AIX BWB_ONT 11,685 ShMem IdleW 11.3 M 858 821 Node AIX BWB_ONT 11,697 Tcp/Ip IdleW 27.1 M 3.5 M 9.0 K Node WinNTNEWTON 11,698 Tcp/Ip MediaW 20.5 M 714 235.8 M Node WinNTNEWTON 11,703 Tcp/Ip IdleW 21.1 M 3.4 M 650 Node WinNTEINSTEIN 11,704 Tcp/Ip MediaW 21.7 M 354 22.3 K Node WinNTEINSTEIN 11,705 Tcp/Ip MediaW 21.6 M 354 3.9 K Node WinNTEINSTEIN 11,706 Tcp/Ip IdleW 20.6 M 34.8 M 840 Node WinNTEINSTEIN 11,709 Tcp/Ip IdleW 18.6 M 465.0 K 1.1 K Node WinNTACSL1 11,710 Tcp/Ip MediaW 19.0 M 354 22.3 K Node WinNTACSL1 11,711 Tcp/Ip IdleW 18.5 M 680.0 K 501 Node WinNTACSL1 11,712 Tcp/Ip MediaW 18.9 M 354 8.9 K Node WinNTACSL1 11,714 Tcp/Ip IdleW 16.4 M 1.8 M 589 Node WinNTITF_TRA 11,715 Tcp/Ip MediaW 16.7 M 354 22.2 K Node WinNTITF_TRA 11,716 Tcp/Ip IdleW 16.6 M 515 819 Node WinNTITF_TRA 11,717 Tcp/Ip MediaW 16.5 M 354 5.3 K Node WinNTITF_TRA 11,718 Tcp/Ip IdleW 9.5 M2.2
Re: Storage Pool Migration and Mediawait question/problem
Wouter, You didn't provide info on your disk pool setup, but a few months back on the forum there was a discussion on whether it was better to use one big volume or carve up the disks into multiple smaller volumes. If you encounter media wait status during migrations at the low migration thresholds you have set, either the next file won't fit in the remaining space and all downstream tape drives are in use, or you have only one or two disk volumes and the client can't get a lock on another volume to use while the migration is running. I personally subscribe to the theory that more volumes (within reason) are better. Most of my disk pools consist of many 1000 MB volumes. I have migration threshold set to 75% and I NEVER see waiting for mount messages in the backup logs. And my disk pools are too small by TSM best practice standards. Good luck. Tab Trepagnier TSM Administrator Laitram Corporation Wouter V [EMAIL PROTECTED]@VM.MARIST.EDU on 01/18/2002 05:21:27 PM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Storage Pool Migration and Mediawait question/problem Why does the migration process cause a (large) delay for my backups (mediawait) ? I don't understand why backup can't continue while TSM is migrating the data from disk to tape ? There is still enough place in the diskpool ! Can anybody give me any hints are recommandations ? Thank you in advance !! Wouter V. Storage Device EstimatedPctPct High Low Next Stora- Pool NameClass NameCapacity Util Migr Mig Mig ge Pool (MB) Pct Pct --- -- -- - - --- --- ARCHIVEPOOL DISK 0.00.00.090 70 BACKUPPOOL DISK 16,720.0 63.3 57.160 30 PTAPE_POOL PTAPE_POOL TAPE_CLASS 1,907,340.4.6 100.0 1000 0 SPACEMGPOOL DISK 0.00.00.090 70 Process Process Description Status Number -- --- 31 MigrationDisk Storage Pool BACKUPPOOL, Moved Files: 42790, Moved Bytes: 1,297,846,272, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 2,043,904 Current output volume: 13. 32 MigrationDisk Storage Pool BACKUPPOOL, Moved Files: 6854, Moved Bytes: 1,225,912,320, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 14,446,592 Current output volume: 06. Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - - 11,683 ShMem IdleW 22.6 M 1.7 K 1.1 K Node AIX BWB_ONT 11,684 ShMem Run 0 S 18.7 K 6.2 G Node AIX BWB_ONT 11,685 ShMem IdleW 11.3 M 858 821 Node AIX BWB_ONT 11,697 Tcp/Ip IdleW 27.1 M 3.5 M 9.0 K Node WinNTNEWTON 11,698 Tcp/Ip MediaW 20.5 M 714 235.8 M Node WinNTNEWTON 11,703 Tcp/Ip IdleW 21.1 M 3.4 M 650 Node WinNTEINSTEIN 11,704 Tcp/Ip MediaW 21.7 M 354 22.3 K Node WinNTEINSTEIN 11,705 Tcp/Ip MediaW 21.6 M 354 3.9 K Node WinNTEINSTEIN 11,706 Tcp/Ip IdleW 20.6 M 34.8 M 840 Node WinNTEINSTEIN 11,709 Tcp/Ip IdleW 18.6 M 465.0 K 1.1 K Node WinNTACSL1 11,710 Tcp/Ip MediaW 19.0 M 354 22.3 K Node WinNTACSL1 11,711 Tcp/Ip IdleW 18.5 M 680.0 K 501 Node WinNTACSL1 11,712 Tcp/Ip MediaW 18.9 M 354 8.9 K Node WinNTACSL1 11,714 Tcp/Ip IdleW 16.4 M 1.8 M 589 Node WinNTITF_TRA 11,715 Tcp/Ip MediaW 16.7 M 354 22.2 K Node WinNTITF_TRA 11,716 Tcp/Ip IdleW 16.6 M 515 819 Node WinNTITF_TRA 11,717 Tcp/Ip MediaW 16.5 M 354 5.3 K Node WinNTITF_TRA 11,718 Tcp/Ip IdleW 9.5 M2.2 M 546 Node WinNTBWB_TRA1 more... (ENTER to continue, 'C' to cancel) 11,720 Tcp/Ip MediaW 9.8 M 354 22.2 K Node WinNTBWB_TRA1 11,721 Tcp/Ip MediaW 9.7 M 360 10.7 K Node WinNTBWB_TRA1 11,722 Tcp/Ip IdleW 9.1 M2.9 M 534 Node WinNTBWB_TRA1 11,723 Tcp/Ip IdleW 7.1 M3.2 M 541 Node WinNTNOTES_TRA 11,724 Tcp/Ip IdleW 9.4 M2.6 K 1.1 K Node WinNTNOTES_TRA 11,725 Tcp/Ip MediaW 7.1 M 409 64.0 M Node WinNTNOTES_TRA 11,726 Tcp/Ip MediaW 9.2 M 406 424.5 K Node WinNTNOTES_TRA 11,727 Tcp/Ip IdleW 7.2 M2.4 M 611 Node WinNTBSC_NT3_TRA 11,728 Tcp/Ip MediaW 7.3 M 354 22.3 K Node WinNTBSC_NT3_TRA 11,729 Tcp/Ip IdleW
Re: Storage Pool Migration and Mediawait question/problem
I only have 2 tape drives, and already do a forced migration, early in the morning (after all backups). I agree the diskpool might be the small, but for financial reasons it couldn't be bigger. Nonetheless, thank you very much for your response ! Wouter V. Unix System Engineer -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]Namens Seay, Paul Verzonden: maandag 21 januari 2002 5:35 Aan: [EMAIL PROTECTED] Onderwerp: Re: Storage Pool Migration and Mediawait question/problem If he has more than two tape drives he may try increasing the number of drives. Also, a couple hours before his backups each night I recommend that he do a force migration by updating the LO and HI to appropriate numbers and after the migration is complete set it back to normal. This way he starts out with the backup pool trimmed. Ultimately, this backuppool is too small for this configuration. The recommendation is about the size of what you are going to backup to a pool during an incremental cycle. -Original Message- From: Kelly Lipp [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 20, 2002 11:01 PM To: [EMAIL PROTECTED] Subject: Re: Storage Pool Migration and Mediawait question/problem This happens if the disk pool fills and migration can't keep up. When the client starts a transaction with the server the server is asked to create enough room for the data. In the case where the diskpool is full, that space will be in the nextstg pool usually tape. So that client is then waiting for media. This happens to most of the clients at this point resulting in the q session you are seeing. Backuppool is not very large in your configuration. You might try lowering high migration to 50 and see if migration can stay ahead of newly arriving data. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Wouter V Sent: Friday, January 18, 2002 4:21 PM To: [EMAIL PROTECTED] Subject: Storage Pool Migration and Mediawait question/problem Why does the migration process cause a (large) delay for my backups (mediawait) ? I don't understand why backup can't continue while TSM is migrating the data from disk to tape ? There is still enough place in the diskpool ! Can anybody give me any hints are recommandations ? Thank you in advance !! Wouter V. Storage Device EstimatedPctPct High Low Next Stora- Pool NameClass NameCapacity Util Migr Mig Mig ge Pool (MB) Pct Pct --- -- -- - - --- --- ARCHIVEPOOL DISK 0.00.00.090 70 BACKUPPOOL DISK 16,720.0 63.3 57.160 30 PTAPE_POOL PTAPE_POOL TAPE_CLASS 1,907,340.4.6 100.0 1000 0 SPACEMGPOOL DISK 0.00.00.090 70 Process Process Description Status Number -- --- 31 MigrationDisk Storage Pool BACKUPPOOL, Moved Files: 42790, Moved Bytes: 1,297,846,272, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 2,043,904 Current output volume: 13. 32 MigrationDisk Storage Pool BACKUPPOOL, Moved Files: 6854, Moved Bytes: 1,225,912,320, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 14,446,592 Current output volume: 06. Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - - 11,683 ShMem IdleW 22.6 M 1.7 K 1.1 K Node AIX BWB_ONT 11,684 ShMem Run 0 S 18.7 K 6.2 G Node AIX BWB_ONT 11,685 ShMem IdleW 11.3 M 858 821 Node AIX BWB_ONT 11,697 Tcp/Ip IdleW 27.1 M 3.5 M 9.0 K Node WinNTNEWTON 11,698 Tcp/Ip MediaW 20.5 M 714 235.8 M Node WinNTNEWTON 11,703 Tcp/Ip IdleW 21.1 M 3.4 M 650 Node WinNTEINSTEIN 11,704 Tcp/Ip MediaW 21.7 M 354 22.3 K Node WinNTEINSTEIN 11,705 Tcp/Ip MediaW 21.6 M 354 3.9 K Node WinNTEINSTEIN 11,706 Tcp/Ip IdleW 20.6 M 34.8 M 840 Node WinNTEINSTEIN 11,709 Tcp/Ip IdleW 18.6 M 465.0 K 1.1 K Node WinNTACSL1 11,710 Tcp/Ip MediaW 19.0 M 354 22.3 K Node WinNTACSL1 11,711 Tcp/Ip IdleW 18.5 M 680.0 K 501 Node WinNTACSL1 11,712 Tcp/Ip MediaW 18.9 M 354 8.9 K Node WinNT
Re: Storage Pool Migration and Mediawait question/problem
OK, thank you, I lowered the high mig limit to 50, this evening I will see what the result is. But, I think I found another reason for the mediawait problem. Since directory information goes to the management class with the longest retention period, the directory info went to a management_class (orabackup_35), which goes directly to tape. I think if a migration starts (tell me if I'm wrong), TSM can't write the directory information directly to tape (because the 2 drives are used), so all clients have to wait until migration is finished (TSM then mounts again the tape with the directory information). I solved this by creating a mc with a longer retention period than all other mc's, going to disk first. (I also could use the dirmc option). Thank you for your responses !! Regards, Wouter Verschaeve Unix System Engineer -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]Namens Kelly Lipp Verzonden: maandag 21 januari 2002 5:01 Aan: [EMAIL PROTECTED] Onderwerp: Re: Storage Pool Migration and Mediawait question/problem This happens if the disk pool fills and migration can't keep up. When the client starts a transaction with the server the server is asked to create enough room for the data. In the case where the diskpool is full, that space will be in the nextstg pool usually tape. So that client is then waiting for media. This happens to most of the clients at this point resulting in the q session you are seeing. Backuppool is not very large in your configuration. You might try lowering high migration to 50 and see if migration can stay ahead of newly arriving data. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Wouter V Sent: Friday, January 18, 2002 4:21 PM To: [EMAIL PROTECTED] Subject: Storage Pool Migration and Mediawait question/problem Why does the migration process cause a (large) delay for my backups (mediawait) ? I don't understand why backup can't continue while TSM is migrating the data from disk to tape ? There is still enough place in the diskpool ! Can anybody give me any hints are recommandations ? Thank you in advance !! Wouter V. Storage Device EstimatedPctPct High Low Next Stora- Pool NameClass NameCapacity Util Migr Mig Mig ge Pool (MB) Pct Pct --- -- -- - - --- --- ARCHIVEPOOL DISK 0.00.00.090 70 BACKUPPOOL DISK 16,720.0 63.3 57.160 30 PTAPE_POOL PTAPE_POOL TAPE_CLASS 1,907,340.4.6 100.0 1000 0 SPACEMGPOOL DISK 0.00.00.090 70 Process Process Description Status Number -- --- 31 MigrationDisk Storage Pool BACKUPPOOL, Moved Files: 42790, Moved Bytes: 1,297,846,272, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 2,043,904 Current output volume: 13. 32 MigrationDisk Storage Pool BACKUPPOOL, Moved Files: 6854, Moved Bytes: 1,225,912,320, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 14,446,592 Current output volume: 06. Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - - 11,683 ShMem IdleW 22.6 M 1.7 K 1.1 K Node AIX BWB_ONT 11,684 ShMem Run 0 S 18.7 K 6.2 G Node AIX BWB_ONT 11,685 ShMem IdleW 11.3 M 858 821 Node AIX BWB_ONT 11,697 Tcp/Ip IdleW 27.1 M 3.5 M 9.0 K Node WinNTNEWTON 11,698 Tcp/Ip MediaW 20.5 M 714 235.8 M Node WinNTNEWTON 11,703 Tcp/Ip IdleW 21.1 M 3.4 M 650 Node WinNTEINSTEIN 11,704 Tcp/Ip MediaW 21.7 M 354 22.3 K Node WinNTEINSTEIN 11,705 Tcp/Ip MediaW 21.6 M 354 3.9 K Node WinNTEINSTEIN 11,706 Tcp/Ip IdleW 20.6 M 34.8 M 840 Node WinNTEINSTEIN 11,709 Tcp/Ip IdleW 18.6 M 465.0 K 1.1 K Node WinNTACSL1 11,710 Tcp/Ip MediaW 19.0 M 354 22.3 K Node WinNTACSL1 11,711 Tcp/Ip IdleW 18.5 M 680.0 K 501 Node WinNTACSL1 11,712 Tcp/Ip MediaW 18.9 M 354 8.9 K Node WinNTACSL1 11,714 Tcp/Ip IdleW 16.4 M 1.8 M 589 Node WinNTITF_TRA 11,715 Tcp/Ip MediaW 16.7 M 354 22.2 K Node WinNTITF_TRA 11,716 Tcp/Ip
Storage Pool Migration and Mediawait question/problem
Why does the migration process cause a (large) delay for my backups (mediawait) ? I don't understand why backup can't continue while TSM is migrating the data from disk to tape ? There is still enough place in the diskpool ! Can anybody give me any hints are recommandations ? Thank you in advance !! Wouter V. Storage Device EstimatedPctPct High Low Next Stora- Pool NameClass NameCapacity Util Migr Mig Mig ge Pool (MB) Pct Pct --- -- -- - - --- --- ARCHIVEPOOL DISK 0.00.00.090 70 BACKUPPOOL DISK 16,720.0 63.3 57.160 30 PTAPE_POOL PTAPE_POOL TAPE_CLASS 1,907,340.4.6 100.0 1000 0 SPACEMGPOOL DISK 0.00.00.090 70 Process Process Description Status Number -- --- 31 MigrationDisk Storage Pool BACKUPPOOL, Moved Files: 42790, Moved Bytes: 1,297,846,272, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 2,043,904 Current output volume: 13. 32 MigrationDisk Storage Pool BACKUPPOOL, Moved Files: 6854, Moved Bytes: 1,225,912,320, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 14,446,592 Current output volume: 06. Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - - 11,683 ShMem IdleW 22.6 M 1.7 K 1.1 K Node AIX BWB_ONT 11,684 ShMem Run 0 S 18.7 K 6.2 G Node AIX BWB_ONT 11,685 ShMem IdleW 11.3 M 858 821 Node AIX BWB_ONT 11,697 Tcp/Ip IdleW 27.1 M 3.5 M 9.0 K Node WinNTNEWTON 11,698 Tcp/Ip MediaW 20.5 M 714 235.8 M Node WinNTNEWTON 11,703 Tcp/Ip IdleW 21.1 M 3.4 M 650 Node WinNTEINSTEIN 11,704 Tcp/Ip MediaW 21.7 M 354 22.3 K Node WinNTEINSTEIN 11,705 Tcp/Ip MediaW 21.6 M 354 3.9 K Node WinNTEINSTEIN 11,706 Tcp/Ip IdleW 20.6 M 34.8 M 840 Node WinNTEINSTEIN 11,709 Tcp/Ip IdleW 18.6 M 465.0 K 1.1 K Node WinNTACSL1 11,710 Tcp/Ip MediaW 19.0 M 354 22.3 K Node WinNTACSL1 11,711 Tcp/Ip IdleW 18.5 M 680.0 K 501 Node WinNTACSL1 11,712 Tcp/Ip MediaW 18.9 M 354 8.9 K Node WinNTACSL1 11,714 Tcp/Ip IdleW 16.4 M 1.8 M 589 Node WinNTITF_TRA 11,715 Tcp/Ip MediaW 16.7 M 354 22.2 K Node WinNTITF_TRA 11,716 Tcp/Ip IdleW 16.6 M 515 819 Node WinNTITF_TRA 11,717 Tcp/Ip MediaW 16.5 M 354 5.3 K Node WinNTITF_TRA 11,718 Tcp/Ip IdleW 9.5 M2.2 M 546 Node WinNTBWB_TRA1 more... (ENTER to continue, 'C' to cancel) 11,720 Tcp/Ip MediaW 9.8 M 354 22.2 K Node WinNTBWB_TRA1 11,721 Tcp/Ip MediaW 9.7 M 360 10.7 K Node WinNTBWB_TRA1 11,722 Tcp/Ip IdleW 9.1 M2.9 M 534 Node WinNTBWB_TRA1 11,723 Tcp/Ip IdleW 7.1 M3.2 M 541 Node WinNTNOTES_TRA 11,724 Tcp/Ip IdleW 9.4 M2.6 K 1.1 K Node WinNTNOTES_TRA 11,725 Tcp/Ip MediaW 7.1 M 409 64.0 M Node WinNTNOTES_TRA 11,726 Tcp/Ip MediaW 9.2 M 406 424.5 K Node WinNTNOTES_TRA 11,727 Tcp/Ip IdleW 7.2 M2.4 M 611 Node WinNTBSC_NT3_TRA 11,728 Tcp/Ip MediaW 7.3 M 354 22.3 K Node WinNTBSC_NT3_TRA 11,729 Tcp/Ip IdleW 6.6 M1.7 M 537 Node WinNTBSC_NT3_TRA 11,730 Tcp/Ip MediaW 7.1 M 354 5.2 K Node WinNTBSC_NT3_TRA
Re: Storage Pool Migration and Mediawait question/problem
If he has more than two tape drives he may try increasing the number of drives. Also, a couple hours before his backups each night I recommend that he do a force migration by updating the LO and HI to appropriate numbers and after the migration is complete set it back to normal. This way he starts out with the backup pool trimmed. Ultimately, this backuppool is too small for this configuration. The recommendation is about the size of what you are going to backup to a pool during an incremental cycle. -Original Message- From: Kelly Lipp [mailto:[EMAIL PROTECTED]] Sent: Sunday, January 20, 2002 11:01 PM To: [EMAIL PROTECTED] Subject: Re: Storage Pool Migration and Mediawait question/problem This happens if the disk pool fills and migration can't keep up. When the client starts a transaction with the server the server is asked to create enough room for the data. In the case where the diskpool is full, that space will be in the nextstg pool usually tape. So that client is then waiting for media. This happens to most of the clients at this point resulting in the q session you are seeing. Backuppool is not very large in your configuration. You might try lowering high migration to 50 and see if migration can stay ahead of newly arriving data. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Wouter V Sent: Friday, January 18, 2002 4:21 PM To: [EMAIL PROTECTED] Subject: Storage Pool Migration and Mediawait question/problem Why does the migration process cause a (large) delay for my backups (mediawait) ? I don't understand why backup can't continue while TSM is migrating the data from disk to tape ? There is still enough place in the diskpool ! Can anybody give me any hints are recommandations ? Thank you in advance !! Wouter V. Storage Device EstimatedPctPct High Low Next Stora- Pool NameClass NameCapacity Util Migr Mig Mig ge Pool (MB) Pct Pct --- -- -- - - --- --- ARCHIVEPOOL DISK 0.00.00.090 70 BACKUPPOOL DISK 16,720.0 63.3 57.160 30 PTAPE_POOL PTAPE_POOL TAPE_CLASS 1,907,340.4.6 100.0 1000 0 SPACEMGPOOL DISK 0.00.00.090 70 Process Process Description Status Number -- --- 31 MigrationDisk Storage Pool BACKUPPOOL, Moved Files: 42790, Moved Bytes: 1,297,846,272, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 2,043,904 Current output volume: 13. 32 MigrationDisk Storage Pool BACKUPPOOL, Moved Files: 6854, Moved Bytes: 1,225,912,320, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 14,446,592 Current output volume: 06. Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - - 11,683 ShMem IdleW 22.6 M 1.7 K 1.1 K Node AIX BWB_ONT 11,684 ShMem Run 0 S 18.7 K 6.2 G Node AIX BWB_ONT 11,685 ShMem IdleW 11.3 M 858 821 Node AIX BWB_ONT 11,697 Tcp/Ip IdleW 27.1 M 3.5 M 9.0 K Node WinNTNEWTON 11,698 Tcp/Ip MediaW 20.5 M 714 235.8 M Node WinNTNEWTON 11,703 Tcp/Ip IdleW 21.1 M 3.4 M 650 Node WinNTEINSTEIN 11,704 Tcp/Ip MediaW 21.7 M 354 22.3 K Node WinNTEINSTEIN 11,705 Tcp/Ip MediaW 21.6 M 354 3.9 K Node WinNTEINSTEIN 11,706 Tcp/Ip IdleW 20.6 M 34.8 M 840 Node WinNTEINSTEIN 11,709 Tcp/Ip IdleW 18.6 M 465.0 K 1.1 K Node WinNTACSL1 11,710 Tcp/Ip MediaW 19.0 M 354 22.3 K Node WinNTACSL1 11,711 Tcp/Ip IdleW 18.5 M 680.0 K 501 Node WinNTACSL1 11,712 Tcp/Ip MediaW 18.9 M 354 8.9 K Node WinNTACSL1 11,714 Tcp/Ip IdleW 16.4 M 1.8 M 589 Node WinNTITF_TRA 11,715 Tcp/Ip MediaW 16.7 M 354 22.2 K Node WinNTITF_TRA 11,716 Tcp/Ip IdleW 16.6 M 515 819 Node WinNTITF_TRA 11,717 Tcp/Ip MediaW 16.5 M 354 5.3 K Node WinNTITF_TRA 11,718 Tcp/Ip IdleW 9.5 M2.2 M 546 Node WinNTBWB_TRA1 more... (ENTER to continue, 'C' to cancel) 11,720 Tcp/Ip MediaW 9.8 M 354 22.2 K Node WinNTBWB_TRA1 11,721 Tcp/Ip MediaW 9.7 M 360 10.7 K Node WinNT
Re: Storage Pool Migration and Mediawait question/problem
This happens if the disk pool fills and migration can't keep up. When the client starts a transaction with the server the server is asked to create enough room for the data. In the case where the diskpool is full, that space will be in the nextstg pool usually tape. So that client is then waiting for media. This happens to most of the clients at this point resulting in the q session you are seeing. Backuppool is not very large in your configuration. You might try lowering high migration to 50 and see if migration can stay ahead of newly arriving data. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs, CO 80949 [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com or www.storserver.com (719)531-5926 Fax: (240)539-7175 -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Wouter V Sent: Friday, January 18, 2002 4:21 PM To: [EMAIL PROTECTED] Subject: Storage Pool Migration and Mediawait question/problem Why does the migration process cause a (large) delay for my backups (mediawait) ? I don't understand why backup can't continue while TSM is migrating the data from disk to tape ? There is still enough place in the diskpool ! Can anybody give me any hints are recommandations ? Thank you in advance !! Wouter V. Storage Device EstimatedPctPct High Low Next Stora- Pool NameClass NameCapacity Util Migr Mig Mig ge Pool (MB) Pct Pct --- -- -- - - --- --- ARCHIVEPOOL DISK 0.00.00.090 70 BACKUPPOOL DISK 16,720.0 63.3 57.160 30 PTAPE_POOL PTAPE_POOL TAPE_CLASS 1,907,340.4.6 100.0 1000 0 SPACEMGPOOL DISK 0.00.00.090 70 Process Process Description Status Number -- --- 31 MigrationDisk Storage Pool BACKUPPOOL, Moved Files: 42790, Moved Bytes: 1,297,846,272, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 2,043,904 Current output volume: 13. 32 MigrationDisk Storage Pool BACKUPPOOL, Moved Files: 6854, Moved Bytes: 1,225,912,320, Unreadable Files: 0, Unreadable Bytes: 0. Current Physical File (bytes): 14,446,592 Current output volume: 06. Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name Number Method StateTimeSent Recvd Type -- -- -- -- --- --- - - 11,683 ShMem IdleW 22.6 M 1.7 K 1.1 K Node AIX BWB_ONT 11,684 ShMem Run 0 S 18.7 K 6.2 G Node AIX BWB_ONT 11,685 ShMem IdleW 11.3 M 858 821 Node AIX BWB_ONT 11,697 Tcp/Ip IdleW 27.1 M 3.5 M 9.0 K Node WinNTNEWTON 11,698 Tcp/Ip MediaW 20.5 M 714 235.8 M Node WinNTNEWTON 11,703 Tcp/Ip IdleW 21.1 M 3.4 M 650 Node WinNTEINSTEIN 11,704 Tcp/Ip MediaW 21.7 M 354 22.3 K Node WinNTEINSTEIN 11,705 Tcp/Ip MediaW 21.6 M 354 3.9 K Node WinNTEINSTEIN 11,706 Tcp/Ip IdleW 20.6 M 34.8 M 840 Node WinNTEINSTEIN 11,709 Tcp/Ip IdleW 18.6 M 465.0 K 1.1 K Node WinNTACSL1 11,710 Tcp/Ip MediaW 19.0 M 354 22.3 K Node WinNTACSL1 11,711 Tcp/Ip IdleW 18.5 M 680.0 K 501 Node WinNTACSL1 11,712 Tcp/Ip MediaW 18.9 M 354 8.9 K Node WinNTACSL1 11,714 Tcp/Ip IdleW 16.4 M 1.8 M 589 Node WinNTITF_TRA 11,715 Tcp/Ip MediaW 16.7 M 354 22.2 K Node WinNTITF_TRA 11,716 Tcp/Ip IdleW 16.6 M 515 819 Node WinNTITF_TRA 11,717 Tcp/Ip MediaW 16.5 M 354 5.3 K Node WinNTITF_TRA 11,718 Tcp/Ip IdleW 9.5 M2.2 M 546 Node WinNTBWB_TRA1 more... (ENTER to continue, 'C' to cancel) 11,720 Tcp/Ip MediaW 9.8 M 354 22.2 K Node WinNTBWB_TRA1 11,721 Tcp/Ip MediaW 9.7 M 360 10.7 K Node WinNTBWB_TRA1 11,722 Tcp/Ip IdleW 9.1 M2.9 M 534 Node WinNTBWB_TRA1 11,723 Tcp/Ip IdleW 7.1 M3.2 M 541 Node WinNTNOTES_TRA 11,724 Tcp/Ip IdleW 9.4 M2.6 K 1.1 K Node WinNTNOTES_TRA 11,725 Tcp/Ip MediaW 7.1 M 409 64.0 M Node WinNTNOTES_TRA 11,726 Tcp/Ip MediaW 9.2 M 406 424.5 K Node WinNTNOTES_TRA 11,727 Tcp/Ip IdleW 7.2 M2.4 M 611 Node WinNTBSC_NT3_TRA 11,728 Tcp/Ip MediaW 7.3 M 354 22.3 K Node WinNTBSC_NT3_TRA 11,729 Tcp/Ip IdleW 6.6 M1.7 M 537 Node WinNTBSC_NT3_TRA 11,730 Tcp/Ip MediaW 7.1 M 354 5.2 K Node WinNTBSC_NT3_TRA
