NetApp ONTAP Operator: full volumes, snapshots and SnapMirror lag

2501's NetApp ONTAP Operator investigates full volumes and SnapMirror lag, manages snapshots within policy and grows volumes, without deleting data or breaking replication.

REQUEST DEMO

READ THE DOCS

NetApp ONTAP Operator is 2501's specialty for NetApp storage: it investigates capacity alerts, manages snapshots within your policies, checks SnapMirror replication and handles routine volume work, without deleting data or breaking replication.

A volume alert fires at 2 AM, or replication falls behind schedule. Before anyone frees space, someone has to work out where it really went, without touching a snapshot that disaster recovery depends on.

What 2501 does

The NetApp ONTAP specialty takes these alerts and requests from your ticketing system. It works out whether space is going to user data, snapshots or overhead, since each needs a different fix. Where you allow it, it grows a volume that has room to grow, takes a snapshot on request, or updates replication when asked. Replication lag is a disaster-recovery warning to explain, never to silence. What it will not do alone comes back as findings and a recommended next step.

Scope map of 2501's NetApp ONTAP Operator: it works out whether space went to user data, snapshots or overhead, grows volumes with room to grow, takes snapshots on request, explains replication lag and updates replication when asked; taking a volume offline, adding a snapshot policy, resyncing and breaking replication need a person, and it never shrinks or destroys a volume or deletes a snapshot replication depends on.

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.
Data and replication come first: it never shrinks or destroys a volume, never deletes a snapshot that replication depends on, and never breaks replication without explicit approval.
Disruptive steps wait for a person: taking a volume offline, resynchronising replication or adding a snapshot policy needs confirmation, 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

Does it work with Amazon FSx for NetApp ONTAP? Yes. 2501 supports FSx for NetApp ONTAP as well as ONTAP clusters in your own data centre.

Will it delete snapshots to free space? Only when space pressure truly requires it, never one that replication depends on, and it never switches a snapshot policy off to clear an alert.

Problems it handles

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

A NetApp ONTAP volume filled by user data, snapshots and overhead gets room back after 2501 works out where the space went and grows the volume while leaving the aggregate headroom, deleting no snapshot replication depends on

Problem

NetApp ONTAP volume full

Deleting snapshots frees a full NetApp volume fast, and the wrong one can break SnapMirror replication. How 2501 finds where the space went and fixes it within your limits.

See how it is handled

NetApp ONTAP Operator: full volumes, snapshots and SnapMirror lag

What 2501 does

You stay in control

Frequently asked

Related

Problems it handles

SEE IT ON YOUR OWN INFRASTRUCTURE