Review warnings for Storage Node system drive recovery
PDF of this doc site
- Get started
Install and upgrade
Install appliance hardware
- Install hardware
- Set up hardware
- Install Red Hat Enterprise Linux or CentOS
- Install Ubuntu or Debian
- Install VMware
- Install appliance hardware
Configure and manage
- Manage security
Manage objects with ILM
- ILM and object lifecycle
- Administer StorageGRID
- Use a tenant account
Use S3 REST API
- Support for Amazon S3 REST API
Monitor and troubleshoot
- Monitor StorageGRID system
- Troubleshoot StorageGRID system
- Expand your grid
Recover nodes and maintain your grid
Grid node recovery procedures
- Recover from Storage Node failures
- Recover from Admin Node failures
- Decommission procedure
- Grid node recovery procedures
Maintain SG6000 hardware
- Maintenance configuration procedures
- Maintain SG5700 hardware
Before recovering a failed system drive of a Storage Node, review the general warnings and considerations for grid node recovery and the following specific warnings.
Storage Nodes have a Cassandra database that includes object metadata. The Cassandra database might be rebuilt in the following circumstances:
A Storage Node is brought back online after having been offline for more than 15 days.
A storage volume has failed and been recovered.
The system drive and one or more storage volumes fails and is recovered.
When Cassandra is rebuilt, the system uses information from other Storage Nodes. If too many Storage Nodes are offline, some Cassandra data might not be available. If Cassandra has been rebuilt recently, Cassandra data might not yet be consistent across the grid. Data loss can occur if Cassandra is rebuilt when too many Storage Nodes are offline or if two or more Storage Nodes are rebuilt within 15 days of each other.
|If more than one Storage Node has failed (or is offline), contact technical support. Don't perform the following recovery procedure. Data loss could occur.
|If this is the second Storage Node failure in less than 15 days after a Storage Node failure or recovery, contact technical support. Rebuilding Cassandra on two or more Storage Nodes within 15 days can result in data loss.
|If more than one Storage Node at a site has failed, a site recovery procedure might be required. See How site recovery is performed by technical support.
|If this Storage Node is in read-only maintenance mode to allow for the retrieval of objects by another Storage Node with failed storage volumes, recover volumes on the Storage Node with failed storage volumes before recovering this failed Storage Node. See the instructions to recover from storage volume failure where system drive is intact.
|If ILM rules are configured to store only one replicated copy and the copy exists on a storage volume that has failed, you will not be able to recover the object.
|If you encounter a Services: Status - Cassandra (SVST) alarm during recovery, see Recover failed storage volumes and rebuild Cassandra database. After Cassandra is rebuilt, alarms should clear. If alarms don't clear, contact technical support.