VMware Datastore Operator: datastore space, snapshots and orphaned files

2501's VMware Datastore Operator investigates full vSphere datastores, removes the snapshots your policy allows, finds orphaned files and reports the space it freed.

REQUEST DEMO

READ THE DOCS

VMware Datastore Operator is 2501's specialty for vSphere datastore capacity: it investigates why a datastore is filling, removes the snapshots your policy says can go, and finds files left behind by virtual machines that no longer exist. Then it reports the space recovered.

A datastore crosses its threshold and every machine on it is exposed: new snapshots can fail and disks cannot grow. The usual causes are forgotten snapshots and folders nobody remembers, found by hand one machine at a time.

What 2501 does

The VMware specialty takes datastore alerts and cleanup requests from your ticketing system and works through 2501's VMware plugin. It finds snapshots that are old, large or stacked too deep, and removes the ones your policy allows once each machine is safe to work on. It works in small batches, confirms the space came back, and escalates when it did not. Files that look orphaned are reported with their size and kept until their status is confirmed.

Scope map of 2501's VMware Datastore Operator: it checks each virtual machine is safe to work on, removes old, large or deeply stacked snapshots your policy allows in small batches, confirms the datastore space that came back and reports orphaned files with their size; protected snapshots, exceptions, space that did not come back and a datastore too full to clean up go to a person.

You stay in control

You choose the level, per specialty: investigate only, act after a person confirms, or act on its own within your rules.
Its authority is narrow: reading the estate and managing snapshots, and an account that cannot delete a machine will not delete one.
Your snapshot policy decides what may be removed. Protected snapshots and exceptions are left for a person, and destructive commands can be blacklisted outright.
On-prem, cloud or hybrid: 2501 runs wherever you do. On-prem, no data leaves your network.

Frequently asked

Do we register every ESXi host in 2501? No. One agent reaches the whole estate through the VMware plugin.

What if the datastore is too full to clean up? Removing a snapshot needs free space to merge it back. When there is too little, it flags the datastore for a person to move machines elsewhere.

Problems it handles

Each page is one kind of ticket, and how this specialty handles it within the limits you set.

A VMware datastore filled by old snapshots and folders left by removed machines gets space back after 2501 removes the snapshots your policy allows in small batches, keeping anything that only looks orphaned

Problem

VMware datastore full

Deleting the biggest files is the quick fix for a full datastore. How 2501 removes only the snapshots your policy allows and keeps files that only look orphaned.

See how it is handled

VMware Datastore Operator: datastore space, snapshots and orphaned files

What 2501 does

You stay in control

Frequently asked

Related

Problems it handles

SEE IT ON YOUR OWN INFRASTRUCTURE