Can Petabyte Storage befault tolerant

USING COMMODITY HARDWARE?

High Availability

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.

Low-cost Data Safety

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.

Scalability

Storage can be extended up to 16 exabytes (~16000 petabytes), which allows us to store more than 2 billion files.

High Performance

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

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:

Watch a Video

Years Of Storage Experience

Minutes For Set Up

Countries

Petabytes Maximum

FAQ

Is it possible to add/remove chunkservers and disks on the fly?

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:

Mark the disk(s) for removal (see How to mark a disk for removal?)

Reload the chunkserver process

Wait for the replication (there should be no "undergoal" or "missing" chunks marked in yellow, orange or red in CGI monitor)

Stop the chunkserver process

Delete entry(ies) of the disconnected disk(s) in mfshdd.cfg

Stop the chunkserver machine

Remove hard drive(s)

Start the machine

Start the chunkserver process

If you have hotswap disk(s) you should follow these:

Mark the disk(s) for removal (see How to mark a disk for removal?)

Reload the chunkserver process

Wait for the replication (there should be no "undergoal" or "missing" chunks marked in yellow, orange or red in CGI monitor)

Delete entry(ies) of the disconnected disk(s) in mfshdd.cfg

Reload the chunkserver process

Unmount disk(s)

Remove hard drive(s)

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.

When I delete files or directories, the MooseFS size doesn't change. Why?

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.

What are limits in MooseFS (e.g. file size limit, filesystem size limit, max number of files, that can be stored on the filesystem)?

The maximum file size limit in MooseFS is 257 bytes = 128 PiB.

The maximum filesystem size limit is 264 bytes = 16 EiB = 16 384 PiB

The maximum number of files, that can be stored on one MooseFS instance is 231 - over 2.1 bln.

Does MooseFS support file locking?

Technical Features

Rolling Upgrades

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.

Tiered Storage

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.

Redundancy

All the system components are redundant and in case of a failure, there is an automatic failover mechanism that is transparent to the user.

Hardware Independence

What our clients say

Our choice for MooseFS seems a right decision as we have achieved the goal we desired – to have an infrastructure of high performance, redundancy and easy maintenance while keeping cost-efficiency in mind. I can honestly recommend MooseFS...

Justas PačekajusSystem Engineer

We have about 1000 webinars per day and of course our clients want to see their events recorded. For us it means lots of media files should be stored for on-demand watching. We have tried many solution but got REAL stable results with MooseFS only...

Dmytro Pereuda

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...

George Breahna

For data storage, Dedikam uses MooseFS, a robust, stable, redundant and high performance file system. We have been using this solution for 10 years so we can say that the system is reliable, robust and secure. We are very satisfied.

Michaël BiharyOwner

Ipla is the Internet TV broadcaster streams on-demand content 24/7. It's possible with the underlying MooseFS storage build with commodity hardware. We appreciated that the system is ready for unexpected peaks...

Grzegorz JanczuraDirector of the Internet Projects

Our core buissnes relies on MooseFS since 2005. We keep a long history of internet traffic which is more than 5.5 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.

Marek Robak, PhDHead of IT Operations

As a researcher I need to deal with large sets of 3D points clouds. Hell of data. MooseFS helps me handle them, I can verify my ideas and algorithms efficiently. Atomic snapshots rocks! In addition I'm sure my work results are safe.