# File Server quotas and shadow copies on Windows Server 2025

> Use FSRM quotas, file screening and Volume Shadow Copy previous versions on a Windows Server 2025 lab, and test restore without confusing snapshots with backups.

**Tested on**

- Build: 26100.33650
- Edition: Standard / Datacenter
- Architecture: x64
- Evidence: E1
- Verified: 2026-10-28

## The short answer

- **FSRM quotas** limit how much a folder/user can store; hard quota blocks, soft quota warns.
- **File screening** blocks file types by policy; useful, but easy to break a workflow.
- **Shadow Copies** keep point-in-time versions for quick “previous versions” restores.
- **None of these is a backup.** They live on the same volume/server and disappear with it.

Use quotas for capacity, shadow copies for user mistakes, and a real backup for disaster.

## Install FSRM

```powershell
Install-WindowsFeature FS-Resource-Manager -IncludeManagementTools
```

Then **Server Manager → Tools → File Server Resource Manager**.

## Quotas

```powershell
New-FsrmQuota -Path 'D:\Shares\Finance' -Size 50GB -SoftLimit
Get-FsrmQuota
```

- **Hard quota:** writes fail at the limit; predictable but can break apps.
- **Soft quota:** warns only; users can exceed it.
- Use a template for consistent limits across shares.
- Monitor `Get-FsrmQuota` and the FSRM event log; a quota is not a report.

Test with a real user: create files until the limit, confirm the error is understandable, then clean up.

## File screening

```powershell
New-FsrmFileGroup -Name 'Block-Media' -IncludePattern '*.mp4','*.mkv'
New-FsrmFileScreen -Path 'D:\Shares\Finance' -IncludeGroup 'Block-Media'
```

Screening is a policy, not malware protection. Do not block entire categories without a notification/exception plan; users will rename files or move data elsewhere.

## Shadow copies

Enable on the volume (not a single folder):

```powershell
vssadmin list shadows
vssadmin list shadowstorage
```

In the GUI: volume → Properties → **Shadow Copies** → enable → schedule → set storage area.

- Keep the schedule realistic (e.g., twice a day) and the storage area bounded.
- Previous Versions on a share lets users restore their own files.
- Shadow copies are not off-host and do not survive disk loss.
- Do not run out of shadow storage; old versions are deleted first.

> **Caution: Shadow copies are not a backup**
>
> A ransomware process with write access can delete shadow copies. Keep an independent, offline/off-host backup and test a restore.

## Test restore

1. Create a file, edit it, wait for the next shadow copy.
2. Right-click → **Restore previous versions**.
3. Restore to a **different name** first; compare.
4. Delete a file and restore it; confirm permissions.
5. Document the schedule and retention.

## Lab boundaries

- Quotas/screening are per-server policy; no central reporting in this lab.
- Shadow copies are per-volume; plan capacity before enabling on a full volume.
- Do not present previous versions as disaster recovery.

## Sources

- [Microsoft Learn — FSRM overview](https://learn.microsoft.com/en-us/windows-server/storage/fsrm/fsrm-overview)
- [Microsoft Learn — Shadow Copies](https://learn.microsoft.com/en-us/windows-server/storage/file-server/volume-shadow-copy-service)
- [Microsoft Learn — FSRM quota commands](https://learn.microsoft.com/en-us/powershell/module/fileserverresourcemanager/new-fsrmquota)

---

Source: https://winbook.fyi/en/server/roles/file-server-quotas/