Search Results

These endpoints mirror the CLI commands described in Software updates, License. Each endpoint runs the CLI command named under its heading, so the behavior, defaults, and restrictions are the same; this page lists how to call it over REST. Conventions that app...

These endpoints mirror the CLI commands described in Systems. Each endpoint runs the CLI command named under its heading, so the behavior, defaults, and restrictions are the same; this page lists how to call it over REST. Conventions that apply to every endpoi...

These endpoints mirror the CLI commands described in Tiering. Each endpoint runs the CLI command named under its heading, so the behavior, defaults, and restrictions are the same; this page lists how to call it over REST. Conventions that apply to every endpoi...

These endpoints mirror the CLI commands described in Users, Permission policies. Each endpoint runs the CLI command named under its heading, so the behavior, defaults, and restrictions are the same; this page lists how to call it over REST. Conventions that ap...

These practices help you get the protection you expect from Multi-Admin Approval, without it getting in your own way. Choosing policies Protect the policies first. Create the Action Policy Delete and Action Policy Edit policies before the others, so the prot...

This page shows how to put Multi-Admin Approval in place on a system: which policies to create, how to lay them out so the protection can't be undone by one administrator, an example with three administrators, and the steps to set it up. For the details of eac...

Multi-Admin Approval makes sure that sensitive operations on a StorONE system only run after several authorized administrators agree to them. No single administrator account can carry out a protected operation alone: the operation is recorded as a pending acti...

This page lists the messages you may see while working with Multi-Admin Approval, what each one means, and what to do. It ends with answers to common questions about how the workflow behaves. When a request is refused "Cannot perform this action because it aff...

Two numbers control Anomaly Detection: the timeframe and the change percentage. The right values depend on how regular your workload is. This page explains how to choose them, gives starting points by workload, shows worked examples, and ends with practices th...

Anomaly Detection runs two independent detectors on the statistics StorONE already collects. Both use the same two settings. This page explains what each detector measures, how it decides that something is abnormal, when it runs, and what you get when it fires...

StorONE continuously collects capacity and performance statistics for your drive pools and volumes. Anomaly Detection uses those statistics to learn what normal usage looks like on your system, and when today's activity is far outside the recent history, it se...

Anomaly Detection is configured the same way everywhere, but where its notifications go, and what surrounds it, changes with the size and needs of your environment. These four architectures cover the common cases. Pick the one closest to yours and adapt it. Ar...

An anomaly notification is a prompt to investigate, not proof of an attack. This page explains how to read one, and gives a response playbook you can adapt into your own runbook. Reading a notification A pool notification Drive pool <name> has abnormal capacit...

This page takes you from nothing to a working setup: preparing the notification path, enabling Anomaly Detection, checking that it works, and changing or disabling it later. You can do the same in the web interface, the CLI, and the REST API. Prerequisites Ite...

Common questions about Anomaly Detection, and what to do when it doesn't behave the way you expect. settings anomaly_detection show returns "Not configured" The feature was never set on this system. Configure it with settings anomaly_detection edit; see Setti...

Deploying takes four steps: create the virtual machine, optionally set up a floating IP, boot it, then configure storage. Prerequisites An Azure virtual network that can reach your on-premises StorONE system, through a VPN or ExpressRoute, when the Azure syste...

Limitations Limitation Detail Single node One node only; HA pairs aren't supported on Azure. A node configured for HA won't start. Floating IP addresses An address must first be configured on the VM's network interface in Azure. StorONE doesn't create addresse...

StorONE on Azure (S1:Azure) is the StorONE storage engine running on a Microsoft Azure virtual machine, using Azure managed disks as its drives. It's typically used as a replication target for your on-premises StorONE systems, so a current copy of your data li...