Among Senergy's many features, quota management through policy may be one of the most time-saving for administrators and quota managers. However, if you're provisioning a new server or setting up Windows quotas for the first time, there are a few requirements to meet first, and some of those are not immediately obvious. Likewise, there are a few common environmental problems we see when administrators begin to use Senergy for quota management that need some explanation.
File Server Resource Manager
The File Server Resource Manager features of Windows servers (part of the File Services role) is the core File Services piece involved in setting quota. FSRM must be installed on the Engine server, and FSRM must be installed on each server where quota is managed.
As a reminder: Senergy can only manage quotas on servers running FSRM or an equivalent service which replicates these APIs is required for quota management. In practice, this generally prevents Senergy from managing quotas on most NAS devices (which commonly use qtrees rather than Windows directory quotas.)
Only local Administrators have permissions to manage quotas and other FSRM features on Windows servers. This requires effective membership in the local Administrators group on each server; there is no other way to grant FSRM permissions exclusively. The Senergy proxy rights group must be a member of the local Administrators group on the Engine server and on each server where storage is managed.
This is a common source of FSRM-related issues when configuring a server to work with Senergy.
The FSRM inbound rules in the Windows firewall need to be enabled, to allow Senergy to remotely manage quotas. These are:
- File Server Remote Management (DCOM-In)
- File Server Remote Management (SMB-In)
- File Server Remote Management (WMI-In)
Additionally, the following inbound rules also need to be enabled:
- Remote File Server Resource Manager Management - FSRM Service (RPC-In)
- Remote File Server Resource Manager Management - Remote Registry (RPC-In)
- Remote File Server Resource Manager Management - RpcSs (RPC-EPMAP)
- Remote File Server Resource Manager Management - Windows Management Instrumentation (Async-In)
- Remote File Server Resource Manager Management - Windows Management Instrumentation (WMI-In)
- Remote File Server Resource Manager Management (SMB-In)
Incorrect Quotas Reported
Senergy's quota management works by setting quotas through the File Server Resource Manager and reading quotas set there. As such, when users or Senergy report incorrect quotas, this is typically the result of incorrectly configured quotas in FSRM.
Nested quotas are the most common quota misconfiguration. Directory quotas report usage and restrict user behavior based on every quota applicable to a path, not just the 'closest' quota for a user.
For example: Given the path
\parent has a 1000 MB quota and
\child has a 500MB quota:
- If all folders are empty, FSRM will report that there's 500MB free in
\parentcontains 200MB of data but
\childis empty, FSRM will report that there's 500MB free in
\parent\child(and 800MB free in
\parentcontains 700MB of data but
\childis empty, FSRM will report that there's 300MB free in
\parent, and thus 300MB free in
\parent\child—both quotas apply.
Check that there are no quotas set in the file system above the path where quotas appear to be reported incorrectly.
FSRM Database Corruption
While very uncommon, we have occasionally seen FSRM's internal database contain corrupted data or be inaccessible to FSRM. Troubleshooting these sorts of problems is outside the scope of this article, but will generally cause errors in the FSRM MMC snap-in or show problems related to specific paths where quotas misbehave. Windows file system administrators may need to investigate these problems directly.