After recovering a storage volume on a Storage Node where the system drive also failed and was recovered, you can restore object data to the recovered storage volume from other Storage Nodes and Archive Nodes.
About this task
Object data can be restored from other Storage Nodes, an Archive Node, or a Cloud Storage Pool, assuming that the grid's ILM rules were configured such that object copies are available.
Attention: If ILM rules are configured to store only one replicated copy and that copy exists on a Storage Node that has failed, you will not be able to recover the object. However, you must still perform the procedure to restore object data to a storage volume to purge lost object information from the database.
Attention: If the only remaining copy of an object is in a
Cloud Storage Pool, StorageGRID must issue multiple
requests to the Cloud Storage Pool endpoint to restore object data. Before running either of the repair-data scripts, contact technical support for help in estimating the recovery time frame and the associated costs.
Note: If the only remaining copy of an object is on an Archive Node, object data is retrieved from the Archive Node. Due to the latency associated with retrievals from external archival storage systems, restoring object data to a Storage Node from an Archive Node takes longer than restoring copies from other Storage Nodes.
To restore object data, you run the repair-data script. This script begins the process of restoring object data and works with ILM scanning to ensure that ILM rules are met. You use different options with the repair-data script, based on whether you are restoring replicated data or erasure coded data, as follows:
- Replicated data: Two commands are available for restoring replicated data, based on whether you need to repair the entire node or only certain volumes on the node:
repair-data start-replicated-node-repair
repair-data start-replicated-volume-repair
- Erasure coded (EC) data: Two commands are available for restoring erasure coded data, based on whether you need to repair the entire node or only certain volumes on the node:
repair-data start-ec-node-repair
repair-data start-ec-volume-repair
Repairs of erasure coded data can begin while some Storage Nodes are offline. Repair will complete after all nodes are available. You can track repairs of erasure coded data with this command:
repair-data show-ec-repair-status
For more information on using the repair-data script, enter repair-data --help from the command line of the primary Admin Node.