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.
To correctly recover failed storage volumes, you need to know both the device names of the failed storage volumes and their volume IDs.
At installation, each storage device is assigned a file system universal unique identifier (UUID) and is mounted to a rangedb directory on the Storage Node using that assigned file system UUID. The file system UUID and the rangedb directory are listed in the /etc/fstab file. The device name, rangedb directory, and the size of the mounted volume are displayed in the Grid Manager.
To see these values, select . Then, select .
In the following example, device /dev/sdc has a volume size of 4 TB, is mounted to /var/local/rangedb/0, using the device name /dev/disk/by-uuid/822b0547-3b2b-472e-ad5e-e1cf1809faba in the /etc/fstab file:
Using the repair-data script
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
repair-data show-ec-repair-status
Notes on data recovery
If the only remaining copy of object data is located 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.