How quotas work with users and groups

When you specify a user or group as the target of a quota, the limits imposed by that quota are applied to that user or group. However, some special groups and users are handled differently. In addition, some rules apply to user and group quotas.

• How you specify UNIX users in the quotas file
  You can specify a UNIX user in the quotas file using one of three formats: the user name, the UID, or a file or directory owned by the user.
• How you specify Windows users in the quotas file
  You can specify a Windows user in the quotas file using one of three formats: the Windows name in pre-Windows 2000 format, the SID, or a file or directory owned by the SID of the user.
• How quotas are applied to the root user
  The root user (UID=0) on UNIX clients is subject to tree quotas, but not user quotas or group quotas. This allows the root user to take actions on behalf of other users that would otherwise be prevented by a quota.
• How quotas work with special Windows groups
  Quotas are applied to the Everyone group and the BUILTIN\Administrators group differently than to other Windows groups.
• How quotas are applied to users with multiple IDs
  A user can be represented by multiple IDs. You can set up a single user quota entry for such a user by specifying a list of IDs as the quota target. A file owned by any of these IDs is subject to the restriction of the user quota.
• How Data ONTAP determines user IDs in a mixed environment
  If you have users accessing your Data ONTAP storage from both Windows and UNIX clients, then both Windows and UNIX security are used to determine file ownership. Several factors determine whether Data ONTAP uses a UNIX or Windows ID when applying user quotas.
• How you link UNIX and Windows names for quotas
  In a mixed environment, users can log in as either Windows users or UNIX users. You can configure quotas to recognize that a user's UNIX id and Windows ID represent the same user.