For example a pool with RAID10 layout provisioned from disks from two or more JBOD units will use the "round-robin" technique so that mirror pairs span the JBODs. If the detected number of enclosures is insufficient for JBOD fault-tolerance the disk selection algorithm switches to a sequential selection mode which groups vdevs by enclosure. This means that should a JBOD be powered off the pool will continue to operate in a degraded state. There are a number of advanced options available during pool creation but the most important one to consider is encryption as this cannot be turned on after the pool is created.Įnclosure Aware Intelligent Disk Selectionįor systems employing multiple JBOD disk enclosures QuantaStor automatically detects which enclosure each disk is sourced from and selects disks in a spanning "round-robin" fashion during the pool provisioning process to ensure fault-tolerance at the JBOD level. If you're not familiar with RAID levels then choose the RAID10 layout and select an even number of disks (2, 4, 8, 20, etc). Creating a storage pool is very straight forward, simply name the pool (DefaultPool is fine too), select disks and a layout for the pool, and then press OK. A given pool of storage can be used for SAN and NAS storage at the same time, additionally, clients can access the storage using multiple protocols at the same time (iSCSI & FC for storage volumes and NFS & SMB/CIFS for network shares). QuantaStor's SAN storage (storage volumes) as well as NAS storage (network shares) are both provisioned from Storage Pools. The amount of fault-tolerance is dependent on multiple factors including hardware type, RAID layout selection and pool configuration. The storage pool is an aggregation of one or more devices into a fault-tolerant "pool" of storage that will continue operating without interruption in the event of disk failures. One of the first steps in configuring an system is to create a storage pool. Navigation: Storage Management -> Storage Pools -> Storage Pool -> Create (toolbar) RAIDZ1/5/50 is generally not recommended because it is not fault tolerant after a single disk failure so during healing using a hot-spare the Storage Pool is exposed. With compression the usable capacity may increase to 75% of the raw capacity or higher.įor archival storage or other similar workloads RAIDZ2 or RAIDZ3 is best and provides higher usable capacity. RAID10 performs very well with sequential IO and random IO patterns but is more expensive since usable capacity before compression is 50% of the raw capacity. We strongly recommend using RAID10/mirroring for all virtualization workloads and databases and RAIDZ2/RAID60 for archive applications that require higher-capacity for applications that produce mostly sequential IO patterns. Pool RAID Layout Selection / General Guidelines For assistance in selecting the optimal layout we recommend engaging the OSNEXUS SE team to get advice on configuring your system to get the most out of it. That said, the optimal RAID type depends on the applications and workloads that the storage will be used for. Storage pools can be provisioned using using all major RAID types (RAID0/1/10/5/50/6/60/7/70) and in general OSNEXUS recommends RAID10 for the best combination of fault-tolerance and performance. From the storage pool users can provision both SAN/storage volumes (iSCSI/FC targets) and NAS/network shares (CIFS/NFS). Storage pools combine or aggregate one or more physical disks (SATA, SAS, or SSD) into a pool of fault tolerant storage.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |