Skip to main content
Pure Technical Services

Cloud Block Store Support Matrix for Azure

Currently viewing public documentation. Please login to access the full scope of documentation.

Cloud Block Store Models and Capacity Points 

The table below reflects the major resources of a single Cloud Block Store managed application. Clock Store Block Store does use other Azure native services but are not listed in the table b/c the costs associated are minimal. They include Azure Key Vault, Cosmos DB, Load Balancers, network interfaces, Azure Identities, etc.

Each row reflects the overall configuration at each capacity point. Notice that each capacity NDU will replace the existing disk with larger disks. 

For more detailed information about all the underlying components, see the Cloud Block Store Architecture & Underlying Resources article.

Model: V10MU-R1

Total Usable Capacity

Total Effective Capacity (4:1)

Total Number of Controller VMs

Total Number of Azure Managed Disks for Persistent Storage

Total Number of disk for NVRAM

2.25 TiB

(2.47TB)

9 TiB

(9.88 TB)

2 x D32s_v3

 

14 x 256 GiB Ultra SSD

2,857 IOPS per disk*

55 MB/s per disk*

2 x 64 GiB Ultra SSD

5,000 IOPS per disk*

150 MB/s per disk*

4.65 TiB

(5.1 TB)

18.6 TiB

(20.5 TB)

2 x D32s_v3

14 x 512 GiB Ultra SSD

2,857 IOPS per disk*

55 MB/s per disk*

2 x 64 GiB Ultra SSD

5,000 IOPS per disk*

150 MB/s per disk*

9.45 TiB

(10.4 TB)

37.8 TiB

(41.6 TB)

2 x D32s_v3

14 x 1 TiB Ultra SSD

2,857 IOPS per disk*

55 MB/s per disk*

2 x 64 GiB Ultra SSD

5,000 IOPS per disk*

150 MB/s per disk*

 

 

Model: V20MU-R1

Total Usable Capacity

Total Effective Capacity (4:1)

Total Number of Controller VMs

Total Number of Azure Managed Disks for Persistent Storage

 

Total Number of disk for NVRAM

4.65 TiB

(5.1 TB)

18.6 TiB

(20.5 TB)

2 x D64s_v3

14 x 512 GiB Ultra SSD

5,714 IOPS per disk*

86 MB/s per disk*

2 x 64 GiB Ultra SSD

15,000 IOPS per disk*

450 MB/s per disk*

9.45 TiB

(10.4 TB)

37.8 TiB

(41.6 TB)

2 x D64s_v3

14 x 1 TiB Ultra SSD

5,714 IOPS per disk*

86 MB/s per disk*

2 x 64 GiB Ultra SSD

15,000 IOPS per disk*

450 MB/s per disk*

19.05 TiB

(20.95 TB)

76.2 TiB

(83.8 TB)

2 x D64s_v3

14 x 2 TiB Ultra SSD

5,714 IOPS per disk*

86 MB/s per disk*

2 x 64 GiB Ultra SSD

15,000 IOPS per disk*

450 MB/s per disk*

28.65 TiB

(31.51 TB)

114.6 TiB

(126.1 TB)

2 x D64s_v3

14 x 3 TiB Ultra SSD

6,144 IOPS per disk*

86 MB/s per disk*

2 x 64 GiB Ultra SSD

15,000 IOPS per disk*

450 MB/s per disk*

38.74 TiB

(42.62 TB)

155 TiB

(170.5 TB)

2 x D64s_v3

14 x 4 TiB Ultra SSD

8,192 IOPS per disk*

86 MB/s per disk*

2 x 64 GiB Ultra SSD

15,000 IOPS per disk*

450 MB/s per disk*

49.54 TiB

(54.5 TB)

198.2 TiB

(218 TB)

2 x D64s_v3

14 x 5 TiB Ultra SSD

10,240 IOPS per disk*

86 MB/s per disk*

2 x 64 GiB Ultra SSD

15,000 IOPS per disk*

450 MB/s per disk*

60.34 TiB

(66.38 TB)

241.4 TiB

(265.5 TB)

2 x D64s_v3

14 x 6 TiB Ultra SSD

12,288 IOPS per disk*

86 MB/s per disk*

2 x 64 GiB Ultra SSD

15,000 IOPS per disk*

450 MB/s per disk*

71.14 TiB

(78.26 TB)

284.6 TiB

(313 TB)

2 x D64s_v3

14 x 7 TiB Ultra SSD

14,336 IOPS per disk*

86 MB/s per disk*

2 x 64 GiB Ultra SSD

15,000 IOPS per disk*

450 MB/s per disk*

81.94 TiB

(90.14 TB)

327.8 TiB

(360.5 TB)

2 x D64s_v3

14 x 8 TiB Ultra SSD

16,384 IOPS per disk*

86 MB/s per disk*

2 x 64 GiB Ultra SSD

15,000 IOPS per disk*

450 MB/s per disk*

92.74 TiB

(102.02 TB)

371 TiB

(408.1 TB)

2 x D64s_v3

14 x 9 TiB Ultra SSD

18,432 IOPS per disk*

86 MB/s per disk*

2 x 64 GiB Ultra SSD

15,000 IOPS per disk*

450 MB/s per disk*

103.54 TiB

(113.9 TB)

414.2 TiB

(455.6 TB)

2 x D64s_v3

14 x 10 TiB Ultra SSD

20,480 IOPS per disk*

86 MB/s per disk*

2 x 64 GiB Ultra SSD

15,000 IOPS per disk*

450 MB/s per disk*

114.34 TiB

(125.78 TB)

457.4 TiB

(503.1 TB)

2 x D64s_v3

14 x 11 TiB Ultra SSD

22,528 IOPS per disk*

88 MB/s per disk*

2 x 64 GiB Ultra SSD

15,000 IOPS per disk*

450 MB/s per disk*

125.14 TiB

(137.66 TB)

500.6 TiB

(550.6 TB)

2 x D64s_v3

14 x 12 TiB Ultra SSD

24,576 IOPS per disk*

96 MB/s per disk*

2 x 64 GiB Ultra SSD

15,000 IOPS per disk*

450 MB/s per disk*

* The IOPS per disk  and MB/s refer to the number of provisioned IOPS and throughput for each Ultra SSD disk. These values do not reflect the total effective IOPS available from Cloud Block Store.

** Pure strongly recommends using Convertible Reserve Instances (rather than On-demand or Standard Reserve) for the underlying controller VMs. This allows customers the flexibility to NDU to newer, cheaper, and more powerful VM types when made available by Azure.   

Supported Regions 

  • Central US
  • East US
  • East US 2
  • South Central US
  • West US
  • West US 2
  • Canada Central
  • North Europe
  • West Europe
  • France Central
  • Germany West Central
  • UK South
  • Japan East
  • Southeast Asia
  • Australia East

 

Supported Capabilities and Features  

Feature/Capability Support Notes
Terraform Deployment Yes Sample Files
Shut down or Stop No Stopping or Shutting down (suspend/resume feature) Cloud Block Store or its underlying resources is only supported currently with the CBS offering on AWS. Suspend/resume for CBS on Azure is under consideration.
Cloud Block Store termination/deletion

Yes, using proper Purity CLI commands

Customer should follow proper procedures to delete a CBS managed app to ensure it is cleanly removed both from Azure and Pure1. See CBS Deployment Guide for steps to terminate/delete a CBS instance.

Host ports 2 (iSCSI)  One per controller.
Replication ports 2 One per controller.
Management ports 2 One per controller.
System ports 2 One per controller. Used to send phone home information to Pure1.
Deduplication Yes  
Compression Yes  
Thin Provisioning Yes  
Snapshots Yes  
CloudSnap creation Yes  
CloudSnap restore Yes  
Snap to NFS No  
Safemode Yes  
QoS (Fairness) No  
QoS (Limits) Yes  
Purity Run No  
WFS No  
Encryption Yes  
REST APIs Yes  
Controller SW NDU (Purity code) Yes  
Controller HW NDU No
  • Non disruptive upgrade for Purity version (controllers) fully supported.
  • Non disruptive upgrade from V10 to V20 is supported using ActiveCluster.
Capacity NDU Yes Support Driven via CLI commands.
Pure1 Yes  
Pure1 Meta (Workload Planner) No  
VM Analytics N/A No VMware Cloud support for CBS.
Azure VMware Service No  
Changing Network IP or subnets No This is an Azure limitation.
Boot from CBS No This is an Azure limitation. VMs are only allowed to boot from native Azure storage.

 

Replication Features Support Notes

Async Replication

 

 

Yes

  • Bi-directional supported between two CBS instances in different AZs or regions.
  • Bi-directional supported between CBS instances and FlashArray.
  • Azure network charges may apply for replication across Availability Zones, VNETs, and/or regions.
  • Egress charges may apply for any data that sent from Cloud Block Store to FlashArray.
Active Cluster (Synchronous Replication) 

Yes

  • Bi-directional supported between two CBS instances in different AZs.
  • Bi-directional supported between two CBS instances cross-clouds.
  • Azure network charges may apply for ActiveCluster configurations across Availability Zones and/or VNETs.
  • For cross-cloud deployments consider the maximum latency not to exceed 11 ms RTT.
  • Minimum Purity version to support cross-cloud on CBS: 6.1.6 or later.
  • ActiveCluster between regions not supported due to latencies between regions.
ActiveDR

Yes

  • Bi-directional supported between two CBS instances in different AZs or regions.
  • Bi-directional supported between two CBS instances cross-clouds.
Minimum Purity version on CBS: 6.1.6 or later.

//V10MU-R1 Limits 

Host Limits 

Description

6.1.x

Max # of hosts

50
Max # of LUNs (volumes) per host 500
Max # of private LUNs connected per host (LUNs not connected to host groups) 500

 

Host Group Limits 

Description

6.1.x
Max # of hosts per host group 50

Max # of LUNs (volumes) per host group

500

Note: Private LUN connections count against host group max LUN limit. 

 

Volume Limits 

Description 6.1.x
Max # of volumes  500
Max volume size 4PB

 

Snapshots and Asynchronous Replication Limits 

Description

6.1.x
Max # of volume snapshots per array1 10,000
Max # of pgroups per array1 250
Max # of pgroup snapshots per array1 3,000
Max # of remote connected arrays 1
Minimum configurable replication frequency2

1 hour

1 Example for pgroup and snapshot limits: If you create a pgroup containing 100 volumes and then create a single pgroup snapshot for that pgroup then the following would be counted against each maximum:

  • 1 pgroup consumed from the array-wide maximum number of pgroups.
  • 1 pgroup snapshot consumed from the array-wide pgroup snapshot maximum.
  • 100 volume snapshots consumed from the array-wide volume snapshot maximum.

Note: In cases where a pgroup snapshot request will result in more volume snapshots than are supported by the CBS managed application, the pgroup snapshot request and/or scheduled pgroup snapshot will fail. 

2 This is the minimum configurable replication frequency. Replication is a background process and priority is given to front-end workload. Maintaining the configured replication frequency depends on several factors such as the front-end workload on the array, the amount of data reduction, the amount of logical address space being replicated, and the available replication bandwidth.

 

ActiveCluster Limits 

Description

6.1.x
Max # of Pods 20
Max # of Stretched Pods 10
Max # of Stretched Volumes 250

 

Snapshot Offload (NFS/Cloud) Replication Limits 

Description

6.1.x

Max # of volume snapshots on an offload target

50,000
Max # of offload targets configurable per FlashArray 1
Max # of FlashArrays configurable per offload target 4

 

 

//V20MU-R1 Limits 

Host Limits 

Description

6.1.x

Max # of hosts

50
Max # of LUNs (volumes) per host 500
Max # of private LUNs connected per host (LUNs not connected to host groups) 500

 

Host Group Limits 

Description

6.1.x

Max # of hosts per host group

50

Max # of LUNs (volumes) per host group

500

Note: Private LUN connections count against host group max LUN limit. 

 

Volume Limits 

Description 6.1.x
Max # of volumes 1000

Max volume size

4PB

 

Snapshot and Asynchronous Replication Limits 

Description

6.1.x

Max # of volume snapshots per array1

20,000
Max # of pgroups per array1 250
Max # of pgroup snapshots per array1 5,000
Max # of remote connected arrays 4
Minimum configurable replication frequency2

30 minutes3

1 Example for pgroup and snapshot limits: If you create a pgroup containing 100 volumes and then create a single pgroup snapshot for that pgroup then the following would be counted against each maximum:

  • 1 pgroup consumed from the array-wide maximum number of pgroups.
  • 1 pgroup snapshot consumed from the array-wide pgroup snapshot maximum.
  • 100 volume snapshots consumed from the array-wide volume snapshot maximum.

Note: In cases where a pgroup snapshot request will result in more volume snapshots than are supported by the FlashArray,  the pgroup snapshot request and/or scheduled pgroup snapshot will fail. 

2 This is the minimum configurable replication frequency. Replication is a background process and priority is given to front-end workload. Maintaining the configured replication frequency depends on several factors such as the front-end workload on the array, the amount of data reduction, the amount of logical address space being replicated, and the available replication bandwidth.

 

ActiveCluster Limits 

Description

6.1.x
Max # of Pods 20
Max # of Stretched Pods 10
Max # of Stretched Volumes 500

 

Snapshot Offload (NFS/Cloud) Replication Limits 

Description

6.1.x

Max # of volume snapshots on an offload target

50,000
Max # of offload targets configurable per FlashArray 1
Max # of FlashArrays configurable per offload target 4