Search Results

Volumes can have an upper (faster) tier that writes land on first, with StorONE evacuating cold data down to the base pool as the upper tier fills up. That per-volume tier is sized when you create or edit the volume. This chapter covers the other half of tieri...

An application is a logical namespace for grouping the volumes that belong to a single workload — for example, a database and its transaction log, or every volume backing a particular VMware datastore. Applications don't consume storage themselves; they're an ...

A volume is the actual unit of storage StorONE presents to the outside world — as a block device (iSCSI, Fibre Channel, NVMeOF), a file share, or an object store. Every volume lives inside an application and is built from the underlying drive pools using StorO...

A physical drive goes through a simple lifecycle in StorONE: when it's first installed it shows up unapproved (StorONE has detected it but isn't using it yet); you approve it to put it to work in a pool; if it's later removed or stops responding it's declared ...

A drive enclosure is the physical chassis or JBOD that houses a set of drive bays (slots). Where the Drives page deals with individual drives, this page deals with the enclosure itself — its slot layout, and which drive (if any) sits in each slot. This is main...

StorONE hosts connect to volumes over the network — iSCSI or NVMeOF — using the IP addresses configured on the system's network interface cards (NICs). By default, a newly configured IP isn't enabled for either protocol; you turn on the protocol(s) you need on...

An NVMeOF enclosure is an external drive shelf that exposes its drives over NVMeOF instead of being directly, locally attached to a StorONE node. StorONE connects out to it as a client (an NVMeOF initiator) over one connection per node, and once connected, the...

Resources is the physical/infrastructure layer of a StorONE system: the drives, the drive pools built from them, the enclosures the drives sit in, and the network interfaces the system uses to talk to hosts and to other nodes. Everything in the Applications & ...

A drive pool is a group of drives that StorONE spreads a volume's erasure-coded data across. Every volume lives on at least one pool (see Volumes), so before you can create your first volume, you need at least one pool with approved drives in it. StorONE maint...

A self-encrypting drive (SED) encrypts everything written to it in its own hardware, and needs a password before it will unlock and expose its data. This page covers the SED-specific parts of the drive lifecycle: finding out which of your drives support it, se...

Encrypting a volume is something you configure once, at the moment you create it — see Encryption under Creating a volume for supplying an encryption key and saving a recovery copy. This chapter covers what comes after that: unlocking an encrypted consistency ...

This page covers checking on the state of your replicated volumes and promoting a secondary volume to primary — the operation you'd use for a planned failover, a DR test, or a real recovery after losing the primary system. See Replication for what primary/seco...

A replication IP is an address StorONE uses only for replication traffic between two systems — it's kept separate from the floating IPs your hosts and clients connect to, so replication traffic has its own dedicated path and doesn't compete with or get exposed...

Normally, promoting a secondary volume to primary is something you do deliberately, by hand, after confirming the primary side is actually down. The replication witness is an optional arbitration service that continuously monitors both systems in a replication...

Replication keeps a copy of a volume's data continuously up to date on a second, independent StorONE system, so a usable copy of your data exists somewhere else entirely — a different array, a different room, a different site. It's how StorONE provides disaste...

This page covers the commands that create, adjust, and tear down a replication pairing: starting replication on a volume, changing a pairing's protocol, pausing and resuming, and stopping replication entirely. For background on what replication does, see Repli...

Snapshots let you restore an entire volume back to an earlier point in time, but sometimes you only need to know what happened to a single file — when it was created, changed, renamed, or deleted, and which snapshots contain which version of it. SnapONE is Sto...

A snapshot is a point-in-time copy of a volume — or, more precisely, of the volume's entire consistency group (CG), so that every volume sharing a CG is always captured at the same instant. Snapshots are near-instantaneous and space-efficient: StorONE only sto...