Search Results

An automation workflow is a saved, named sequence of StorONE CLI commands that you can run as a single unit, as many times as you like, instead of typing (or scripting) each command individually. It's built for repeatable, multi-step procedures — provisioning ...

A scheduled report emails the output of up to six List commands — the same read-only commands you'd otherwise run yourself and read on screen — to a set of recipients on a recurring schedule. Use it to keep stakeholders who don't log into StorONE up to date: ...

An action policy tells StorONE that a particular kind of operation needs the approval of several administrators before it runs. This page covers creating, editing, listing, and deleting policies. For the big picture, see Multi-Admin Approval; for a complete, r...

When an action policy is in place for an operation, performing that operation doesn't happen immediately — it creates a pending action instead, which sits waiting for review until enough of the policy's authorized reviewers approve it. How approval works Initi...

StorONE's monitoring commands give you both a live view of what the system is doing right now and a historical view of how it got there — health, capacity, performance, utilization, and tiering, at the system, pool, node, application, or volume level. Most mon...

Where the live monitoring views show what's happening right now, these views look backward — performance and utilization trends over a date range, which volumes have been busiest, and exactly how much physical space each volume is really reserving. For the two...

These views show what StorONE is doing right now. In an interactive CLI session they stream continuously — refreshing on the configured interval — until you press a key to stop; the web interface shows the same data as a live-updating chart. When called non-in...

Volumes with an upper (autotiering) tier evacuate the coldest data down to the lower tier once the upper tier's pinned size is exceeded — see the Tiering chapter for how tiers are configured. These three views let you watch that evacuation happen live, review ...

Every StorONE node keeps its own local history of the notifications it has generated, independent of whether you've configured any notification targets to receive them. This is useful for after-the-fact investigation — for example, confirming when a Replicatio...

StorONE watches its own health continuously — hardware, replication, capacity, security, and more — and raises notifications when something changes state or needs attention. A notification target tells StorONE where to send those notifications: an email inbox,...

Every change you make to a system — creating a volume, editing a schedule, deleting a user, and so on — is tracked as a configuration. This chapter covers viewing that history and, for scripting, waiting on configurations to complete. Configuration history Con...

Every StorONE system runs against a license that determines what capacity and features are available. This chapter covers viewing your current license details and uploading a new license file — for example, after a capacity or feature entitlement change from S...