How to recover deleted data from ServiceNow instanceInstructionsIf the data is deleted or missing from ServiceNow, recovering it depends on how and when it was deleted, and whether it can be retrieved. For more information on backups, see Instance backup and recovery. More information on backups and retention is covered in this white paper: Delivering performance, scalability, and availability with the ServiceNow AI Platform. Deleted records module This module has some limitations. Only audited tables are tracked in the deleted records module. If table A references table B/C and only table A is audited, data from table B/C cannot be retrieved from the deleted records module. For more information, see: Use the Deleted Records module to restore a deleted record. If the data is removed from Deleted records table(sys_audit_delete), the data can never be retrieved. See Record Deletes/Updates, how to track, find and troubleshoot these issues. Rollback context We also have rollback contexts which are enabled by default when we delete the data using a script from Background Scripts. This context is kept only for 10 days and then it is purged, tracking INSERT, DELETE, and UPDATE statements to recover data by undoing SQL statements within 10 days of deletion, if configured for Rollback. There are rollback context expiration properties that will cleanse the table by creating a scheduled job "Clean Expired Rollback Contexts". Rollback context properties Roll back and delete recovery Use the Delete Recovery module to restore a deleted record Use the Script Execution History module to roll back a Scripts-Background execution How to Enable Rollback context for Fix Script Execution Mass-Deletion and Excess Data Management Recommendations Manual Data recovery by ServiceNow Support If there is an unforeseen event of data deletion on a PROD, ServiceNow can recover most of the data if reported within 4 days (as of this writing) from the actual event, as DB Transaction/BIN logs are kept for 4 days and data can be recovered. We have standard operating procedures to recover data by analyzing individual cases. We have daily backups, and data logged between 10 AM and 6 AM is lost if the daily backup is dated 6 AM and data deletion happens at 10 AM. However, if we have BINLOGS (kept for 4 days), we can recover most of the data by spinning up a temp instance and playing the binlogs till 10 AM after restoring the 6 AM backup. Restoring a Production Instance from Backup Backup Request for a Production instance Data recovery from an upgrade perspective If dataloss is observed after 4 days, some data can still be recovered using 14-28 day backups (retention period for your organization). For PROD instance data deletion or corruption, create a ServiceNow Support case ASAP to utilize BINLOGS for data retrieval. Warning: Manual Data recovery is not an option for any SUB PROD environment and the options for recovery are on this KB Dataloss on sub production or non production instances.