Quotas and Automated Cleanup

Nobody set a quota on the partner folders, because nobody had asked for one. For six years that was fine. Then one partner's export job started re-sending the same file every five minutes. The disk was full by Monday, and every other partner's upload failed at once. One partner with a runaway job can fill a transfer server for everyone. Quotas are the operational answer: a ceiling per account, per partner, or per folder. That turns a disk-full outage into a single rejected upload and a polite email. Cleanup automation is the other half - removing what has served its purpose before it becomes a capacity problem. The disk will otherwise make that decision for you, all at once.

This series covers both halves as operations rather than policy. It starts with quotas as an operational control and designing quota policies partners accept. Then it covers enforcing them at the filesystem, the server, or by script, and age-based cleanup jobs that do not bite. Next comes cleaning up temporary files, partials, and orphans. Finally, it covers monitoring the quotas and the cleanup jobs themselves. The governance side - retention periods, legal holds, what must be kept - is in our retention series. This series is the machinery that carries those decisions out, with the rails on.

Articles in This Series

• Quotas as an Operational Control
  What quotas protect against, soft versus hard limits, per-user, per-partner, and per-folder scopes, and where quotas end and retention policy begins.
• Designing Quota Policies Partners Accept
  Sizing quotas from real usage, grace mechanisms, communicating limits before enforcing them, the upload-rejected experience from the partner's side, and the exceptions lane.
• Enforcing Quotas: Filesystem, Server, and Script
  This article explains filesystem quotas in plain words and server-level quotas where they exist. It covers script-based enforcement as the fallback, and the honest limits and blind spots of each approach.
• Age-Based Cleanup Jobs That Do Not Bite
  The operational patterns: dry runs, exclusions, path guards, deletion logs, and the guardrails that keep a cleanup job from becoming the deleted-inbox story.
• Cleaning Up Temp Files, Partials, and Orphans
  Abandoned partial uploads, leftover temporary names, orphaned marker files, and stale locks - detection rules, safe removal, and how old is old enough.
• Monitoring Quotas and Cleanup Jobs
  Usage-versus-quota alerts that warn before rejection, cleanup job health, the cleanup that quietly stopped running, and the quarterly quota review.

Explore More Topics

This series is part of the Sysax file transfer topic library. The library covers the protocols, security practices, automation techniques, and operational skills behind reliable file transfer. The library pairs well with the practical tools we build. Sysax Multi Server is a secure FTP, FTPS, SFTP, and HTTPS server for Windows. Sysax FTP Automation schedules and scripts secure transfers so the routine ones run themselves.