Tiering - Objects placed in storage tiers/classes based on its metadata independent of other unrelated objects. Object metadata can decide how many copies should exist and where(geo locations/fault domains). In an object storage system, DR is not volume centric. The unit of disaster protection is the volume. Again, this does not bother whether individual files want to be replicated or not. How are files/volumes protected from a disaster? Typically, in a Disaster Recovery(DR) setup, entire volumes/volume-sets are setup for replication to a DR site. All objects need not be versioned, each individual object can tell if it is versioned. In an object storage system, you will rarely see snapshots of volumes, objects will be snapshot-ed, perhaps automatically. A lot of space can get used(wasted?) for a complete volume snapshot while only a few files needed to be snapped. Whether all of them like it or not, whether all of them need it or not. When a snapshot is taken, all files in the volume are snapped too. What are snapshots today? They are point in time copies of a volume. I would muster this: Object storage is a (new/different) ''object centric'' way of thinking of data, its access and management. I believe there is an NFS protocol extension that allows this. Storage/Access by OID is a way to handle data without bothering about naming it. HTTP access to data in filesystems has been available in many well known NAS systems. IMO, Object storage has nothing to do with scale because someone could build a FS which is capable of storing a huge number of files, even in a single directory.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |