Advanced Search
Search Results
369 total results found
Anomaly Detection reference architectures
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...
Responding to an anomaly notification
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...
Setting up Anomaly Detection
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...
Troubleshooting Anomaly Detection
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...
StorONE on Azure
Deploying StorONE on Azure
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 and best practices for StorONE on Azure
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 Microsoft Azure
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...
Example: disaster recovery to Azure
This example replicates the volume finance/db01 from an on-premises system, onprem-1, to a StorONE system on Azure, azure-dr. The primary copy stays on premises; the Azure copy is promoted only if the primary site is lost. The steps are: Before you begin, d...