Iain, I run small disk pools also, and I also had HI=0 for a while. That's not a good idea because you prevent TSM from combining data into a internal package prior to migration. We saw files as small as 1 KB migrating. That forces your TSM server to track a HUGE number of objects.
Now, on our smallest disk pools (5 to 6 GB) we set HI=10 so that migration doesn't begin until 500-600 MB of data has been committed. Much better performance. We also set a 1 GB max size so that if a client sends a very large file - say 3 GB - it goes straight to tape. Tab Trepagnier TSM Administrator Laitram, L.L.C. Iain Barnetson <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> 03/04/2005 04:24 AM Please respond to "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> To ADSM-L@VM.MARIST.EDU cc Subject Re: migration and backup I'm in a similar situation where my primary stg diskpool is not big enough to contain a nights backups. I have the migration set to hi=0 lo=0. This means it's constantly migrating but I've 6 dedicated lto2 tape drives so isn't an issue for me. Regards, Iain -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of John Naylor Sent: 04 March 2005 10:17 To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] migration and backup Your disk pool is way too small. It should be large enough to hold one night's backups If you can't do that, set your hi mig threshold to a low value say 10 or even lower At 80% your backup fills up the remaining 20% of your pool faster than migration can empty it. nghiatd <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> 04/03/2005 10:15 Please respond to "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> To ADSM-L@vm.marist.edu cc Subject migration and backup Hi all, I setup TSM ver 5.2 client on Win 2K that has more than 200 GB data, But TSM server machine only 20 GB hard disk. So I configure Backuppool ---> Diskpool --->Tapepool. Diskpool : 18 GB High Migration Threshold : 80 % Low Migration Threshold : 0 %. People said when migration process is started, backup process is still continuous. But I view log file ; 02/03/2005 06:22:26 Normal File--> 719,648,279 \\BILL2_200411_2.tar * Unsuccessful* 02/03/2005 06:22:26 A1114I Waiting for mount of offline media. 02/03/2005 06:55:37 Retry # 1 Normal File--> 719,648,279 \\BILL2_200411_2.tar [Sent] 02/03/2005 06:55:37 ANS1809W Session is lost; initializing session reopen procedure. 02/03/2005 06:55:53 ... successful 02/03/2005 06:56:16 Normal File--> 726,513,573 \\BILL2_200411_3.tar [Sent] So backup was stopped when migration process is started. Does anyone have idea to backup process still continue ? Nghiatd ********************************************************************** The information in this E-Mail is confidential and may be legally privileged. It may not represent the views of Scottish and Southern Energy Group. It is intended solely for the addressees. Access to this E-Mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any unauthorised recipient should advise the sender immediately of the error in transmission. Unless specifically stated otherwise, this email (or any attachments to it) is not an offer capable of acceptance or acceptance of an offer and it does not form part of a binding contractual agreement. Scottish Hydro-Electric, Southern Electric, SWALEC, S+S and SSE Power Distribution are trading names of the Scottish and Southern Energy Group. **********************************************************************
