Object content stored on different types of storage
When the Storage Tiering service moves an object off the ingest tier and onto another storage tier, the service removes all copies of the object data from the ingest tier and stores the specified number of copies of the object data on the new storage tier. However, at least one copy of the object metadata must always remain on primary running storage. For each storage tier that’s defined for a given namespace, the service plan specifies the number of copies of object data that must be stored on the tier and the number of copies of object metadata that must be stored on primary running storage.
For each object in a given namespace, the Storage Tiering service always moves copies of the data for that object among the storage tiers that are defined for the namespace by its service plan. However, the Storage Tiering service does not move all of the other content for an object to each storage tier that’s defined for a namespace.
For each copy of an object that’s stored on primary spindown storage, only the data, custom metadata, ACL, and secondary metadata for that object are actually stored on primary spindown storage. All copies of the primary metadata for an object must always remain on primary running storage.
Objects moved from primary running storage to primary spindown storage are always kept on the same storage node.
For each copy of an object that’s moved to S Series or extended storage, only the data for that object is actually stored on primary running storage. All copies of the object metadata must always remain on primary running storage.