Clone Autonomous Database from a Backup

Shows the options to select a backup as the clone source for cloning Autonomous Database.

Perform the following prerequisite steps as necessary:

  • Open the Oracle Cloud Infrastructure Console by clicking the navigation icon next to Oracle Cloud.

  • From the Oracle Cloud Infrastructure left navigation menu click Oracle Database and then, depending on your workload click one of: Autonomous Data Warehouse, Autonomous JSON Database, or Autonomous Transaction Processing.
  1. Choose your region. See Switching Regions for information on switching regions and working in multiple regions.
  2. Choose your Compartment. See Compartments for information on using and managing compartments.
  3. Select an Autonomous Database instance from the list in your compartment.
  4. On the Details page, from the More Actions drop-down list, select Create Clone.
  5. On the On the Create Autonomous Database Clone page, choose the clone type from the choices:
    • Full Clone: creates a new database with the source database’s data and metadata.
    • Refreshable Clone: creates a read-only full clone that can be easily refreshed with the source database’s data.

      See Using Refreshable Clones with Autonomous Database for more information.

    • Metadata Clone: creates a new database with the source database’s metadata without the data.
  6. In the Configure clone source area, select the Clone source option:
    • Clone from database instance: This creates a clone from a running database. See Clone an Autonomous Database Instance for details and steps with this selection.

    • Clone from a backup: This selection creates a database clone using a backup or lets you enter a point-in-time to create the clone. Select this option.

  7. In the Configure clone source area, select the Backup clone type:
    • Point in time clone: Enter a timestamp to clone in the Enter Timestamp field.

    • Select the backup from a list: Enter From and To dates to narrow the list of backups then select a backup to use for the clone source.

  8. Provide basic information for the Autonomous Database.
    • Create in Compartment. See Compartments for information on using and managing compartments.

    • Display Name Specify a user-friendly description or other information that helps you easily identify the resource.

      You can use the name provided, of the form: Clone of DBname or change this to the name you want to use to identify the database. The supplied DBname is the name of the source database that you are cloning.

      Note:

      After you create a clone you cannot change the display name. Thus, using the supplied Clone of DBname may not be the display name you want to use when you create a clone.
    • Database Name: Specify the database name; it must consist of letters and numbers only. The maximum length is 30 characters. The same database name cannot be used for multiple Autonomous Databases in the same tenancy in the same region.

  9. Configure the database.
    • Choose database version Select a database version that is the same version or is a higher version than the source database.

    • OCPU count Specify the number of CPU cores for your database.

      Your license type determines the OCPU count maximum. For example, if your license type is Bring Your Own License (BYOL) with Oracle Database Standard Edition (SE), the OCPU count maximum is 8.

    • OCPU auto scaling By default OCPU auto scaling is enabled to allow the system to automatically use up to three times more CPU and IO resources to meet workload demand. If you do not want to use OCPU auto scaling then deselect this option.

      See Use Auto Scaling for more information.

    • Storage (TB) Specify the storage you wish to make available to your database, in terabytes.

      For a Full Clone, the minimum storage that you can specify is the source database's actual used space rounded to the next TB.

    • Storage auto scaling By default storage auto scaling is disabled. Select if you want to enable storage auto scaling to allow the system to automatically expand to use up to three times more storage.

      See Use Auto Scaling for more information.

  10. Create administrator credentials.
    • Username This is a read-only field.

    • Password Set the password for the Autonomous Database Admin user. The password must meet the strong password complexity criteria based on Oracle Cloud security standards. For more information on the password complexity rules see Create Users on Autonomous Database - Connecting with a Client Tool.
    • Confirm password Specify a value to confirm the password.
  11. Choose network access

    Note:

    After you clone your Autonomous Database you can change the network access option you select for the cloned instance.
    • Secure access from everywhere

      By default all secure connections are allowed from everywhere.

    • Secure access from allowed IPs and VCNs only

      This option restricts connections to the database according to the access control lists (ACLs) you specify. To add multiple ACLs for the Autonomous Database, click + Access Control Rule.

      See Configure Access Control Lists When You Provision or Clone an Instance for more information.

    • Private endpoint access only

      This option assigns a private endpoint, private IP, and hostname to your database. Specifying this option allows traffic only from the VCN you specify; access to the database from all public IPs or VCNs is blocked. This allows you to define security rules, ingress/egress, at the Network Security Group (NSG) level and to control traffic to your Autonomous Database.

      See Configure Private Endpoints When You Provision or Clone an Instance for more information.

  12. Choose license and Oracle Database Edition
    • Bring Your Own License (BYOL)

      Select if your organization already owns Oracle database software licenses. Bring your existing database software licenses to the database cloud service. See Cloud pricing for information on Bring Your Own License (BYOL) and other licensing options for Oracle Cloud Infrastructure cloud service pricing.

    • Choose an Oracle Database Edition

      When you select Bring Your Own License (BYOL), you also choose an Oracle Database Edition. The Oracle Database Edition you select is based on the license you bring to Autonomous Database and changes the maximum value that you can select for the OCPU count. The choices are:

      Oracle Database Enterprise Edition (EE): For this license type the maximum allowed value for OCPU count is 128. With auto scaling enabled you can use up to OCPU count x 3 OCPUs. For example, if you set the OCPU count to 128, you can use up to 384 OCPUs.

      Oracle Database Standard Edition (SE): For this license type the maximum allowed value for OCPU count is 8. With auto scaling enabled you can use up to OCPU count x 3 OCPUs. This license restricts the number of OCPUs you can use to a maximum of 8 OCPUs, with or without auto scaling enabled.

      See Use Auto Scaling for more information.

    • License Included

      Subscribe to new database software licenses and the database cloud service.

  13. (Optional) Provide up to 10 maintenance contacts.

    Click Add Contact and in the Contact Email field, enter a valid email address. If the database you are cloning has a customer contact list, the list is copied. To enter multiple Contact Email addresses, repeat the process to add up to 10 customer contact emails.

    See View and Manage Customer Contacts for Operational Issues and Announcements for more information.

  14. (Optional) Click Show Advanced Options to select advanced options.
    • Encryption Key

      Encryption using Oracle-managed keys: By default Autonomous Database uses Oracle-managed encryption keys. Using Oracle-managed keys, Autonomous Database creates and manages the encryption keys that protect your data and Oracle handles rotation of the TDE master key.

      Encrypt using customer-managed keys: If you select customer-managed keys, a master encryption key in the Oracle Cloud Infrastructure Vault is used to generate the TDE master key on Autonomous Database.

      See Use Customer-Managed Encryption Keys on Autonomous Database for more information.

    • Maintenance

      Patch level By default the patch level is the patch level of the source database. Select Early to configure the instance with the early patch level. When cloning a source database with Early patch level, you can only choose the Early patch level for your clone.

      See Set the Patch Level for more information.

    • Management

      Shows the character set and national character set for your database.

      See Choose a Character Set for Autonomous Database for more information.

    • Tags

      If you want to use Tags, enter the TAG KEY and VALUE. Tagging is a metadata system that allows you to organize and track resources within your tenancy. Tags are composed of keys and values which can be attached to resources.

      See Tagging Overview for more information.

  15. Click Create Autonomous Database Clone.

On the Oracle Cloud Infrastructure console the State shows Provisioning... until the new database is available.

Notes:

  • If there is an ongoing clone from backup operation on a source database, you cannot initiate a new clone operation on the same backup being cloned until the ongoing operation completes. Thus, you cannot clone from backup twice concurrently from a specific backup (for example, a specific timestamp or a specific selected backup from the list of backups).

  • For external tables, partitioned external tables, and the external partitions of hybrid partitioned tables a backup does not include the external files that reside on your Object Store. Thus, for the clone from backup operation, it is your responsibility to backup, and restore if necessary, the external files associated with external tables, external partitioned tables, or the external files for a hybrid partitioned table

  • With clone from backup, the Oracle Machine Learning workspaces, projects, and notebooks of the source database are not cloned to the new database.

See Notes for Cloning Autonomous Database for additional information on cloning.

See Cloning an Autonomous Database for information on using the API.