Hi Nick: That is exactly what I want but according to the doc this does not work:
"Note: This size limit applies only when the server is storing files during a session with a client. The limit does not apply when you move data from one pool to another, either manually or automatically through storage pool migration" So I have to admit, I've been lazy and have not tried this yet. I will have to try it out. Thanks, Tim -----Original Message----- From: Nicholas Cassimatis [mailto:[EMAIL PROTECTED] Sent: May 27, 2003 7:19 PM To: [EMAIL PROTECTED] Subject: Re: anyone using ATA disk systems Yep - have a maxsize on the 2nd DASD pool. When migration kicks off from the first DASD pool, the larger files will "skip" over the 2nd DASD pool to tape. It's just a 2 step nextpool configuration. Plus, if the 2nd DASD pool gets overfilled, it will migrate to the tape pool, so you won't get an out of space condition. Your storagepools would look like this: Storage Device Estimated Pct Pct High Low Next Stora- Pool Name Class Name Capacity Util Migr Mig Mig ge Pool (MB) Pct Pct ----------- ---------- ---------- ----- ----- ---- --- ----------- SCSIDASD DISK 1000.0 00.0 00.0 90 70 ATADASD ATADASD DISK 1000.0 00.0 00.0 90 70 TAPEPOOL TAPEPOOL TAPECLASS 0.0 00.0 00.0 90 70 And the ATADASD pool would have a maxsize parameter on it of whatever you wanted. Nick Cassimatis [EMAIL PROTECTED] Think twice, type once.