Complete the following checks for every restore or clone:
Storage
The selected Protection Group snapshot and timestamp were recorded.
-
All database volumes were restored or cloned from the same snapshot point.
-
GRID/CRS/+OCR volumes were excluded.
-
Every target RAC node sees every required database volume.
-
Multipath or NVMe-oF paths are healthy and consistent.
ASM
asmcmd lsdg
asmcmd lsd-
Intended database disk groups are mounted.
-
ASM reports no unresolved disk, path, or rebalance errors.
-
No unapproved source and clone disk group identities are mounted together on the same ASM cluster.
Database and RAC
SELECT name, db_unique_name, open_mode, database_role FROM v$database;
SELECT inst_id, instance_name, host_name, status FROM gv$instance ORDER BY inst_id;
srvctl status database -d <DB_UNIQUE_NAME>
srvctl status service -d <DB_UNIQUE_NAME>
-
The database is in the intended open mode.
-
All required RAC instances are running.
-
Services run on their intended instances.
-
Database and ASM alert logs show successful recovery or expected recovery messages only.
Application and Operations
-
Application connectivity tests pass through the intended service names.
-
Backup, monitoring, scheduler, and integration configuration reflects the correct environment.
-
For clones, production-facing jobs and integrations are disabled or redirected.
-
The change record includes snapshot ID, volume mapping, recovery actions, validation evidence, and final disposition.