Cross Tenancy and Cross-Region Cloning
You can clone an Autonomous Database instance from one tenancy, source tenancy, to a different tenancy (destination tenancy).
- About Cross Tenancy Cloning
When you create a cross tenancy clone you can either select that the clone is created in the same region as the source tenancy or in a different region than the source tenancy (cross-region). - Prerequisites for Cross Tenancy Cloning
Describes prerequisites for creating a cross tenancy clone where the source database is in one tenancy and the cloned database is in a different tenancy. - Create a Cross Tenancy or Cross-Region Clone
Shows the steps to create a cross tenancy clone when the source database and the cloned database are in the same region, or when the source database and the cloned database are in different regions (cross-region). - Create a Cross Tenancy Clone from a Backup
Shows the steps to create a cross tenancy clone from a backup.
Parent topic: Cloning and Moving an Autonomous Database
About Cross Tenancy Cloning
When you create a cross tenancy clone you can either select that the clone is created in the same region as the source tenancy or in a different region than the source tenancy (cross-region).
The cross tenancy cloning option is only available using the CLI or the Autonomous Database REST APIs. This option is not available using the Oracle Cloud Infrastructure Console.
Note the following for cross tenancy cloning:
-
All clone types are supported: the cloned database can be a Full clone, a Metadata clone, or a Refreshable clone.
-
A clone can be created from a source Autonomous Database instance or from a backup (using the latest backup, a specified backup, or by selecting a long-term backup).
-
The source Autonomous Database instance can use either the ECPU or OCPU compute model. Depending on your workload type, you can clone from a source that uses the OCPU compute model to a clone that uses the ECPU compute model (this is allowed for the Data Warehouse and the Transaction Processing workload types).
-
The cloned database can be in the same region or in a different region (cross-region).
-
The cross tenancy cloning option does not support cloning with customer managed keys on the source. See Manage Encryption Keys on Autonomous Database for more information on customer managed keys.
Parent topic: Cross Tenancy and Cross-Region Cloning
Prerequisites for Cross Tenancy Cloning
Describes prerequisites for creating a cross tenancy clone where the source database is in one tenancy and the cloned database is in a different tenancy.
You must run the commands to create a cross tenancy clone on the destination tenancy. Before you create a cross tenancy clone you need to define OCI Identity and Access Management groups and policies on the source tenancy, the tenancy that contains the instance you are cloning, and on the destination tenancy. The groups and policies you define allow you to run commands to create the clone on the destination tenancy and allow the destination tenancy to contact the source tenancy where the source Autonomous Database instance resides.
The OCI Identity and Access Management groups and policies you add support the following:
-
A member of a group in the source tenancy allows a group in the destination tenancy to access (read) the source Autonomous Database instance on the source tenancy.
You do not need to allow other actions on the source Autonomous Database instance (for example, start, stop terminate, or any write operations).
-
A member of a group in the destination tenancy is allowed to create a clone in the destination tenancy using the Autonomous Database instance in the source tenancy as the clone source.
On the destination tenancy you also add a policy that allows a group to manage the Autonomous Database instance on the source tenancy. For example, this policy allows the group to create the clone database, and allows a refreshable clone to run commands that contact the source tenancy, such as Refresh and Disconnect.
To create a cross tenancy clone use OCI Identity and Access Management to create the required groups and to define the policies that authorize cross tenancy cloning:
See Getting Started with Policies for more information.
Parent topic: Cross Tenancy and Cross-Region Cloning
Create a Cross Tenancy or Cross-Region Clone
Shows the steps to create a cross tenancy clone when the source database and the cloned database are in the same region, or when the source database and the cloned database are in different regions (cross-region).
These steps cover creating a Full clone or a Metadata clone. See Create a Cross Tenancy or Cross-Region Refreshable Clone for details on creating a cross tenancy refreshable clone.
The cross tenancy cloning option is only available using the CLI or the Autonomous Database REST APIs. This option is not available using the Oracle Cloud Infrastructure Console.
To create a cross tenancy clone:
-
For information about using the API and signing requests, see REST APIs and Security Credentials.
-
For information about SDKs, see Software Development Kits and Command Line Interface.
Parent topic: Cross Tenancy and Cross-Region Cloning
Create a Cross Tenancy Clone from a Backup
Shows the steps to create a cross tenancy clone from a backup.
These steps cover creating a Full clone or a Metadata clone. See Create a Cross Tenancy or Cross-Region Refreshable Clone for details on creating a cross tenancy refreshable clone.
The cross tenancy cloning option is only available using the CLI or the Autonomous Database REST APIs. This option is not available using the Oracle Cloud Infrastructure Console.
To create a cross tenancy clone from a backup:
-
For information about using the API and signing requests, see REST APIs and Security Credentials.
-
For information about SDKs, see Software Development Kits and Command Line Interface.
Parent topic: Cross Tenancy and Cross-Region Cloning