If the master Moab copy of an object goes bad (is damaged or corrupted), a recovery process should fetch a copy from archival storage and replace the Moab object.
We will first try the Local Archive as the speediest and most efficient repair.
If the Local Archive doesn't work for some reason, a new copy needs to be fetched from one of the cloud archives
Consider the case where the bad Moab object has already been propagated to the archives? It would not show as a fixity discrepancy. May beed a different story on version or archive copy rollback and recovery from DOR.
If the master Moab copy of an object goes bad (is damaged or corrupted), a recovery process should fetch a copy from archival storage and replace the Moab object.
Consider the case where the bad Moab object has already been propagated to the archives? It would not show as a fixity discrepancy. May beed a different story on version or archive copy rollback and recovery from DOR.