Preparing for Data Export

Learn about the tasks associated with preparation for the appliance-based data export to your environment.

Prepare phase indicator for data export

This topic describes the tasks associated with preparing for the Data Export job. The Project Sponsor role typically performs these tasks. See Roles and Responsibilities.

Note

You can only run Oracle Cloud Infrastructure CLI commands from a Linux host. This differs from running CLI commands for other Oracle Cloud Infrastructure Services on a variety of host operating systems. Appliance-based commands require validation that is only available on Linux hosts.

Installing and Using the Oracle Cloud Infrastructure Command Line Interface

The Oracle Cloud Infrastructure Command Line Interface (CLI) provides a set of command line-based tools for configuring and running Data Export jobs. Use the Oracle Cloud Infrastructure CLI as an alternative to running commands from the Console. Sometimes you must use the CLI to complete certain tasks as there is no Console equivalent.

Minimum Required CLI Version

The minimum CLI version required for Data Export is 2.12.1.

Determining CLI Versions

Access the following URL to see the currently available version of the CLI:

https://github.com/oracle/oci-cli/blob/master/CHANGELOG.rst

Enter the following command at the prompt to see the version of the CLI currently installed on your machine:

oci --version

If you have a version on your machine older than the version currently available, install the latest version.

Note

Always update to the latest version of the CLI. The CLI is not updated automatically, and you can only access new or updated CLI features by installing the current version.

Linux Operating System Requirements

See Requirements for a list of the Linux operating systems that support the CLI.

Installing the CLI

Installation and configuration of the CLIs is described in detail in Command Line Interface (CLI).

Using the CLI

You can specify CLI options using the following commands:

  • --option value or
  • --option=value

The basic CLI syntax is:

oci dts resource action options

This syntax is applied to the following:

  • oci dts is the shortened CLI command name.

  • job is an example of a resource.

  • create is an example of an action.

  • Other strings are options.

The following command to create an export job shows a typical CLI command construct.

oci dts export create --compartment-id ocid.compartment.oc1..exampleuniqueID --bucket-name MyBucket1 --display-name MyExportJob --addressee "MyCompany Corp" --care-of "John Doe" --address1 "123 Main St." --city-or-locality Anytown --state-province-region CA --country USA --zip-postal-code 12345 --phone-number "555.555.1212" --email jdoe@mycompany.com
Note

In the previous examples, provide a friendly name for the export job using the ‑‑display‑name option.

Accessing Command Line Interface Help

All CLI help commands have an associated help component you can access from the command line. To view the help, enter any command followed by the --help or -h option. For example:


oci dts export --help
			
NAME
dts_export -

DESCRIPTION
Data Transfer Service CLI Specification

AVAILABLE COMMANDS
o change-compartment

o configure-physical-appliance

o create

o create-policy

o delete

o generate-manifest
			
o list

o request-appliance

o setup-notifications

o show

o update

When you run the help option (--help or -h) for a specified command, all the subordinate commands and options for that level of CLI are displayed. If you want to access the CLI help for a specific subordinate command, include it in the CLI string, for example:


oci dts export create --help
			
NAME
dts_export_create -

DESCRIPTION
Creates  a  new  Appliance  Export Job that corresponds with customer's
logical dataset

USAGE
oci dts export create [OPTIONS]

REQUIRED PARAMETERS
--address1 [text]

Address line 1.
			
--addressee [text]

Company or person to send the appliance to

--bucket-name [text]

Name of the object storage bucket for this export job

--care-of [text]

Place/person to direct the package to.

--city-or-locality [text]

:

Setting Up the Oracle Cloud Infrastructure Configuration File

Before using the command line utility, create a configuration file that contains the required credentials for working with Oracle Cloud Infrastructure. You can create this file using a setup dialog or manually using a text editor.

Using the Setup CLI

Run the oci setup config command line utility to walk through the first-time setup process. The command prompts you for the information required for the configuration file and the API public/private keys. The setup dialog generates an API key pair and creates the configuration file.

For more information about how to find the required information, see:

Manual Setup

If you want to set up the API public/private keys yourself and write your own configuration file, see SDK and CLI Configuration File.

Tip

Use the oci setup keys command to generate a key pair to include in the config file.

Create the configuration file /root/.oci/config with the following structure:

[DEFAULT]
user=<The OCID for the data transfer administrator>
fingerprint=<The fingerprint of the above user's public key>
key_file=<The _absolute_ path to the above user's private key file on the host machine>
tenancy=<The OCID for the tenancy that owns the data transfer job and bucket>
region=<The region where the transfer job and bucket should exist. Valid values are: 
us-ashburn-1, us-phoenix-1, eu-frankfurt-1, and uk-london-1, and ap-osaka-1.>

For example:

[DEFAULT]
user=ocid1.user.oc1..unique_ID
fingerprint=4c:1a:6f:a1:5b:9e:58:45:f7:53:43:1f:51:0f:d8:45
key_file=/home/user/ocid1.user.oc1..exampleuniqueID.pem
tenancy=ocid1.tenancy.oc1..unique_ID
region=us-phoenix-1

For the data transfer administrator, you can create a single configuration file that contains different profile sections with the credentials for multiple users. Then use the ‑‑profile option to specify which profile to use in the command. Here is an example of a data transfer administrator configuration file with different profile sections:

[DEFAULT]
user=ocid1.user.oc1..exampleuniqueID
fingerprint=4c:1a:6f:a1:5b:9e:58:45:f7:53:43:1f:51:0f:d8:45
key_file=/home/user/ocid1.user.oc1..exampleuniqueID.pem
tenancy=ocid1.tenancy.oc1..exampleuniqueID
region=us-phoenix-1
[PROFILE1]
user=ocid1.user.oc1..exampleuniqueID
fingerprint=4c:1a:6f:a1:5b:9e:58:45:f7:53:43:1f:51:0f:d8:45
key_file=/home/user/ocid1.user.oc1..exampleuniqueID.pem
tenancy=ocid1.tenancy.oc1..exampleuniqueID
region=us-ashburn-1

By default, the DEFAULT profile is used for all CLI commands. For example:

oci dts export create --compartment-id ocid.compartment.oc1..exampleuniqueID --bucket-name MyBucket --display-name MyDisplay ...

Instead, you can issue any CLI command with the --profile option to specify a different data transfer administrator profile. For example:

oci dts export create --compartment-id ocid.compartment.oc1..exampleuniqueID --bucket-name MyBucket --display-name MyDisplay ... --profile MyProfile

Using the example configuration file above, the profile_name would be profile1.

If you created two separate configuration files, use the following command to specify the configuration file to use:

oci dts export create --compartment-id compartment_id --bucket bucket_name --display-name display_name

Creating the Required IAM Policies

Each service in Oracle Cloud Infrastructure integrates with IAM for authentication and authorization.

To use Oracle Cloud Infrastructure, you must be given the required type of access in a policy  written by an administrator, whether you're using the Console or the REST API with an SDK, CLI, or other tool. If you try to perform an action and get a message that you don't have permission or are unauthorized, confirm with your administrator the type of access you've been granted and which compartment  you should work in.

You provide resource access to the data export administrators group using policies. See Managing Groups for more information.

Create this group using the following policies:

Allow group group-name to manage appliance-export-jobs in compartment compartment-name
Allow group group name to manage buckets in compartment compartment name
Allow group group name to manage objects in compartment compartment name

To enable notifications, add the following policies:

Allow group group name to manage ons-topics in tenancy
Allow group group name to manage ons-subscriptions in tenancy
Allow group group name to manage cloudevents-rules in tenancy
Allow group group name to inspect compartments in tenancy

See Getting Started with Policies for more information.

Requesting Appliance Entitlement

If your tenancy is not entitled to use the Data Transfer Appliance, you must request the Data Transfer Appliance Entitlement before creating an export job.

Establishing the Data Transfer Appliance Entitlement Policy

Use the following policy to enable users in a specific group to request a Data Transfer Appliance Entitlement in your tenancy.

Allow group group_name to {DTA_ENTITLEMENT_CREATE} in tenancy

Entitlement Eligibility

Your request for a Data Transfer Appliance Entitlement in your tenancy may be denied if you are a free trial customer. If your request is denied, upgrade to a full account. You can also contact your Oracle Customer Support Manager or Oracle Support to determine your options for obtaining the entitlement.

Appliance Entitlement Eligibility

Your request for a Data Transfer Appliance Entitlement in your tenancy may be denied if you are a free trial customer. If your request is denied, upgrade to a full account. You can also contact your Oracle Customer Support Manager or Oracle Support to determine your options for obtaining the entitlement.

Using the Console

Open the Transfer Job page and click Request at the top. Otherwise, you are prompted to request the entitlement when attempting to create your first export job.

Once requested, the status of your request is visible at the top of the Transfer Job page. For example:

Data Transfer Appliance Entitlement: Granted

It can take a while to get the Data Transfer Appliance Entitlement approved. After Oracle receives your request, a Terms and Conditions Agreement is sent to the account owner via DocuSign to use the appliance. The entitlement request is approved once the signature is received. The Data Transfer Appliance Entitlement is a tenancy-wide entitlement that you need to request once for each tenancy.

Using the CLI

Use the oci dts appliance request-entitlement command and required parameters to request an appliance entitlement:

oci dts appliance request-entitlement --compartment-id compartment_id --name name --email email

name is the name of the requester.

email is the email address of the requester.

For example:

oci dts appliance request-entitlement --compartment-id ocid.compartment.oc1..exampleuniqueID --name "John Doe" --email jdoe@mycompany.com
					
{
  "data": {
    "compartment-id": "ocid.compartment.oc1..exampleuniqueID",
    "creation-time": "2019-12-18T18:29:15+00:00",
	"defined-tags": {},
	"display-name": null,
	"freeform-tags": {},
	"id": "ocid1.datatransferapplianceentitlement.oc1..exampleuniqueID",
	"lifecycle-state": "CREATING",
	"lifecycle-state-details": "REQUESTED",
	"requestor-email": "rsmith@example.com",
	"requestor-name": "Robert Smith",
    "update-time": "2019-12-20T19:04:09+00:00"
  }
}
Showing the Status of a Data Transfer Appliance Entitlement

Use the oci dts appliance show-entitlement command and required parameters to show the status of your request for an appliance entitlement:

oci dts appliance show-entitlement --compartment-id compartment_id

For example:

oci dts appliance show-entitlement --compartment-id ocid.compartment.oc1..exampleuniqueID 
{
  "data": {
    "compartment-id": ""ocid.compartment.oc1..exampleuniqueID",
    "defined-tags": null,
    "display-name": null,
    "freeform-tags": null,
    "id": null,
    "lifecycle-state": "ACTIVE",
    "lifecycle-state-details": "APPROVED",
    "requestor-email": null,
    "requestor-name": null
  }
}

Setting Up Notifications

Set up rules for the Export Job notification resource that notify the appropriate administrators of the tenancy of events such as when someone creates an export job and when Oracle ships the export appliance.

The types of events you can set up are:

  • CREATE

  • DELETE

  • UPDATE

See Notifications and Overview of Events for more information.

You can also set up notifications for your export job using the CLI. See Setting Up Export Job Notifications for more information on this feature.

Notification Policies

Set up the following policies to support notifications for export jobs:

Allow group group name to manage ons-topics in tenancy
Allow group group name to manage ons-subscriptions in tenancy
Allow group group name to manage cloudevents-rules in tenancy
Allow group group name to inspect compartments in tenancy

Configuring Firewall Settings

The firewall port number is 443 for all data transfer methods.

Ensure that your local environment's firewall can communicate with the Data Transfer Service running on the IP address ranges for your Oracle Cloud Infrastructure region based on the following table. Also ensure that open access exists to the Object Storage IP address range. You only need to configure this IP access for the region where your data transfer job is associated.

Region

Data Transfer

Object Storage

US East (Ashburn)

140.91.0.0/16

134.70.24.0/21

US West (Phoenix)

129.146.0.0/16

134.70.8.0/21

US Gov East (Ashburn)

splat-api.us-langley-1.oraclegovcloud.com

objectstorage.us-gov-ashburn-1.oraclegovcloud.com

US Gov West (Phoenix)

splat-api.us-luke-1.oraclegovcloud.com

objectstorage.us-luke-1.oraclegovcloud.com

US DoD East (Ashburn)

splat-api.us-gov-ashburn-1.oraclegovcloud.com

objectstorage.us-gov-ashburn-1.oraclegovcloud.com

US DoD West (Phoenix)

splat-api.us-gov-phoenix-1.oraclegovcloud.com

objectstorage.us-gov-phoenix-1.oraclegovcloud.com

Brazil East (Sao Paulo)

140.204.0.0/16

134.70.84.0/22

Canada Southeast (Toronto)

140.204.0.0/16

134.70.116.0/22

Germany Central (Frankfurt)

130.61.0.0/16

134.70.40.0/21

India West (Mumbai)

140.204.0.0/16

134.70.76.0/22

Japan Central (Osaka)

140.204.0.0/16

134.70.112.0/22

Japan East (Tokyo)

140.204.0.0/16

134.70.80.0/22

South Korea Central (Seoul)

140.204.0.0/16

134.70.96.0/22

UK South (London)

132.145.0.0/16

134.70.56.0/21

Creating Export Jobs

This section describes how to create an export job as part of the preparation for the data export. See Data Export Reference for complete details on all tasks related to export jobs.

An export job represents the collection of files that you want to export and signals the intention to copy those files from your Oracle Cloud Infrastructure Object Storage or Archive Storage bucket to your data center using an Oracle-provided export appliance. Create the export job in the same compartment as the bucket and supply a human-readable name for the export job.

Note

It is recommended that you create a compartment for each export job to minimize the required access your tenancy.

Creating an export job returns a job ID that you specify in other export tasks. For example:

ocid.compartment.oc1..exampleuniqueID

Using the Console

  1. Open the navigation menu and click Migration & Disaster Recovery. Under Data Transfer, click Exports. The Export Jobs page appears.

  2. Choose a Compartment you have permission to work in under List scope. All export jobs in that compartment are listed in tabular form.

  3. Click Create Export Job. The Create Export Job dialog box appears.

  4. Complete the following:

    • Job Name: Enter the name of the export job.

    • Bucket: Select the bucket that contains the data to be exported from the list. All available buckets for the selected compartment are listed. If you want to select a bucket in a different compartment, click Change Compartment and select the compartment that contains the bucket you want.

    • Company Name: Enter the name of company receiving the exported data.

    • Recipient Phone: Enter the phone number of the recipient contact for the exported data.

    • Recipient Email: Enter the e-mail address of the recipient contact for the exported data.

    • Care Of: Enter the name of the recipient contact for the exported data.

    • Address Line 1: Enter the primary address of the company receiving the exported data.

    • Address Line 2: Enter any additional address information for the company receiving the exported data.

    • City/Locality: Enter the city of locality of the company receiving the exported data.

    • State/Province/Region: Enter the state, province, or region of the company receiving the exported data.

    • Zip/Postal Code: Enter the ZIP code or country postal code of the company receiving the exported data.

    • Country: Enter the country of the company receiving the exported data.

  5. (Optional) Complete the tagging settings:

    • Tag namespace: Select a namespace from the list.

    • Tag key: Enter a tagging key.

    • Tag value: Enter a value for the tagging key.

    See Overview of Tagging for more information.

  6. (Optional) Add any tagging information, including the tag namespace, key, and value in the associated fields.

  7. Click Create.

The export job you created is added to the list of export jobs.

Using the CLI

Use the dts export create command and required parameters to create an export job.

oci dts export create --compartment-id compartment_id --bucket-name bucket_name --display-name display_name --addressee addressee --care-of care_of --address address --city-or-locality city_or_locality --state-province-region state_province_region --country country --zip-postal-code zip_postal_code --phone-number phone_number --email email [OPTIONS]

display_name is the name of the export job as it appears.

addressee is the company or person to receiving the appliance.

care_of is the contact associated with the addressee.

address is the required address of the addressee.

city_or_locality is city or locality of the addressee.

state_province_region is the state, province, or region of the addressee.

country is the country of the addressee.

zip_postal_code is the zip or postal code of the addressee.

phone_number is the phone number of the addressee or contact.

email is the email address of the addressee or contact.

For a complete list of flags and variable options for CLI commands, see the Command Line Reference.

For example:

oci dts export create --compartment-id ocid.compartment.oc1..exampleuniqueID 
--bucket-name MyBucket1 --display-name MyExportJob1 --addressee "Example, Inc." --care-of "Robert Smith" 
--address1 "2300 Oracle Way" --city-or-locality Austin --state-province-region TX --country USA 
--zip-postal-code 78741 --phone-number 6035550100 --email jsmith@example.com

{
  "data": {
    "appliance-decryption-passphrase": "********",
    "appliance-delivery-tracking-number": null,
    "appliance-delivery-vendor": null,
    "appliance-return-delivery-tracking-number": null,
    "appliance-serial-number": null,
    "bucket-access-policies": [
    "POLICIES CREATION IN PROGRESS"
    ],
    "bucket-name": "MyExportJobs",
    "compartment-id": "ocid.compartment.oc1..exampleuniqueID",
    "creation-time": "2020-06-18T17:24:13+00:00",
    "customer-shipping-address": {
      "address1": "2300 Oracle Way",
      "address2": null,
      "address3": null,
      "address4": null,
      "addressee": "Example, Inc.",
      "care-of": "Robert Smith",
      "city-or-locality": "Austin",
      "country": "USA",
      "email": "rsmith@example.com",
      "phone-number": "6035550100",
      "state-or-region": "TX",
      "zipcode": "78741"
    },
    "defined-tags": {},
    "display-name": "MyExportJob1",
    "first-object": null,
    "freeform-tags": {},
    "id": "ocid1.datatransferapplianceexportjob.oc1..exampleuniqueID",
    "last-object": null,
    "lifecycle-state": "CREATING",
    "lifecycle-state-details": "PENDING_MANIFEST_GENERATION",
    "manifest-file": null,
    "manifest-md5": null,
    "next-object": null,
    "number-of-objects": null,
    "prefix": null,
    "range-end": null,
    "range-start": null,
    "receiving-security-tie": null,
    "sending-security-tie": null,
    "total-size-in-bytes": null
  },
  "etag": "4--gzip"
}

Notifications To include notifications, include the --setup-notifications option. See Setting Up Export Job Notifications for more information on this feature.

Getting an Export Job's OCID

Each export job you create has a unique OCID within Oracle Cloud Infrastructure. For example:

ocid1.datatransferapplianceexportjob.oc1..exampleuniqueID

You will need to forward this export job OCID to the Data Administrator.

Using the Console

  1. Open the navigation menu and click Migration & Disaster Recovery. Under Data Transfer, click Exports. The Export Jobs page appears.

  2. Choose a Compartment you have permission to work in under List scope. All export jobs in that compartment are listed in tabular form.

  3. Click the export job whose details you want to get. Click the Actions menu (Actions Menu), and then click View Details. The export job's Details page appears.

The export job OCID is displayed in the details.

Using the CLI

Use the oci dts export list command and required parameters to get the details of an export job:

oci dts export list --compartment-id compartment_id

For a complete list of flags and variable options for CLI commands, see the Command Line Reference.

For example:

oci dts export list --compartment-id ocid.compartment.oc1..exampleuniqueID
				
{
  "data": [
    {
      "bucket-name": "MyExportJobs",
      "creation-time": "2020-06-18T17:24:13+00:00",
      "defined-tags": {},
      "display-name": "MyExportJob1",
      "freeform-tags": {},
      "id": "ocid1.datatransferapplianceexportjob.oc1..exampleuniqueID",
      "lifecycle-state": "CREATING",
      "lifecycle-state-details": "PENDING_MANIFEST_GENERATION"
    },
    {
      "bucket-name": "MyTestExportJobs",
      "creation-time": "2020-06-18T18:07:59+00:00",
      "defined-tags": {},
      "display-name": "MyTestExportJob",
      "freeform-tags": {},
      "id": "ocid1.datatransferapplianceexportjob.oc1..exampleuniqueID",
      "lifecycle-state": "CREATING",
      "lifecycle-state-details": "PENDING_MANIFEST_GENERATION"
    }
  ]
}

The ID for each export job is included in the return:

"id": "ocid1.datatransferapplianceexportjob.oc1..exampleuniqueID"
Tip

When you create an export job using the oci dts export create CLI, the export job ID is displayed in the CLI's return. You can also run the oci dts export show CLI for that specific job to get the ID.

Setting Up Export Job Notifications

You can generate notifications that send messages regarding changes to a new or existing export job through the CLI. Using this feature creates a topic, subscription for a list of email addresses, and a rule that notifies you on all events related to the export job's activities and changes in state. This method provides a more convenient way to generate notifications tailored to export jobs.

The CLI command to set up export job notifications is different depending on whether you are creating a new export job or updating an existing export job. In both cases, running the CLI command prompts you to enter the email addresses of each notification subscriber as a comma separated list. Each recipient is sent an email with a link to confirm they want to receive the notifications.

You are prompted to enter those email addresses you want included in the notifications, separated by commas (","). When your list is complete, add a colon (":") followed by your own email address: user1@mycompany.com,user2@mycompany.com : myemail@mycompany.com.

For both of the notification commands, the following is returned:

If the commands fail to run, you can use the OCI CLI to do the setup manually:
export ROOT_COMPARTMENT_OCID=ocidv1:tenancy:oc1:exampleuniqueID
oci ons topic create --compartment-id $ROOT_COMPARTMENT_OCID --name DTSExportTopic --description "Topic for data transfer service export jobs"
oci ons subscription create --protocol EMAIL --compartment-id $ROOT_COMPARTMENT_OCID --topic-id $TOPIC_OCID --endpoint $EMAIL_ID
oci events rule create --display-name DTSExportRule --is-enabled true --compartment-id $ROOT_COMPARTMENT_OCID --actions '{"actions":[{"actionType":"ONS","topicId":"$TOPIC_OCID","isEnabled":true}]}' --condition '{"eventType":["com.oraclecloud.datatransferservice.addapplianceexportjob","com.oraclecloud.datatransferservice.deleteapplianceexportjob","com.oraclecloud.datatransferservice.updateapplianceexportjob","com.oraclecloud.datatransferservice.moveapplianceexportjob"]}' --description "Rule for data transfer service to send notifications for export jobs"
Creating topic for export
		

When Creating an Export Job

Include the --setup notifications parameter as part of the oci dts export create command:

oci dts export create ... --setup-notifications

Setting Up Notifications for All Export Jobs

Use the dts export setup-notifications command to set up notifications for all export job:

oci dts export setup-notifications

For a complete list of flags and variable options for CLI commands, see the Command Line Reference.

Generating the Export Manifest File

The data export job requires that you generate a manifest file for the files you want to be exported to you in the Data Transfer Appliance. This manifest file is stored in your export job's bucket. Oracle uses the manifest file to download from that bucket all the files that are listed in the manifest. When the Data Transfer Appliance is sent to you, the download summary is available at the root of the Data Transfer Appliance's mount point, allowing you to compare the manifest against the download summary.

Note

You can only use the CLI command to generate the export manifest file.

Using the CLI

Use the oci dts export generate-manifest command and required parameters to generate the export manifest file:

oci dts export generate-manifest --compartment-id compartment_id --job-id job_id --bucket bucket [OPTIONS]

For a complete list of flags and variable options for CLI commands, see the Command Line Reference.

Creating the Data Export Policy

Data export requires you to add the provided policy language to authorize a secure Oracle IAM user to have read-only access to the bucket for export. You must have administrator privileges in your tenancy to create the data export policy.

Using the Console

  1. Open the navigation menu and click Migration & Disaster Recovery. Under Data Transfer, click Exports. The Export Jobs page appears.

  2. Choose a Compartment you have permission to work in under List scope. All export jobs in that compartment are listed in tabular form.

  3. Click the export job whose data export policies you want to access. The export job's Details page appears.

  4. Find the export policies under Policy Language.

  5. Copy and use these policy statements in the policy you create in the Console.

See Getting Started with Policies for more information.

Using the CLI

Use the oci dts export create-policy command and required parameters to create a data export policy.

oci dts export create-policy --job-id job_id

For a complete list of flags and variable options for CLI commands, see the Command Line Reference.

Note

The export create-policy CLI automates the process of generating policies for export job. You do not need to use the Console to create individual policies if you run this CLI.

For example:

oci dts export create-policy --job-id ocid1.datatransferapplianceentitlement.oc1..exampleuniqueID

Setting up the following policies in the root compartment. If the following operation fails it means that you do not have enough privileges to create policies. Re-run the below command with the correct user
NOTE: Sometimes you will need to replace a single quote with '"'"'
oci iam policy create --name e2e-export-test-af3df5176d46_Policy --compartment-id $ROOT_COMPARTMENT --statements '["DEFINE TENANCY OCI_TENANCY AS ocid1.tenancy.oc1..exampleuniqueID", "DEFINE GROUP OCI_EXPORT_GROUP AS ocid1.group.region1..exampleuniqueID", "ADMIT GROUP OCI_EXPORT_GROUP OF TENANCY OCI_TENANCY TO read objects IN TENANCY where target.bucket.name='dtsTestBucket'", "ADMIT GROUP OCI_EXPORT_GROUP OF TENANCY OCI_TENANCY TO read objectstorage-namespaces IN TENANCY"]' --description "The policies to allow DTS to process the export job"

{
  "data": {
    "compartment-id": "ocid1.tenancy.region1..exampleuniqueID",
    "defined-tags": {},
    "description": "The policies to allow DTS to process the export job",
    "freeform-tags": {},
    "id": "ocid1.policy.region1..uniqueID",
    "inactive-status": null,
    "lifecycle-state": "ACTIVE",
    "name": "e2e-export-test-af3df5176d46_Policy",
    "statements": [
      "DEFINE TENANCY OCI_TENANCY AS ocid1.tenancy.oc1..exampleuniqueID",
      "DEFINE GROUP OCI_EXPORT_GROUP AS ocid1.group.region1..exampleuniqueID",
      "ADMIT GROUP OCI_EXPORT_GROUP OF TENANCY OCI_TENANCY TO read objects IN TENANCY where target.bucket.name='dtsTestBucket'",
      "ADMIT GROUP OCI_EXPORT_GROUP OF TENANCY OCI_TENANCY TO read objectstorage-namespaces IN TENANCY"
    ],
    "time-created": "2020-07-09T18:37:23.332000+00:00",
    "version-date": null
  },
  "etag": "20eb7654cd14fcfcaf8648de3c6dcc84d553069f"
}

Requesting the Export Appliance

This section describes how to request an export appliance from Oracle.

Using the Console

  1. Open the navigation menu and click Migration & Disaster Recovery. Under Data Transfer, click Exports. The Export Jobs page appears.

  2. Choose a Compartment you have permission to work in under List scope. All export jobs in that compartment are listed in tabular form.

  3. Click the export job link for which you want to request the export appliance. The export job's Details page appears.

  4. Click Request Export Appliance. The Request Export Appliance dialog box appears prompting you to review the manifest file before continuing with the export appliance request. Review the manifest file to ensure all your export job information, such as the bucket and contact information is correct. If anything is not correct, cancel the application request and correct the export job information before trying again to request an export application.

  5. Click Request.

The Details page is updated to indicate Appliance Requested. The state of your export job is updated to Pending Approval in the list of export jobs.

Using the CLI

Use the dts export request-appliance command and required parameters to request an export appliance.

oci dts export request-appliance --job-id job_id

For a complete list of flags and variable options for CLI commands, see the Command Line Reference.

For example:

oci dts export request-appliance --job-id ocid1.datatransferapplianceentitlement.oc1..exampleuniqueID
					
{
  "data": {
    "appliance-decryption-passphrase": null,
    "appliance-delivery-tracking-number": null,
    "appliance-delivery-vendor": null,
    "appliance-return-delivery-tracking-number": null,
    "appliance-serial-number": null,
    "bucket-access-policies": [
      "DEFINE TENANCY OCI_TENANCY AS ocid1.tenancy.oc1..exampleuniqueID",
      "DEFINE GROUP OCI_EXPORT_GROUP AS ocid1.group.region1..exampleuniqueID",
      "ADMIT GROUP OCI_EXPORT_GROUP OF TENANCY OCI_TENANCY TO read objects IN TENANCY where target.bucket.name='MyExportBucket'",
      "ADMIT GROUP OCI_EXPORT_GROUP OF TENANCY OCI_TENANCY TO read objectstorage-namespaces IN TENANCY"
    ],
    "bucket-name": "MyExportBucket",
    "compartment-id": "ocid1.compartment.region1..exampleuniqueID",
    "creation-time": "2020-07-09T18:36:59+00:00",
    "customer-shipping-address": {
      "address1": "2300 Oracle Way",
      "address2": null,
      "address3": null,
      "address4": null,
      "addressee": "Example, Inc.",
      "care-of": "Robert Smith",
      "city-or-locality": "Austin",
      "country": "USA",
      "email": "rsmith@example.com",
      "phone-number": "6035550100",
      "state-or-region": "TX",
      "zipcode": "78741"
    },
    "defined-tags": {},
    "display-name": "e2e-export-test-af3df5176d46",
    "first-object": "oci_data_export_export-job-37",
    "freeform-tags": {},
    "id": "ocid1.datatransferapplianceexportjob.region1..exampleuniqueID",
    "last-object": "oci_data_export_export-job-40",
    "lifecycle-state": "ACTIVE",
    "lifecycle-state-details": "PENDING_APPROVAL",
    "manifest-file": "oci_data_export_manifest_ocid1.datatransferapplianceexportjob.region1..exampleuniqueID",
    "manifest-md5": "NcEMgcgK2fK8HfvUV3eWAA==",
    "next-object": null,
    "number-of-objects": "2",
    "prefix": null,
    "range-end": "oci_data_export_export-job-50",
    "range-start": "oci_data_export_export-job-37",
    "receiving-security-tie": null,
    "sending-security-tie": null,
    "total-size-in-bytes": "85585303"
  },
  "etag": "1"
}

Tracking the Export Appliance Delivery

Using the Console

  1. Open the navigation menu and click Migration & Disaster Recovery. Under Data Transfer, click Exports. The Export Jobs page appears.

  2. Choose a Compartment you have permission to work in under List scope. All export jobs in that compartment are listed in tabular form.

  3. Click the export job for which you want to display the details. The export job's Details page appears.

The status of the requested export appliance is listed under Appliance Information.

Using the CLI

Use the oci dts export show command and required parameters to get the details of an appliance export transfer job.

oci dts export show --job-id job_id [OPTIONS]

For a complete list of flags and variable options for CLI commands, see the Command Line Reference.

For example:

oci dts export show --job-id ocid1.datatransferapplianceexportjob.oc1..exampleuniqueID

{
  "data": {
    "appliance-decryption-passphrase": "********",
    "appliance-delivery-tracking-number": null,
    "appliance-delivery-vendor": null,
    "appliance-return-delivery-tracking-number": null,
    "appliance-serial-number": null,
    "bucket-access-policies": [
      "POLICIES CREATION IN PROGRESS"
    ],
    "bucket-name": "MyExportJobs",
    "compartment-id": "ocid.compartment.oc1..exampleuniqueID",
    "creation-time": "2020-06-18T17:24:13+00:00",
    "customer-shipping-address": {
      "address1": "2300 Oracle Way",
      "address2": null,
      "address3": null,
      "address4": null,
      "addressee": "Example, Inc.",
      "care-of": "Robert Smith",
      "city-or-locality": "Austin",
      "country": "US",
      "email": "rsmith@example.com",
      "phone-number": "6035550100",
      "state-or-region": "TX",
      "zipcode": "78741"
    },
    "defined-tags": {},
    "display-name": "MyExportJob1",
    "first-object": null,
    "freeform-tags": {},
    "id": "ocid1.datatransferapplianceexportjob.oc1..exampleuniqueID",
    "last-object": null,
    "lifecycle-state": "CREATING",
    "lifecycle-state-details": "PENDING_MANIFEST_GENERATION",
    "manifest-file": null,
    "manifest-md5": null,
    "next-object": null,
    "number-of-objects": null,
    "prefix": null,
    "range-end": null,
    "range-start": null,
    "receiving-security-tie": null,
    "sending-security-tie": null,
    "total-size-in-bytes": null
    },
  "etag": "1--gzip"
}

The status of the requested export appliance is listed in the appliance attributes in the returned information.

Notifying the Data Administrator

When you have completed all the tasks in this topic, provide the Data Administrator of the following:

  • IAM login credentials

  • Oracle Cloud Infrastructure CLI configuration files

  • Export job ID