Degradation Operations Clear Suspect Object Part in Storage Pool Clear Suspect Object Part on Tape Clear Suspect Object Part on an Amazon S3 Target Clear Suspect Object Part on an Azure Target Clear Suspect Object Part on a DS3 Target Get Degraded Object Parts Get Degraded Buckets Get Degraded Data Persistence Rules Get Degraded Amazon S3 Replication Rules Get Degraded Azure Replication Rules Get Degraded DS3 Replication Rules Get Suspect Object Parts in Storage Pools Get Suspect Object Parts on Tape Media Get Suspect Object Parts on Amazon S3 Targets Get Suspect Object Parts on Azure Targets Get Suspect Object Parts on DS3 Targets Get Suspect Buckets Get Suspect Objects Get Suspect Objects with Full Details Mark Suspect Object Part in a Storage Pool as Degraded Mark Suspect Object Part on Tape as Degraded Mark Suspect Object Part on an Amazon S3 Target as Degraded Mark Suspect Object Part on an Azure Target as Degraded Mark Suspect Object Part on a DS3 Target as Degraded This chapter provides detailed information about suspect and degraded data. Data is considered suspect if one or more copies of the data is corrupt (if the checksum read does not match the expected value). Data is considered degraded if it is manually marked as lost (for example, if an ejected tape that contains a copy is marked as permanently lost) or if suspect data is manually marked as degraded. Degraded data can still be read provided that at least one copy of the data is good. If every copy of copy of the data is marked as degraded, this eliminates your ability to GET or VERIFY the object.
