What you are saying is the maximum file size is larger than the percentage of the storage pool left. I would think it would be prudent to have the maximum file size no larger than 1/3 the percentage of the storage pool left. To my knowledge, a file that is smaller than the maximum file size (aggregates) will go into the disk pool regardless of whether it will fit or not. When the threshold is reached migration will kick off. The sessions sending files (aggregates) to the disk pool appear to suspend when this happens based on what I have seen.
The other case is the file is larger than the maximum file size and goes directly to tape. To my knowledge there are no messages or anything to tell you that this condition happened. But, what you can look for is media wait time for sessions. Then do some looking at the backups and contents tables to see what files are too large to fit in the maximum file size. Read this from the Define Storage pool. If a file exceeds the maximum size and no pool is specified as the next storage pool in the hierarchy, the server does not store the file. If a file exceeds the maximum size and a pool is specified as the next storage pool, the server stores the file in the next storage pool that can accept the file size. If you specify the next storage pool parameter, at least one storage pool in your hierarchy should have no limit on the maximum size of a file. By having no limit on the size for at least one pool, you ensure that no matter what its size, the server can store the file. For logical files that are part of an aggregate, the server considers the size of the aggregate to be the file size. Therefore, the server does not store logical files that are smaller than the maximum size limit if the files are part of an aggregate that is larger than the maximum size limit. Notes: 1. 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. I know this is not what you asked but maybe it will help you understand the issues. Paul D. Seay, Jr. Technical Specialist Naptheon Inc. 757-688-8180 -----Original Message----- From: David E Ehresman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 09, 2002 3:00 PM To: [EMAIL PROTECTED] Subject: Re: Disk storage pool too small? >If you look through your activity log you will see when the disk storage >pool fills up it will automatically get migrated to tape based upon the >low and high water migration values. > I'm not asking about disk storage migration but the case when a node backup goes directly to tape because it is backing up up a file that will not fit in the disk storagepool even though the disk storage pool has not hit its migration high water value. David