Clone an Instance Using a Snapshot

After taking a snapshot of an instance, you can use the snapshot to quickly create a clone of the instance.

Note:

Cloning is not supported currently for the following:
  • Instances associated with Oracle Cloud Infrastructure Database or Oracle Autonomous Transaction Processing.
  • Instances where authenication with Oracle Identity Cloud Service is enabled.
  • Instances on Oracle Cloud at Customer created before release 17.4.1.
    To find out whether an instance was created before 17.4.1:
    1. Do one of the following:
      • Send a GET REST API request to the instance. See View a Service Instance in REST API for Oracle Java Cloud Service.
      • Run the CLI command psm jaas service -s serviceInstanceName -of json. See psm jaas service in PaaS Service Manager Command Line Interface Reference.
    2. In the data that the API request or the CLI command returns, search for the line "provisionEngine":"Metadata_x_y" (for example, "provisionEngine":"Metadata_1_0").
      • If the provisionEngine line does not exist, then the instance was created before the 17.4.1 release.
      • If the line exists, then the instance was created after 17.4.1.

To create a clone of an instance, complete the following steps:

  1. Sign in to the web console.
  2. Click the name of the instance that you want to create a clone of.
  3. Click the Administration tile.
  4. Click the Snapshots tab.
  5. Click Menu icon for the snapshot that you want to clone from.
  6. Click Create Clone.
    The instance creation wizard starts.
  7. On the Instance page of the wizard, specify the following attributes:
    Field Description

    Instance Name

    Specify a name for the Oracle Java Cloud Service instance.

    Description

    (Optional) Enter a short description of the Oracle Java Cloud Service instance.

    Notification Email

    (Optional) Specify an email address where you would like to receive a notification of any events occurring with the service instance, including whether provisioning has succeeded or failed.

    Region

    Selected automatically; same as the original instance.

    IP Network

    (Only if a region is selected) (Not available on Oracle Cloud Infrastructure) Select an IP network if you want to create the service instance in an IP network that you’ve defined.

    By default, each node in your instance is auto-assigned a public and a private IP address. The IP addresses might change each time the service instance is restarted. You can reserve and assign fixed public IP addresses.

    In order to select an IP network if you have selected Enable Authentication Using Identity Cloud Service, which automatically configures a managed load balancer, you must first attach an internet-facing load balancer to the IP network.

    This field is not relevant to Oracle Cloud Infrastructure.

    Assign Public IP

    (Not available on Oracle Cloud Infrastructure)

    Choose whether to assign public IP addresses to the nodes in your service instance. You must first select an Oracle Cloud Infrastructure Classic region and specify an IP network.

    If you select this check box (default), then any node added during instance provisioning, or later added as part of a scaling operation, will have a public IP address assigned to it. You will be able to directly access the nodes from the public Internet. This selection is for use cases where you intend to deploy Java EE applications to the Oracle Java Cloud Service instance and access them from the public Internet.

    If you deselect this check box, then any node added during instance provisioning, or later added as part of a scaling operation, will not have a public IP address assigned to it. You will not be able to directly access the nodes from the public Internet. This selection is for use cases where you intend to deploy Java EE applications to the Oracle Java Cloud Service instance and access them only within your IP network or from your on-premises data center over a VPN network.

    Availability Domain

    (Available only on Oracle Cloud Infrastructure)

    Select an availability domain. A region can have multiple isolated availability domains, each with separate power and cooling. The availability domains within a region are interconnected using a low-latency network.

    Note that the database that you intend to associate with your Oracle Java Cloud Service instance can be in a different availability domain within the selected region.

    Subnet

    Select the Oracle Cloud Infrastructure subnet to which the nodes of your instance must be attached.

    This field provides a No Preference option and a list of the available subnets. Each subnet is shown in the format compartmentName | vcnName | subnetName. A tooltip lists the compartment name, VCN name, subnet name, and the OCID of the subnet.

    • To have the subnet assigned automatically, select No Preference. The subnet ManagedCompartmentForPaaS | svc-vcn | svc-subnet-... is used for your instance.

      Note: Don't select No Preference if you plan to associate an Oracle Cloud Infrastructure Database with your service instance.

      If you want to configure security rules for your instance, don’t select No Preference or ManagedCompartmentForPaaS | svc-vcn | svc-subnet-.... Select a subnet in a VCN that you created.

    • To assign a subnet explicitly, select a suitable subnet from the available options.

    • If none of the available subnets meets your networking requirements, then cancel the Create Instance wizard. In Oracle Cloud Infrastructure, create the required VCN and subnets, create policies to allow Oracle Java Cloud Service to use the VCN, and select the appropriate subnet while creating your instance. See Prerequisites for PaaS Services on Oracle Cloud Infrastructure in the Oracle Cloud Infrastructure documentation.

    Database instances in Oracle Database Cloud Service and Oracle Cloud Infrastructure Database must be in the same region and virtual cloud network (VCN) as the Oracle Java Cloud Service instance. The database and service instance do not need to be in the same subnet. The database and service instance can be on different VCNs only if you configure VCN peering.

    Tags

    (Optional) Select existing tags or add tags to associate with the service instance.

    To select existing tags, select one or more check boxes from the list of tags that are displayed on the pull-down menu.

    To create tags, click Plus sign icon to display the Create Tags dialog box. In the New Tags field, enter one or more comma-separated tags that can be a key or a key:value pair.

    If you do not assign tags during provisioning, you can create and manage tags after the service instance is created.

    Bring Your Own License

    The Bring Your Own License (BYOL) option enables you to bring your on-premises Oracle WebLogic Server licenses to Oracle Cloud. BYOL instances are billed at a lower rate than other instances. See Frequently Asked Questions: Oracle BYOL to PaaS.

    You must own a Universal Credits or Government subscription in order to use BYOL.

    BYOL is enabled by default. If you deselect this option, your account will be charged for the new service instance according to your Oracle Java Cloud Service agreement.

    Note: Before you scale up or scale out a BYOL instance, you must have enough WebLogic Server licenses for the additional OCPUs that will be allocated to the instance after it is scaled.

    Service Level

    Selected automatically; same as the original instance.

    Software Release

    Selected automatically; same as the original instance.

    Software Edition

    Selected automatically; same as the original instance.
  8. Click Next.
  9. On the Details page, select the Advanced tab, and specify the following attributes:
    Field Description

    WebLogic Clusters

    Configured automatically; same as the original instance.

    Compute Shape

    Select the compute shape to use for all Administration Server and Managed Server nodes. The compute shape is the number of Oracle Compute Units (OCPUs) and amount of memory (RAM) that you want to allocate to these nodes. The selected shape is not used for Coherence or Load Balancer nodes.

    The list of available shapes varies depending on whether you selected an Oracle Cloud Infrastructure Classic or Oracle Cloud Infrastructure region.

    (Advanced option) When you create multiple WebLogic clusters, you can assign a different compute shape for different clusters. This field displays the compute shape of the selected cluster.

    If you purchased a Universal Credits subscription for Oracle Java Cloud Service, you will pay at the Pay-As-You-Go rate when you exceed your monthly or annual maximum credit.

    Server Count

    Selected automatically; same as the original instance.

    Reserved IPs

    (Not available on Oracle Cloud Infrastructure)

    Select reserved IP addresses for the nodes in your cluster, or leave the default value as Assign Automatically if you want Oracle to automatically assign IP addresses to these nodes. The number of IP addresses that you select must equal the number of nodes in the cluster.

    This option is displayed only if you selected a specific Region for this service instance.

    You create IP reservations by using the Reserved IPs tab in the Oracle Java Cloud Service Console. If you do not see this tab on the console, click the gear icon next to this field and follow the instructions to create your first IP reservation. After creating IP reservations, you need to restart the instance creation wizard.

    Domain Partitions

    Selected automatically; same as the original instance.

    Enable Access to Administration Consoles

    (Advanced option) Select this check box if you want to enable access to the WebLogic Service Administration Console, Fusion Middleware Control, and Load Balancer Console for the service instance. If you do not select this option, these consoles will not be externally accessible, and also will not appear as choices in the service instance’s menu Menu icon.

    Alternatively, you can enable access to the administration consoles after creating the service instance.

    If you are creating this service instance in Oracle Cloud Infrastructure, access to the administration consoles is enabled by default; selecting or deselecting this check box has no effect.

    Deploy Sample Application

    Selected or deselected automatically to match the original instance.

    Enable Authentication Using Identity Cloud Service

    Selected automatically; same as the original instance.

    SSH Public Key

    Specify the public key that will be used for authentication when connecting to a node in your instance by using a Secure Shell (SSH) client.

    Click Edit to display the SSH Public Key for VM Access dialog, and then specify the public key using one of the following methods:

    • Select Key file name and use your web browser to select a file on your machine that contains the public key.

    • Select Key value and paste the value of the public key into the text area. Be sure the value does not contain line breaks or end with a line break.

    • Select Create a New Key if you want Oracle to generate a public/private key pair for you. You will be prompted to download these generated keys.

    If you choose to create a new key, the generated private key file is in OpenSSH format. Before connecting to a node in this service instance with the PuTTY SSH client, you must first convert the key to PuTTY’s proprietary format.

    Local Administrative User Name

    Enter your choice of user name for the WebLogic Server administrator. The default is weblogic. This name is used to access the WebLogic Server Administration Console, Fusion Middleware Control, and Load Balancer Console for the service instance.

    Password

    Specify a password for the WebLogic Server administrator and confirm the password.

    Provision Local Load Balancer

    Selected automatically; same as the original instance.

    Load Balancer

    This option is displayed only if you selected an Oracle Cloud Infrastructure region.

    Selected automatically; same as the original instance.

    Compute Shape

    Select the compute shape to use for all the load balancer nodes in the service instance. The compute shape is the number of Oracle Compute Units (OCPUs) and amount of memory (RAM) that you want to allocate to these nodes.

    The list of available shapes varies depending on whether you selected an Oracle Cloud Infrastructure Classic or Oracle Cloud Infrastructure region.

    You are billed for Oracle Traffic Director nodes at the same price that you are billed for Oracle WebLogic Server nodes in your Oracle Java Cloud Service subscription.

    Add Another Active OTD Node

    This option is displayed only if Provision Local Load Balancer is set to Yes.

    Select this check box to provision a second load balancer node running Oracle Traffic Director (OTD) in this service instance. Both load balancer nodes route traffic to the cluster of WebLogic Managed Servers.

    You can also add a second load balancer node to a service instance after creating the service instance.

    Reserved IPs

    Select reserved IP addresses for the load balancer nodes in your cluster, or leave the default value as Assign Automatically if you want Oracle to automatically assign IP addresses to these nodes. The number of IP addresses that you select must equal the number of load balancer nodes in the service instance.

    This option is displayed only if these conditions are true:

    • You selected a specific Oracle Cloud Infrastructure Classic Region for this service instance.

    • Provision Local Load Balancer is set to Yes

    You create IP reservations by using the Reserved IPs tab in the Oracle Java Cloud Service Console. If you do not see this tab on the console, click the gear icon next to this field and follow the instructions to create your first IP reservation. After creating IP reservations, you need to restart the instance creation wizard.

    Load Balancing Policy

    If you selected Provision Local Load Balancer, choose one of the following policies:

    • Least Connection Count (default)—Passes each new request to the Managed Server with the least number of connections. This policy is useful for smoothing distribution when a Managed Server receives more requests than it can handle efficiently.

    • Least Response Time—Passes each new request to the Managed Server with the fastest response time.

    • Round Robin—Evenly distributes requests across all Managed Servers, regardless of the number of connections or response times.

    Database Instance Name

    Note: Cloning is not supported currently for Oracle Java Cloud Service instances associated with Oracle Cloud Infrastructure Database or Autonomous Transaction Processing.

    The source and the cloned instance can't use the same infrastructure database.

    Select an existing Oracle Database Cloud Service (Classic) deployment or Oracle Database Exadata Cloud Service deployment to connect to this service instance.

    Oracle Java Cloud Service provisions the selected database with the required schemas for running a service instance.

    The list only includes a database deployment if it meets the following criteria:
    • Is in an active state and not currently in the process of being provisioned

    • Is not configured with a Backup Destination set to None (not applicable to Oracle Database Cloud Service — Virtual Image deployments).

    Note the following additional constraints and limitations:

    • To ensure that you can restore the database for an Oracle Java Cloud Service instance without risking data loss for other service instances, Oracle recommends that you do not associate the same infrastructure schema database (or the same pluggable database) with multiple service instances. Backups of a database that is used with multiple Oracle Java Cloud Service instances contain data for all the instances. Therefore, if you restore the database from a backup, data for all the service instances is restored, which might not be the intended result.

    • Oracle Java Cloud Service does not support Oracle Database 18c.

    • If you selected an IP Network for this service instance, you must also select an Oracle Database Cloud Service (Classic) database deployment that is attached to an IP network. If the service instance and database deployment are attached to different IP networks, the two IP networks must be connected to the same IP network exchange.

    • If you selected the Oracle Java Cloud Service— Virtual Image service level, you can select an Oracle Database Cloud Service — Virtual Image database deployment. However, you must configure the Oracle Database Cloud Service — Virtual Image environment before you create this service instance.

    PDB Name

    Specify the pluggable database the service instance will connect to.

    If you don't specify a PDB name, Oracle Java Cloud Service uses the default Oracle Database 12c PDB name that was provided when the Oracle Database Cloud Service (Classic) database deployment was originally created.

    The PDB value doesn't apply to databases running Oracle Database 11g.

    Administrator User Name

    Enter the name of the database administrator that Oracle Java Cloud Service will use to connect to the selected database deployment and to provision the required schemas for this service instance.

    • If you selected the software release Oracle WebLogic Server 11g (11.1.1.7), you can specify the default user SYS or any user that has been granted the DBA role.

    • If you selected the software release Oracle WebLogic Server 12c (any version), you can specify the user SYS or any user that has been granted the SYSDBA privilege.

    Password

    Enter the password for the database administrator.

    Add Application DB

    (Advanced option) Add a up to four database deployments for your application schema.

    Click Add if you want to specify a separate Oracle Database Cloud Service database deployment or Oracle Database Exadata Cloud Service database dedicated for your application schema. When you add an application database, the Oracle Java Cloud Service creates an additional data source in your Oracle WebLogic Server domain to connect to this database.

    Use the Add Database Configuration dialog to select the name of an existing Oracle Database Cloud Service database deployment or Oracle Database Exadata Cloud Service database, and to provide a user name and password for this database.

    Click Add and repeat this process for up to three more database deployments.

    Backup Destination

    (Advanced option) Select Both Remote and Disk Storage if you want to enable automated and on-demand backups for this service instance. Backups will be saved to object storage and to block storage volumes that are attached to the nodes of the instance.

    The default value is None, meaning that you cannot use Oracle Java Cloud Service to take backups of this service instance. You can configure backups on a service instance after creating it.

    This field is not relevant if you selected Oracle Java Cloud Service—Virtual Image.

    Object Storage Container

    This field is displayed only if Backup Destination is set to Both Remote and Disk Storage.

    Enter the object storage location where backups of the service instance must be stored.

    The object storage container field in the instance creation wizard is auto-populated with a default container URL in the format restEndpointUrl/JaaS, where restEndpointUrl is the REST endpoint URL of the Oracle Cloud Infrastructure Object Storage Classic service in the account, and JaaS is the default container name. You can change the container name.

    Note that if the account doesn’t include an Object Storage service entitlement or if the region selected is an Oracle Cloud Infrastructure region, then the container field is not autopopulated.

    • Oracle Cloud Infrastructure Classic: Enter the URL of a container in Oracle Cloud Infrastructure Object Storage Classic.

      Format: rest_endpoint_url/containerName

      You can find the REST endpoint URL of the Oracle Cloud Infrastructure Object Storage Classic service instance in the Infrastructure Classic Console.

      Example: https://acme.storage.oraclecloud.com/v1/MyService-acme/MyContainer

      Note: You can select the Create Object Storage Container check box to have a new container created automatically.

    • Oracle Cloud Infrastructure: Enter the URL of a bucket in Oracle Cloud Infrastructure Object Storage. See Prerequisites for PaaS Services on Oracle Cloud Infrastructure in the Oracle Cloud Infrastructure documentation.

      Format: https://swiftobjectstorage.region.oraclecloud.com/v1/namespace/bucket

      To find out your namespace, sign in to the Oracle Cloud Infrastructure web console, click the tenancy name, and look for the Object Storage Namespace field.

      Example: https://swiftobjectstorage.us-phoenix-1.oraclecloud.com/v1/myCompany/myBucket

    User Name

    This field is displayed only if Backup Destination is set to Both Remote and Disk Storage.

    In Oracle Cloud Infrastructure Classic regions only, this field is not displayed if you selected Enable Authentication Using Identity Cloud Service.

    • Oracle Cloud Infrastructure Classic: Enter the user name of the Oracle Cloud Infrastructure Object Storage Classic service user who created the container you specified earlier. If the container doesn’t exist, then enter the user name of a service administrator.

    • Oracle Cloud Infrastructure: Enter the user name of the Oracle Cloud Infrastructure Object Storage user who created the bucket you specified earlier.

    Password

    This field is displayed only if Backup Destination is set to Both Remote and Disk Storage.

    In Oracle Cloud Infrastructure Classic regions only, this field is not displayed if you selected Enable Authentication Using Identity Cloud Service.

    • Oracle Cloud Infrastructure Classic: Enter the password of the user you specified.

    • Oracle Cloud Infrastructure: Enter the Auth Token generated in Oracle Cloud Infrastructure for the user you specified. See Prerequisites for PaaS Services on Oracle Cloud Infrastructure in the Oracle Cloud Infrastructure documentation.

    Create Object Storage Container

    This option is displayed only if Backup Destination is set to Both Remote and Disk Storage.

    If the Oracle Cloud Infrastructure Object Storage Classic container that you specified doesn’t exist, or if you aren’t sure whether it exists, then select this check box. If the container doesn’t exist, it will be created automatically.

    This option is not relevant to Oracle Cloud Infrastructure. The specified Oracle Cloud Infrastructure Object Storage bucket must exist prior to creating a service instance.

    Provision Data Grid Cluster

    Selected automatically; same as the original instance.

    Compute Shape

    Selected automatically; same as the original instance.

    Cluster Size

    Selected automatically; same as the original instance.

    Managed Servers Per Node

    Selected automatically; same as the original instance.
  10. Click Next.
  11. On the Confirmation page, review the attributes you configured.
    • To make changes, click Back and make the necessary changes.
    • To proceed with creating the clone, click Create.

After the clone is created, the Snapshots tab shows the cloned instance under Cloned Services.

On the Instances page of the web console, cloned instances are indicated by the Cloud with coffee cup icon.

Note:

In Oracle Cloud Infrastructure Classic and Oracle Cloud at Customer, if you create a clone from a colocated snapshot (Colocated snapshot icon), you can't take a snapshot of the cloned instance.