Disk Manager LVM: safe cleanup for full LVM logical volumes

Disk Manager LVM investigates full LVM logical volumes, removes only what is safe, and says whether growing the volume is warranted, without ever growing it itself.

REQUEST DEMO

READ THE DOCS

Disk Manager LVM is the 2501 specialty for Linux disks managed by LVM. It brings Disk Manager's investigation and safe cleanup to logical volumes, within limits you set, and reports whether a volume should grow without ever growing it.

A full logical volume often sits in a volume group with free space, so extending it looks like the quick fix. But if something is filling the volume, a bigger one fills too.

What 2501 does

Disk Manager LVM reads the logical volume and its volume group as well as the files: how large the volume is and how much free space the group has. It finds what is filling the volume and why, checks that log rotation and retention are working, and removes only files that are no longer in use and clearly past retention, with your retention policies taking precedence. When safe cleanup is not enough, its report sets out what was recovered, what needs a service fix or a person's decision, and whether extending the volume is recommended, and why. The typical ticket is an LVM logical volume filling up.

Scope map of 2501's Disk Manager LVM: it reads the free space in the volume group and what fills the full logical volume, removes old files past retention and checks log rotation, and recommends whether to extend the volume; extending it, database files, application data, large live logs and recent backups and snapshots stay with a person, and storage configuration is never changed.

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.
Volumes stay yours: it never extends a logical volume or changes storage configuration. It recommends, and a person decides.
Some actions are never allowed: blacklisted commands and hosts stay out of reach, whatever a ticket asks for.

Frequently asked

How is it different from Disk Manager? The cleanup discipline is the same. Disk Manager LVM also looks at the volume and its volume group and says whether to grow it, while Disk Manager covers Linux disks in general.

What does it leave to a person? Database files and application data, large live logs, recent backups and snapshots, anything whose purpose is unclear, and any decision to grow a volume.

Problems it handles

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

An LVM logical volume filling up gets back the space that is safe to remove, while 2501 leaves database files to a person, flags runaway logging for a service fix and recommends whether to extend, never extending the volume itself

Problem

LVM logical volume full

When an LVM volume fills, extending it is the tempting fix. How 2501 frees space safely first, never grows the volume itself, and says whether growing it is warranted.

See how it is handled

Disk Manager LVM: safe cleanup for full LVM logical volumes

What 2501 does

You stay in control

Frequently asked

Related

Problems it handles

SEE IT ON YOUR OWN INFRASTRUCTURE