Knowing the differences between restartable and recoverable states, you can now create a storage-consistent snapshot that can serve both purposes. This is done by creating a consistent snapshot containing all the data, redo, and control files, thus satisfying the requirements for a restart solution. If that snapshot is used, Oracle performs crash/instance recovery and open the database.

However, the snapshot can also be used for a recovery solution. This is done by only using the datafiles, thus satisfying the requirement for recovery solution. The datafiles can be restored alone back to the production database, then use the archive and redo logs to perform media recovery. Or, mount the datafiles to a different server and use RMAN from there to create a backup image to Data Domain or another backup target.

In other words, by creating a consistent snapshot containing the database data, control, and redo log files, and with the ability to restore just the datafiles or all the files, snapshot can be used for both purposes.

Note: To use such a hybrid solution it is required to separate the Oracle data, redo, and archive logs from each other, such as to different ASM disk groups, or file systems. See the requirements section below.