Join us at SC18, booth 4129 from 12th to 15th November where we’ll demonstrate how MooseFS by Tuxera reliably handles your mission-critical data, ensuring data …
November 9th, 2018Read more
No Single Point of Failure a.k.a SPOF-less configuration. Metadata of the file system is kept in two or more copies on physical redundant servers. User data is redundantly spread across the storage servers in the system.
MooseFS enables users to save a lot of HDD space maintaining the same data redundancy level. In most common scenarios you will save at least 55% of HDD space. Available from MooseFS 4.0 Pro.
Storage can be extended up to 16 exabytes (~16000 petabytes), which allows us to store more than 2 billion files.
Designed to support high performance I/O operations. User data can be read/written simultaneously on many storage nodes, thereby avoiding single central server or single network connection bottlenecks.
MooseFS is a Fault-tolerant, Highly available, Highly performing, Scaling-out, Network distributed file system. It spreads data over several physical commodity servers, which are visible to the user as one virtual disk. It is POSIX compliant and acts like any other Unix-like file system supporting:
It works with all applications that require a standard file system.Download now
You can add/remove chunk servers on the fly. But keep in mind that it is not wise to disconnect a chunk server if this server contains the only copy of a chunk in the file system (the CGI monitor will mark these in orange). You can also disconnect (change) an individual hard drive. The scenario for this operation would be:
If you have hotswap disk(s) you should follow these:
If you follow the above steps, work of client computers won't be interrupted and the whole operation won't be noticed by MooseFS users.
MooseFS does not immediately erase files on deletion, to allow you to revert the delete operation. Deleted files are kept in the trash bin for the configured amount of time before they are deleted.
You can configure for how long files are kept in trash and empty the trash manually (to release the space). There are more details in Reference Guide in section "Operations specific for MooseFS".
In short - the time of storing a deleted file can be verified by the mfsgettrashtime command and changed with mfssettrashtime.
Yes, since MooseFS 3.0.
Ability to perform one-node-at-a-time upgrades, hardware replacements and additions, without disruption of service. This feature allows you to maintain hardware platform up-to-date with no downtime.
The assignment of different categories of data to various types of storage media to reduce total storage cost. Hot data can be stored on fast SSD disks and infrequently used data can be moved to cheaper, slower mechanical hard disk drives.
All the system components are redundant and in case of a failure, there is an automatic failover mechanism that is transparent to the user.
Enhanced performance achieved through a dedicated client (mount) components specially designed for Linux, FreeBSD and MacOS systems.
Performs all I/O operations in parallel threads of execution to deliver high performance read/write operations.
Exceptional performance on almost every hardware platform that runs a POSIX compliant Operating System like Linux, Mac OSX or FreeBSD.
"We started deploying MooseFS Pro as a Distributed File System on all our storage servers.This eliminated the Single Point of Failure we previously had, as now copies of each data block resides on multiple servers. With this new storage model we not only have redundancy within...
Our core buissnes relies on MooseFS since 2005. We keep a long history of internet traffic which is more than 4 Petabytes of data as for now. Our storage grows with 300000 events as second. With MooseFS we are sure our customers get their reports on time.
M. Robak, Ph. D.
Head of IT Operations
+48 22 390 90 90