At smaller object sizes, deletes become highly problematic and effectively disqualify any object store that employs such an approach. Because MinIO writes metadata atomically along with the object data, it does not require a database (Cassandra in most cases) to house the metadata. Veeam’s default is 1MB objects but supports anywhere from 256K to 4MB. This can have devastating effects if the plug gets pulled in the middle of your job and your database gets corrupted. One way slower object stores try to make shortcuts is to move to an eventual consistency model. Longer backup restore cycles would result in increased disruption to business. With the ability to read/write at speeds in excess of 160 GB/s in a single 32 node cluster, MinIO can backup and restore at speeds once considered impossible for object storage.
There are a number of reasons but these four stand out: This is where modern object stores like MinIO are exceptionally well suited.
Traditional object storage architectures (think appliance vendors) are not up to the task here for a number of reasons. First, backups and restores need to go quickly no matter the size.