A customer needs to be able to perform an instant recovery of database data files. The recovery point is one hour to enable them to have a specified point time to restore the data if the data migratio

Volume clones create a full copy of a volume at a single point in time and are not designed for scheduled, recurring hourly recovery points tied to a migration rollback window.

Backups to disk support scheduled, point-in-time copies of database data files at defined intervals - in this case every hour - establishing a concrete recovery point objective (RPO) of one hour. If the migration fails, the data can be instantly restored from the most recent hourly backup to the exact state it was in at that snapshot time. This method is specifically designed around structured recovery points, unlike continuous replication approaches that do not inherently preserve discrete restore points.

Asynchronous replication continuously mirrors data to a secondary system with some lag but does not provide a mechanism to restore to a specific historical point one hour in the past.

Snapshots capture storage-level point-in-time states but are typically short-lived, storage-local constructs and are not the standard mechanism for defining a structured hourly recovery point for a migration scenario.