Please enable JavaScript.
Coggle requires JavaScript to display documents.
VMC - Coggle Diagram
VMC
Storage
FSx NetApp ONTAP
- Fully featured NetApp ONTAP
- Concurrent multi-protocol access: NFS, SMB, iSCSI
- Snapshot / Cloning (FlexClone)
- Replication (SnapMirror)
- Storage efficiency capabilities:
- deduplication
- compression
- compaction
- thin provisioning
- cloud tiering
- Supplemental NFS Datastore support for VMC
- Jointly engineered by VMware and AWS
- Outcome:
- NFS Datastore support
- 4 Datastore per cluster (in addition to those 2 default provided)
- NFS Cloud Certification program
- Amazon FSx NetApp ONTAP
- API and UI integration
- Benefit
- Right size storage to control cost
- Full acces to ONTAP's enterprise data management
- Accelerate migration - rehost on AWS without changing code or how you manage data
Amazon FSx for NetApp ONTAP
- AWS managed service built on NetApp ONTAP
- Up to 192TiB Flash Capacity
- Throughput up to 2GB/s per filesystem
- 99.99% Availability
- Filesystem:
- SSD storage capacity 1024GiB ÷ 192 TiB
- IOPS up to 80000
- Throughput capacity 128 Mbps ÷ 2048 Mbps
- SVM (Storage Virtual Machine) endpoint for datastore connection
- Volume - Datastore
- VMware Transit Connect (for use as VMC Datastore) - implies data processing fees -->CHECK<--
- Datastore mapping to Filesystem:
- 1:1
- 1:M - achieve higher IOPS or support different filesystem requirements
nConnect
Challenges:
- Only one NFS session across a single TCP session
- Instance bandwidth limitation of 5 Gbps per ESXi host
Features:
- NFS mount option
- Provides multiple (up to 16) transport connections per TCP
- Requires ONTAP 9.8 or greater
- nConnect with VMC today support up to 4 connections per TCP
- Queue depth limit:
- Single connection has 128 limit
- nConnect with VMC has 128 x 4= 512 limit
Operations:
- Enabled by default
- Managed by VMware
Limitations
-->CHECK<--
Throughput
Datastore throughput
- Each vSphere host has a dedicated connection to each datastore
- AWS limits each connection to ~ 450-500MB/s
Host throughput
- Multiple Datastores can be attached to a single host to overcome this situation
Cluster throughput
- Is the host throughput multiplied by the number of hosts
Supportability
- Connected VPC not supported for FSx for NetApp deployment
- Only multi-AZ deployments of FSx for NetApp supported
- VMC single-AZ cluster support only
- Up to 4 FSx for NetApp volumes attached to a single vSphere cluster
- No initial support for VAAI (VAAI allows to offloaded some operations)
- FSx for NetApp volumes not supported as destination for SRM and VCDR
Sizing
Required metrics:
- Storage capacity: overall capacity within the FSx for NetApp filesyetm and split between SSD and Capacity (e.g. 20%/80%)
- IOPS: using User Provisioned Mode, FSx scales with 3 SSd IOPS per GiB in Provisioned IOPS
- Throughput capacity: 128-2048 Mbps
Using RVTools
- Keep higher IO workloads (e.g. DB) on vSAN
-Estimate TGW cost: VMware suggest to use at least 35% of used storage capacity (not allocated) to estimate data transit
- Estimate IOPS:
- Use 0.5 IOPS per GB for an average workload
- Use 3 IOPS per GB for high transaction/database workloads
VMC Flex Storage
Why External Storage
- Hyperconverged sizign is basd on the most used resource
- Storage bound workload end up with a lot of hosts with unused CPU/Memory
- Independent scaling of storage capacity
- Ideal for higher capacity workloads (go to vSAN for performance and consistent latency)
- VMware Cloud Flex Storage
- Scalable & Elastic
- Simplified: you just add an NFS Datastore from the UI
- Predictable Cloud Economics: there is no variability of cost over time
Need to Know for Pricing
- Min 25TiB required, or customer charged min 25TiB regardless of usage
- No TGW required
- Pay only for the storage you use under a simple $ per GB pricing model.
Key Features
- VMware maanged NFS storage for VM
- Log-Structure Filesystem (LFS) with 2 Tier design:
- NVMe for Cache with optimized capacity pricing
- Low latency writes
- Variable latency reads
- S3 for Capacity
- Compliments with vSAN (do not replace it)
- Single AZ (no stretched clusters CHECK)
- Lives in a VMware managed VPC single tenant per customer
-