How do ZBS and SFS work together within SmartX Enterprise Cloud Platform?

Deep Analysis

Understanding how ZBS and SFS complement each other helps architects design comprehensive storage solutions.

ZBS: Distributed Block Storage

Core Capabilities

• Protocols: iSCSI and vhost
• Deployment: VMs, containers, and physical machines
• Architecture: Distributed across cluster nodes
• Use Cases: Databases, critical applications, container persistent storage

ZBS Features

• Volume Pinning: Prevent data sinking for guaranteed performance
• I/O Localization: Prioritize local I/O for lower latency
• RDMA Support: High-speed data transfer
• EC Support: 28 erasure coding combinations

SFS: SMTX File Storage

Core Capabilities

• Type: Distributed file storage
• Protocol: Enterprise file access
• HA: HA for file access IPs
• Multi-Path: Multiple access IP paths for file systems

SFS Features

• File Controller HA: Ensures business continuity
• Online/Offline Management: Server-side file system control
• Multi-Path Mounting: Load balancing and failover for file access
• Integration: Works with ZBS for underlying storage

How They Work Together

Shared Infrastructure

• Same Platform: Both ZBS and SFS run on SmartX ECP
• Shared Hardware: Cluster nodes serve both block and file workloads
• Unified Management: Single management interface for all storage

Complementary Workloads

• Block Workloads: Database VMs, critical business applications
• File Workloads: File shares, container image registries, logging
• Dynamic Allocation: Storage resources allocated based on need

Deployment Options

Hyperconverged with ELF

• Native Hypervisor: SmartX ELF for optimal integration
• Performance: Best performance with ELF+ZBS+SFS
• Simplicity: Single vendor for entire stack

Hyperconverged with VMware ESXi

• Alternative: VMware ESXi as hypervisor option
• Flexibility: For shops already invested in VMware
• Feature Parity: Most ZBS/SFS features available

Use Case Examples

Virtual Desktop Infrastructure (VDI)

• Boot Volumes: ZBS for high-performance boot disks
• User Profiles: SFS for shared profile storage
• Benefit: Fast boot times + shared access

Database + Application Stack

• Database: ZBS block storage for database volumes
• Shared Files: SFS for application binaries and logs
• Benefit: Optimized storage for each workload type

Container Platform

• Persistent Volumes: ZBS for database containers
• Image Registry: SFS for container image storage
• Benefit: Persistent storage + shared file access

Management Integration

Unified Storage Management

• Single Interface: SmartX ECP management console
• Storage Policies: Consistent policy framework
• Monitoring: Integrated observability for both block and file

Resource Efficiency

• Shared Pool: Block and file share underlying storage pool
• Dynamic Tiering: Hot/cold data tiering across workloads
• Thin Provisioning: Efficient capacity utilization

Why This Integration Matters

• Simplified Operations: One platform for block and file storage
• Cost Efficiency: Shared hardware reduces total cost
• Performance Optimization: Right storage type for each workload
• Future-Proof: Scale storage independently as needs grow