Short answer: Event-driven scanning listens to Qumulo’s change notifications and scans each new or modified file shortly after the write, on separate scan servers running your antivirus engine. Capacity depends on how many files change at peak, how long your engine needs per file, and how quickly you want results. Each scan server runs one scan per CPU core, minus two cores for the operating system.
How it works, step by step
- A client creates or modifies a file in a protected directory on Qumulo.
- Qumulo emits a change notification through its REST API. Qumulo’s notification system is designed not to drop events and to deliver them in order.
- The orchestrator receives the event and checks whether the path is protected.
- Several events for the same file within a short window are merged into one, so a file saved ten times in a row is scanned once.
- A scan job enters a queue and goes to the next available scan server.
- The scan server opens the file over SMB and calls the antivirus engine’s command-line scanner with the file’s UNC path.
- The engine scans the file and takes the action configured in its own policy: report, quarantine or delete.
The client is never blocked. The file is available immediately, and the scan follows within seconds.
Components
| Component | Role | Runs on |
|---|---|---|
| Qumulo cluster | Emits change notifications, serves files via SMB | Your cluster, Qumulo Core 6.0.0 or later |
| Orchestrator (yuzuy software) | Receives events, merges them, queues and distributes scan jobs | VM in your data center |
| Scan server (yuzuy Protection Client) | Runs scan jobs, calls the antivirus CLI | Windows Server 2012 R2 or later |
| Antivirus engine | Detection, remediation, reporting | Same server as the Protection Client |
Communication between the yuzuy software and the Protection Clients uses AMQP over TLS on TCP 5671, registration uses HTTPS on TCP 443. File access uses SMB through hidden shares that yuzuy creates with minimal permissions for a dedicated service account.
Requirements for the antivirus engine
The engine needs a command-line scanner that accepts UNC paths. Not every product has one, and some CLI scanners handle network paths poorly. Customers run the integration with CrowdStrike, ESET, Microsoft Defender, Sophos, WithSecure and Bitdefender.
Behaviour such as timeouts, archive handling, locked files and remediation is controlled by the engine’s own configuration. Results appear in the engine’s management console like any other detection.
Sizing
Three numbers decide how many scan servers you need:
- Peak change rate: files created or modified per second at the busiest time, not the daily average.
- Scan time per file: depends on the engine, file types and sizes. Measure it on a sample of your own data.
- Acceptable delay: how long a changed file may wait for its scan at peak.
Each Protection Client runs as many scans in parallel as it has CPU cores minus two. Two cores stay reserved for the operating system and the client.
parallel scans needed = peak files per second × seconds per scan
scan servers = ⌈ parallel scans needed ÷ (CPU cores per server − 2) ⌉
Illustrative example: at a peak of 10 changed files per second and 0.5 seconds per scan, you need 5 parallel scans. One server with 8 cores provides 6. Add a second server so scanning continues during maintenance or a failure.
From practice: about 3,000 user home directories are covered by 2 Protection Clients. The minimum per Protection Client is 6 CPU cores and 8 GB RAM.
Above the peak, the queue absorbs bursts. Jobs wait in order, and the delay grows until the burst passes. If the delay is regularly too long, add a Protection Client: the load spreads across all servers assigned to a cluster without further configuration.
Scope: what to protect
You can protect the whole file system or selected directories. Bulk ingest areas, such as camera dumps or instrument output with very high file counts, can be left out or assigned to dedicated scan servers. If a protected directory contains another protected subdirectory, the subdirectory is handled once, not twice.
Failure behaviour and availability
| Situation | What happens |
|---|---|
| One Protection Client fails | Running scans on it may fail; queued jobs go to the remaining clients |
| All Protection Clients fail | Jobs stay queued in the yuzuy software until a client is back |
| yuzuy software unavailable | No change notifications are received and nothing is queued; files changed during the outage are not scanned. Use hypervisor HA for the VM |
| Scan fails | No automatic retry; the failure is logged |
Logs show events that did not lead to a successful scan, so gaps can be found and closed. Log retention is 7 days by default. There is no queue on the Qumulo side: changes made while the yuzuy software is down are not scanned later.
Rollout in three steps
- Set up a Windows server with your antivirus engine and the yuzuy Protection Client. The client registers with the yuzuy software.
- Assign the Protection Client to a Qumulo cluster and choose the antivirus engine and its command-line parameters in yuzuy.
- Add the paths to protect. Start with one share, measure scan times and queue delay, then extend.
A proof of concept can run against a virtual Qumulo cluster or a section of your production system.
Anti-Virus Integration · Does Qumulo support ICAP? Antivirus scanning options for Qumulo
FAQ
How fast is a new file scanned? Within seconds when scan servers have free capacity. Events for the same file are merged for about 10 seconds first, then the job is queued.
Does each scan server need a separate antivirus license? That depends on your antivirus vendor’s licensing. yuzuy itself does not limit the number of Protection Clients.
Can I use Linux scan servers? Not today. Protection Clients run on Windows Server.
