Object permanently unavailable

When the Archive Node requests an object from the Tivoli Storage Manager (TSM) server and the retrieval fails, the Archive Node retries the request after an interval of 10 seconds. If the object is permanently unavailable (for example, because the object is corrupted on tape), the TSM API has no way to indicate this to the Archive Node, so the Archive Node continues to retry the request.

When this situation occurs, an alarm is triggered, and the value continues to increase. To see the alarm, go to Support > Grid Topology > Archive Node > ARC > Retrieve > Request Failures.

A retrieval can fail if the object is temporarily unavailable. In this case, subsequent retrieval requests should eventually succeed.

If the object is permanently unavailable, you must perform the "determining if objects are unavailable" procedure to identify the object, and then manually cancel the Archive Node’s request.

If the StorageGRID Webscale system is configured to use an ILM rule with only one active content placement instruction, copies of an object are not made.

If an object is lost, it cannot be recovered; however, you must still determine if object is permanently unavailable to “clean up” the StorageGRID Webscale system, to cancel the Archive Node’s request, and purge metadata for the lost object.