C: drive full on Windows Server

When the C: drive on a Windows server fills up, the fastest space to reclaim, such as shadow copies, crash dumps and event logs, is also what a restore, a crash analysis or an audit may depend on. 2501 finds where the space went, clears only what is safe, and reports the rest for a person to decide.

Space also goes to places few people check, such as update and servicing leftovers, temporary files and the Recycle Bin.

What 2501 does

The Windows disk specialty brings the discipline used on a full Linux partition to Windows Server. It checks the drive and the disk under it and works out what is using the space before removing anything. It adapts to the server's role, since a domain controller, a database server and a web server differ in what is safe to clear, and frees the drive back below its alert threshold when that can be done safely.

Its report gives usage before and after, what each action recovered, why the space built up, and what needs an application owner, a policy change or more capacity.

You stay in control

• You choose the level: investigate only, act after a person confirms, or act on its own within your rules. The level is set per specialty, not per ticket.
• Left to a person: shrinking shadow storage and changing the page file or hibernation file.
• Logs and dumps are handled with care: it never deletes event log files directly or truncates a live log, and keeps the latest crash dump.
• Your rules apply: nothing newer than your retention period is removed, and application files wait for approval or a policy that covers them.

Frequently asked

Why not just delete the shadow copies? They often back your backup and recovery work, so shrinking their storage waits for approval.

Does it cover drives other than C:? Yes. It handles capacity alerts on any Windows Server volume, whether it holds the system, data or logs.

Related

• Disk Manager Windows
• Windows Server automation