When cloning from a backup, what is the earliest timestamp of the backup allowed in Autonomous Database?

When creating a clone of an Oracle Autonomous Database from a backup, the system imposes a minimum age requirement on the backup that can be used. The selected backup must be at least two hours old. This ensures that the backup is fully processed, consistent, and available in object storage for the cloning operation to proceed successfully. Backups that are more recent than two hours will not be presented as valid options for cloning.

B. 24 hours: This is incorrect. While you can clone from backups that are 24 hours old or older, it is not the earliest allowed timestamp; backups newer than 24 hours are also available.
C. 1 hour: This is incorrect. A backup that is only one hour old is too recent and does not meet the minimum two-hour age requirement for cloning.
D. 30 minutes: This is incorrect. A 30-minute-old backup is significantly more recent than the minimum two-hour requirement and cannot be used for cloning.

1. Oracle Cloud Infrastructure Documentation. (2024). Clone an Autonomous Database. In Use Autonomous Database on Shared Exadata Infrastructure.

Section: To clone an Autonomous Database from a backup

Quote: "Select a backup from the list of backups. The list shows backups you can use to create a clone. The backup must be at least 2 hours old."

2. Oracle Cloud Infrastructure Documentation. (2024). Cloning an Autonomous Database on Dedicated Exadata Infrastructure. In Use Autonomous Database on Dedicated Exadata Infrastructure.

Section: To clone an Autonomous Database from a backup

Quote: "Select a backup from the list of backups. The list shows backups you can use to create a clone. The backup must be at least 2 hours old."