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 next to Oracle Cloud.
From the Oracle Cloud Infrastructure left navigation list click Autonomous Data Warehouse.
- Choose your region. See Switching Regions for information on switching regions and working in multiple regions.
- Choose your Compartment. See Compartments for information on using and managing compartments.
- Select an Autonomous Data Warehouse instance from the list in your compartment.
- On the Details page, from the More Actions drop-down list, select Create Clone.
- On the On the Create
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
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.
- 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 Data Warehouse 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.
- 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.
Point in time clone
Description of the illustration adb_clone_source_backup.png
Select the backup from a list
Description of the illustration adb_clone_source_list.png
Note:When creating a clone from a backup, you must select a backup that is at least 2 hours old, or the clone operation will fail.
- 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 14 characters. The same database name cannot be used for multiple Autonomous Databases in the same tenancy in the same region.
- Configure the database.
Choose database version Select a database version that is either the same version or is a higher version than the source database.
OCPU Count Specify the number of CPU cores for your database.
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.
Auto scaling Deselect to disable auto scaling. With auto scaling the system to automatically uses up to three times more CPU and IO resources to meet workload demand. See Use Auto Scaling for more information.
- Create administrator credentials.
Username This is a read-only field.
- Password Set the password for the Autonomous Data Warehouse 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.
- Choose network access
Allow secure access from everywhere
By default all secure connections are allowed from everywhere. To restrict access configure an access control list (ACL). To add an ACL for the Autonomous Database, select Configure access control rules.
See Configure Access Control Lists for an Existing Autonomous Database Instance for more information.
Virtual cloud network
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.
- Choose a license type.
Bring Your Own License
My organization already owns Oracle database software licenses. Bring my existing database software licenses to the database cloud service (details).
Subscribe to new database software licenses and the database cloud service.
(Optional) Click Show Advanced Options to enter additional options.
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.
On the Oracle Cloud Infrastructure console the State shows Provisioning... until the new Autonomous Data Warehouse database is available.
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).
When creating a clone from a backup, you must select a backup that is at least 2 hours old, or the clone operation will fail.
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.