Skip to main content

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 addresses itself on cloud deployments. Multi-system registration A StorONE system on Azure can't register itself in multi-system management. It must be added as a remote node from an on-premises system.

Best practices

    Size the managed disks for both capacity and bestperformance practicestier, because the disk type and caching choices directly set the drive performance StorONE sees. Use the Azure system as a replication target and keep the primary copy on premises. Promote the replica on Azure only for disaster recovery. Protect against VM loss. Because there's no HA on Azure, replicate from (or back to) another StorONE system, so the data on Azure is never the only copy. Use --asynchronous replication over the WAN so production writes don't wait on the round trip to Azure. Open only the ports you need in the network security group; see Deploying StorONE on Azure.

    Troubleshooting

    "Cloud-based S1 controllers cannot be registered locally"

    You tried to register the Azure system from itself. Register it as a remote node from the on-premises system instead: systems multi_system_manager register --remoteNode <azure management IP>. See Example: disaster recovery to Azure.

    "On cloud deployments, address needs to already be configured"

    The address you tried to add in StorONE isn't configured on the VM's network interface in Azure. Add it to the interface in Azure first, then add it in StorONE.

    A node configured for HA won't start

    HA isn't supported on Azure. Deploy a single node.

    Clients can't reach the floating IP

    Check that the load-balancer VM's user data has the right public_ip, load_balancer_internal_ip, and s1_ips, and that the network security group allows TCP 18016 from the load-balancer VM to each StorONE node. See Deploying StorONE on Azure.

    See also: Overview · Floating IPs