Friday, February 5, 2010

Windows
Server 2003 R2 contains some new features that help to better administer file
and storage servers, including folder level quota enforcement.

The old
school disc quota was volume based, that is why it is limited to per disk, and
thus it is sometimes pretty complicated to set up. Other limitations were also
there. Such as, Disk quotas are per-user. In other words, quotas are based on
who owns files, not on which folder they are stored in as long as the folders
are on the same volume. Disk quotas are calculated using the logical size of
files, not the actual physical disk space they occupy. You can’t configure disk
quotas on multiple volumes simultaneously. When disk quotas are exceeded, the
only notification that can be generated is having an event logged to the Event
logs.

Windows
Server 2003 R2 contains some new features that help to better administer file
and storage servers, including folder level quota enforcement.

The old
school disc quota was volume based, that is why it is limited to per disk, and
thus it is sometimes pretty complicated to set up. Other limitations were also
there. Such as, Disk quotas are per-user. In other words, quotas are based on
who owns files, not on which folder they are stored in as long as the folders
are on the same volume. Disk quotas are calculated using the logical size of
files, not the actual physical disk space they occupy. You can’t configure disk
quotas on multiple volumes simultaneously. When disk quotas are exceeded, the
only notification that can be generated is having an event logged to the Event
logs.