Defining a Cloud Target (CLI)

After enabling the cloud data service, you can create a cloud target, which is the combination of location, bucket, and data bucket. Each cloud target uses HTTPS certificates assigned to the cloud data service from the system's trust chain and any other uploaded trusted certificates assigned to the service. For information about assigning a certificate to the cloud data service, see Assigning a Certificate to a Service (CLI).

  1. Go to configuration services cloud.
    hostname:> configuration services cloud
  2. Optional: To set the TLS versions and ciphers, enter ls to list the properties, and then set the tls_version and ciphers properties.
  3. Enter targets.
  4. List the properties to configure by entering get.
    hostname:configuration services cloud targets> get
    Properties:
                          name = (unset)
                      location = (unset)
                          user = (unset)
                 databucket_on = false
                        bucket = (unset)
                   data_bucket = (unset)
                       tenancy = (unset)
                           key = (unset)
                      proxy_on = false
                    proxy_host = (unset)
                    proxy_user = (unset)
                proxy_password = (unset)
                    writelimit = (unset)
                     readlimit = (unset)
  5. To modify the properties, use the set command, such as set name=oci-phoenix. The configuration properties are as follows:
    • name - Your name for this cloud target, which must be unique for your system.

    • location - The URL for a regional API endpoint (location), such as https://objectstorage.us-phoenix-1.oraclecloud.com

    • user - Your user name OCID from the Oracle Cloud Infrastructure account.

    • databucket_on - Set this to true if your data and metadata will be in different buckets. Data will be saved to the data_bucket, and metadata will be saved to the bucket. If you use an archive bucket, the metadata must be saved to a standard bucket.

    • bucket - An established bucket name. Data can be saved in either a standard or archive bucket. The combination of location, bucket, and data_bucket must be unique for your system. If you set databucket_on to true, this property is for the metadata bucket; if you set databucket_on to false, this property is for both the metadata and data. To specify a namespace, include it in the bucket name, such as namespace/bucket; for example, export/test2/bucket where export/test2 is the namespace. This can be used to specify a different share name for the target appliance, with the namespace used as the mountpoint.

    • data_bucket - If you set databucket_on to true, this property is for the data bucket; if you set databucket_on to false, this property cannot be set. The combination of location, bucket, and data_bucket must be unique for your system.

    • tenancy - Your tenancy name OCID from the Oracle Cloud Infrastructure account.

    • key - Your private key for the account, which must match the public key uploaded to the Oracle Cloud Infrastructure account. Enter the key in the Privacy Enhanced Mail (PEM) format.

      Use the setkey command to enter the key in an interactive mode, thus allowing multiple lines. When finished entering all lines, enter a period (".").

      hostname:configuration services cloud targets> setkey
      ("." to end)> - - - - -BEGIN RSA PRIVATE KEY- - - - -
      ("." to end)> MD0CAQACCQDJCnSbjr7nUQIDAQABAggQMmdyfF9wgQIFAOQayRsCBQDhoGQDAgRr
      ("." to end)> NWanAGQeHthbAgQeJsyk
      ("." to end)> - - - - -END RSA PRIVATE KEY- - - - -
      ("." to end)> .
    • proxy_on - Set this to true to use a proxy for system communications with the web, and complete the property for proxy_host (host port name and number). The proxy_user (user name) and proxy_password (user password) properties are optional. Example for proxy_host: www-proxy.us.example.com:80.

    • writelimit (optional) - Set to a value and unit of measurement to limit the traffic write bandwidth when uploading a cloud backup to the cloud target. For example, 5M/s limits writes to the cloud target to 5 megabytes per second.

    • readlimit (optional) - Set to a value and unit of measurement to limit the traffic read bandwidth when restoring a cloud backup from the cloud target. For example, 4M/s limits reads from the cloud target to 4 megabytes per second.

  6. When done, enter commit.
    hostname:configuration services cloud (uncommitted)> commit