Restore Consistency and Recovery

Oracle

Audience
Public
Technology Integrations
Oracle
Source Type
Documentation

Protection Group snapshots provide write-order consistency across their member volumes. The Oracle recovery action after restore depends on how the snapshot was created and on the recovery objective.

Source snapshot type Typical recovery behavior Operational guidance
Application-consistent Oracle may require media recovery using required archived redo; the exact action depends on whether hot backup mode or suspend was used and what redo is available. Follow the documented recovery plan and retain all archived redo that covers the snapshot point. Do not assume that ALTER DATABASE OPEN alone is always sufficient.
Crash-consistent Oracle performs instance/crash recovery when the database starts; further recovery may be needed depending on restored files and the desired recovery point. Expect recovery and validate the alert log. Do not use RESETLOGS unless the recovery path requires it.
Recovery decision: ALTER DATABASE OPEN RESETLOGS is not a routine snapshot-restore command. Use it only after incomplete recovery, recovery using a backup control file, or another Oracle-documented recovery path that requires it. Opening with RESETLOGS starts a new database incarnation and affects backup and recovery strategy.