+1 855.EXABLOX (855.392.2569) Japanese Version
Yes, VMware is supported for use with OneBlox. OneBlox 4312 is VMware Ready and may be used as an NFS Datastore with vShpere ESXi 5.5 and 6.
No. All of the information stored in a OneBlox Ring is on the customer’s premises. OneSystem has a global view and enables proactive monitoring, reporting, and management, but DOES NOT store any customer data in the cloud. For those organizations that require on-premises management, Private OneSystem is a deployment option.
Yes. OneBlox’s inline deduplication is at the global file system level. OneBlox offers variable-length and fixed-length deduplication. All primary information and snapshots are deduplicated across all shares with variable-length deduplication enabled within a OneBlox Ring to maximize storage utilization. Similarly for all shares within a OneBlox that have fixed-length deduplication enabled. Moreover, there are no separate deduplication storage pools to manage.
Yes. OneBlox’s Continuous Data Protection (CDP) takes an unlimited number of snapshots to ensure information can be recovered from a few seconds ago. The snapshots capture only the parts of a file that changes so there is very little storage overhead. Additionally, all snapshots are deduplicated against the primary storage, and there isn’t a separate snapshot storage pool to manage. CDP requires zero-configuration and is enabled by default. No complex scheduling and management.
Maybe. OneSystem communicates via HTTPS over standard secure HTTP firewall port 443. If your organization enables standard HTTPS web traffic, OneSystem can securely communicate with OneBlox. If you’re company has firewall rules in place, please refer to this article on our support site for more information.
Yes. All local access to OneBlox remains intact if the internet connection is disrupted. Users can access, update information, write new information, delete, and recover all of the information stored in a OneBlox Ring without OneSystem connectivity.
OneBlox uses our own object-based file system which creates 3 copies of every data object to protect against hardware failures. OneBlox then intelligently places these data objects on different drives and/or OneBlox in a Ring. Such a copy/distribution scheme protects your data to the greatest possible extent from either 2 drive failures or even from an unlikely event of 2 OneBlox failures when you have a Ring of 3 or more OneBlox.
If a drive fails, you may remove it at anytime. If you are proactively removing a drive, ensure OneBlox is not rebalancing the information. There's an alarm declared in OneSystem when this is happening. If you have any doubt, please contact Exablox support before proactively removing any drives.
As Exablox protects against 2 drive failures, OneBlox requires at least 3 disk drives, each at least 1TB, as a minimum configuration.
For the OneBlox 4312, any SATA II/III or SAS drive that is at least 1TB and up to 8TB is supported. The 4312 fully supports up to 12Gb/sec SAS drives. For the OneBlox 3308, any SATA I/II/III or SAS drive that is at least 1TB and up to 6TB is supported. The 3308 midplane is 6Gb/sec so 12Gb/sec drives are supported, but they will auto-negotiate down to 6Gb/sec.
To date Exablox has more than 50 different manufacturer, model, capacity combinations disk drives currently used in production with OneBlox. With many PBs of customer deployed storage capacity there are many proven choices for your organization. Read more.
No. You can mix and match any speed and capacity drive in the same OneBlox and within a OneBlox Ring.
No. Since OneBlox doesn’t use legacy RAID, all drives act independently and read/write I/O requests are independently delivered to each drive. Slower drives will not degrade the performance of higher performing drives within OneBlox. With the 4312 OneBlox application performance can be maximized by utilizing high performing drives are used in all of the drive bays within the Ring.
Since OneBlox uses our own object-based file system, we forego the lengthy RAID rebuild times. OneBlox knows every object in a OneBlox Ring and knows which drive that object resides on. When a drive fails, OneBlox simply copies those objects from the other two locations to the new replacement drive. Since OneBlox isn’t limited by RAID groups, all of the drives are copying only the necessary objects and aren’t required to read every sector on the drive, calculate parity, then write the data/parity to the new drive.
No. There is no need for an spare drive to sit idle. When a drive fails, OneBlox will begin to copy the objects that were on the failed drive from other drives in the OneBlox Ring. OneBlox will automatically bring the health of the Ring back to a fully protected state by ensuring there are three copies of every object in a Ring, even without replacing the failed drive.
For NFS exports, we support more than 30+ million files in a single directory/folder. From an architectural perspective the limit is approximately 1 trillion files per directory.
For SMB shares, we support at least 1 million files in a single directory/folder. The theoretical limit is approximately 10 million.
No. We currently do not support Hyper-V. We will be supporting Hyper-V in the future.
Yes. OneBlox supports SMB 2.0, 2.1, and 3.0 and NFS v3.
RISK-FREE 30-Day Evaluation Unit. Power Meets Simplicity. At a Fraction of the Cost.Get FREE Eval