Resources or data disappear through a provider mistake or through your own operators and automation, such as a Terraform apply in Resource Manager or a cleanup script. In May 2024 a Google Cloud provisioning misconfiguration deleted UniSuper's private cloud subscription, which removed both geographic copies, and UniSuper restored from backups it kept with another provider. On OCI, deleted volumes, backups and unversioned objects cannot be recovered, so stop the automation and protect the surviving copies first.
Look here
Log
Search for
Audit, who deleted what
Deletes and terminations with their principal: DeleteBucket, DeleteVolume, DeleteBootVolume, DeleteVolumeBackup, TerminateInstance, DeleteAutonomousDatabase, TerminateDbSystem. Record data.identity.principalName, ipAddress and userAgent. If the principal or address is unknown, treat it as an attack and open deletion and ransomware
Object Storage write log
Object deletions, with data.requestAction, DELETE, by data.principalName. Audit records bucket events and no object events, so this log is the only record, if it was enabled
Resource Manager jobs
Jobs that ran on the stack in the window: oci resource-manager job list -c <compartment-ocid> --stack-id <ocid>
Resource Manager plan
What a run planned to destroy: oci resource-manager job get-job-tf-plan --job-id <ocid> --file plan.json --tf-plan-format JSON
DevOps and scheduled jobs
Deployments, cleanup functions and scripts that ran at the deletion times. Read the logs of the functions and scripts, and list deployments with: oci devops deployment list -c <compartment-ocid> --all
Oracle-side actions
Actions by Oracle staff. Operator Access Control and Delegate Access Control log operator access for their listed Exadata and Cloud@Customer services only. The documentation reviewed does not say other Oracle staff actions appear in your Audit log. Check Console Announcements: oci announce announcements list -c <tenancy-ocid> --all
Object versions
Previous versions and delete markers in versioned buckets: oci os object list-object-versions -bn <bucket> --all
Volume backups
Surviving backups of each volume, in each region: oci bv backup list -c <compartment-ocid> --volume-id <ocid>
Terminated databases
Terminated Autonomous AI Databases that may still be undeleted: oci db autonomous-database list -c <compartment-ocid> --lifecycle-state TERMINATED
Contain
#
Item
1
Stop the automation before restoring. Disable the pipeline trigger, remove the automation principal from the group that can delete, and cancel running Resource Manager jobs: oci resource-manager job cancel --job-id <ocid>
2
Save the Terraform state, the job logs and an Audit export for the window as evidence, as in Evidence. Save the state with: oci resource-manager job get-job-tf-state --job-id <ocid> --file state.json
3
Back up surviving volumes manually. Manual backups do not expire: oci bv backup create --volume-id <ocid> --display-name <case-id> --type FULL
4
Turn on versioning for affected buckets: oci os bucket update -bn <bucket> --versioning Enabled
5
Undelete a terminated Autonomous AI Database in the Console within 72 hours or the backup retention period, whichever is shorter
6
Check terminated databases protected by the Recovery Service. Their backups stay while the protected database is in Delete Scheduled state, 72 hours by default or the policy retention period if that option was set before termination, and are then deleted. Act on them inside that window
7
If Oracle caused the loss or can help reverse it, open a support request from the Console Help menu with impact Critical issue. From the CLI, severity HIGHEST needs a 24x7 contact: oci support incident create -c <tenancy-ocid> --problem-type TECH --severity HIGHEST --title <text> --description <text>
Eradicate and recover
#
Item
1
Restore volumes from backups, following Recover: oci bv volume create --availability-domain <ad> -c <compartment-ocid> --volume-backup-id <ocid>
2
Restore deleted objects in versioned buckets by deleting their delete markers, as in deletion and ransomware
3
Where the source region lost its copies, copy backups back from the other region: oci bv backup copy --volume-backup-id <ocid> --destination-region <region>
4
Fix the configuration and run a new plan. Have a second person review every destroy before the apply: oci resource-manager job create-plan-job --stack-id <ocid>
5
Enable cross-region copy in user-defined block volume backup policies
6
Replicate critical buckets to another region: oci os replication create-replication-policy -bn <bucket> --name <name> --destination-region <region> --destination-bucket <bucket>
7
Lock backups with Block Volume retention lock and Recovery Service retention lock, and keep one copy outside the tenancy
8
Record what could not be recovered and why
Watch out
A deleted block volume cannot be restored, and policy-based backups expire on schedule. Only manual backups are kept until someone deletes them.
Scheduled cross-region backup copies can take up to 24 hours, and a copy keeps the retention period of its source.
A forced cancel of a Resource Manager job can leave a state file that does not match the resources. Plan against that state only after checking it.
Autonomous AI Database undelete needs the ECPU compute model and a free database name.
Oracle documentation: Audit overview, details for Object Storage logs, Object Storage object versioning, deleting a block volume, Block Volume backups, policy-based backups, Block Storage ransomware-resilient backup protection release note, scheduled deletion of a protected database, backup retention for a terminated database, Recovery Service retention lock, undelete a terminated Autonomous AI Database, overview of Operator Access Control, overview of Delegate Access Control, Console Announcements, creating a support request; OCI CLI help for resource-manager job, recovery protected-database, bv backup copy and support incident create. UniSuper and Google Cloud joint statement. Checked September 2026. Rechecked October 2026: Audit overview (no object-level events), and every command against OCI CLI 3.94.2, including the 24x7 contact that severity HIGHEST requires; undelete a terminated Autonomous AI Database (72 hours or the backup retention period, ECPU only, no same-name database in the region).