The Archive Node provides an interface through which object data can be sent to an external archival storage system (tape or the cloud) for long term storage.
If the ILM policy requires that a copy of object data be archived, the CMS service sends a request to the Archive Node, which in turn sends the object data to the targeted archival storage system.
The table shows the primary attributes used to track object data sent to the targeted external archival storage system:
Component | Attribute changes |
---|---|
Note: The StorageGRID Webscale system cannot detect how much available storage is attached to the Archive Node.
|
Active Objects (AROP): The number of copies of object data in the process of being written to the archival storage system increases by one as the object is being archived and decreases by one once the object is archived. Archived Objects (AROA): The total number of copies of object data written to the archival storage system by this ARC service increases by one. Archived Bytes (ARBA): The total amount of content written to the archival storage system increases by an amount equivalent to the object size. |
Inbound Replications Completed (RIRC): The total number of copies of object data replicated to the destination ARC service increases by one. | |
Objects Retrieved (ORET): The number of persistent objects retrieved from the storage system of the source LDR increases by one each time the object is replicated from this source LDR to the Archive Node. | |
Outbound Replications – Completed (RORC): The total number of copies of object data replicated from the source Storage Node increases by one each time the object is replicated from this source Storage Node service to the Archive Node. |