EBC Single Tenant Storage

Storage is a fixed part of the EBC platform and it's available in a variety of storage policies representing different performance levels (tiers). Each disk assigned to a VM is linked to the desired policy at creation and in this way gets the desired performance level.

An overview of the storage policies is depicted in the table below.

Storage Policy	Tier	Use	RPO=0 Replication	IOPS / GB	Max. Performance
Ultra performance	0	Enterprise DB (Logs), AI, Machine Learning	No	15	15000 IOPS
High performance	1	DB (Logs), RDS/SBC, VDI Low latency beneficial workloads	Yes	9	8000 IOPS
Performance (default)	2	Generic VM’s, App / Web services, High performance File services / Object storage	Yes	4	2000 IOPS
Standard	3	Back-up, Generic File services / Object storage	—	1	500 IOPS

RPO=0 Replication

An option for EBC storage is that the data from one site is continuously replicated to a second location. This option is suitable where an RPO value of 0 (zero) is required. Every write to the data is immediately performed on both sites. Only when the data is written correctly on both sites, a commit takes place. In the event that the storage on site A is unavailable, the storage on site B is accessed.

File Storage Premium is only available for the High Performance and Performance Tiers. In combination with EBC ST Premium, an infrastructure can be delivered with RPO=0, and an RTO of 1 hour.

The implementation of EBC storage premium is the Active Passive variant, which means that the primary location is always site AM3, and the secondary location is ZW1. In the event of a disaster, writing and reading can take place in ZW1.

Features of EBC Single Tenant Storage

The following features apply to the use of storage policies within the EBC environment:

• Minimum recommended virtual disk size is 40 GB
• Maximum virtual disk size is 8 TB
• Performance values are limits per allocated virtual disk to a VM
• Storage capacity is allocated in multiples of 250 GB to a specific storage policy within the VDC
• Storage capacity is allocated per policy in a VDC and is not transferable to additional VDCs
• On reaching the capacity limit (agreed amount + 50% margin) of a storage policy, adjustments that require additional storage cannot be implemented

EBC Single Tenant Storage Purchase Units (PU)

EBC Single Tenant Storage is available in purchase units of 1 GB, 1 TB, >100TB or 1PB per storage policy. On the storage platform, extra capacity is reserved per policy for any additional consumption. The reservation is 50% of the number of purchased units. When ordering more than 10TB, the extra capacity is determined in consultation.

The overage storage is charged on the pay-as-you-go basis.

Purchase Unit	Tier	Calculation Type	Unit	Description
EBC Storage	Ultra performance High performance Performance Standard	Baseline	1GB 1TB 1PB	Number of PUs as agreed with the customer.
		Overage	1GB	Additional consumption above baseline.

For the RPO=0 variant, the price includes the storage on two locations, so 1GB RPO=0 includes the 1GB at AM3 and ZW1.

A Self Service module is available in Service Now to increase the number of purchase units of your settlement. The increase of the available storage according to the settlement is deployed immediately.

EBC Single Tenant Storage Consumption

To calculate shared storage, the consumption per policy and allocated capacity of all linked virtual disks is measured according to use by:

• VM swap files
• Snapshots
• File in a Library (vApp templates and ISOs)

If you want to link more than 4 TB to one or more VMs, Equinix recommends using the Equinix Managed Storage Service (EMSS). Via the EMSS, storage can be linked within the client’s VMs without the intervention of the EBC platform.

An example is the use of a virtual back-up server. Advantages may be that the EBC VM back-up does not disrupt its own back-up cycle and data is not unnecessarily duplicated. Optional snapshots or extra copies of the data stored within the EMSS service can be made available in a second site.