When you are using the Replication Task Suite (RTS) with a "ReplicateConsumer" enabled, the RTS will write DELETION_RECORD entries to your backup location anytime a deletion occurs in DSpace. This feature allows you to see which objects have been deleted and decide whether you wish to restore them:
However, unfortunately, the RTS fails to check if the AIP already exists in your backup location. This can lead to odd scenarios where a DELETION_RECORD exists but an AIP does NOT, e.g.
- If you created and deleted an Item in the same day, but your AIP backup is only performed nightly. This would mean a DELETION_RECORD would be auto-generated on deletion, even though the AIP was never generated.
This is a minor issue as it doesn't cause instability in the backup. However, the existent of a DELETION_RECORD usually implies that the object can be restored – but in this case it is not possible since the AIP backup was not performed before the deletion occurred.
The fix would be to ensure the DELETION_RECORD is only generated if an AIP exists.