Data Transfer is an offline data migration service that lets you securely move petabyte-scale datasets from your datacenter to Object Storage or Archive Storage on Oracle Cloud Infrastructure. Using the public internet to move data to the cloud is not always feasible due to high network costs, unreliable network connectivity, long transfer times, and security concerns. The Data Transfer service overcomes these challenges and can significantly reduce the time that it takes to migrate data to the cloud.

You should use Data Transfer when uploading data using public internet connectivity is not feasible. This lack of feasibility may stem from the upload dataset being too large, the internet connection being too slow, or an inability to dedicate the required internet bandwidth for the extended time that it takes to upload data. Data Transfer is also a great alternative when using Oracle FastConnect is not an option, either because your network infrastructure cannot support it or when you cannot justify the FastConnect investment because you do not expect to transfer data frequently.

You can comfortably use Data Transfer to upload hundreds of TB of data to the cloud. Our recommendation is that you consider using Data Transfer if uploading data over the public internet takes longer than 1-2 weeks.

Oracle FastConnect is a network-connectivity alternative to using the public internet for connecting your on-premises datacenter or network with Oracle Cloud Infrastructure. Typically, you would use Oracle FastConnect when you require a dedicated, reliable, and consistent networking experience as compared to public internet-based connections.

FastConnect is a great alternative to Data Transfer. We encourage the use of FastConnect to transfer the data whenever possible. This is especially true if you need to transfer large quantities of data to Oracle on an ongoing basis. However, if investing in FastConnect is not feasible or you don't expect to frequently upload data from your datacenter, then Data Transfer is a great alternative to migrate your data to the cloud.

Two solutions: Data Transfer Appliance and Data Transfer Disk

The Data Transfer Appliance service uses a high-capacity storage appliance that you loan from Oracle for a short duration of time (30 days) to facilitate data migration to the cloud. The transfer appliance is especially useful when you need to migrate a large amount of data, up to 150 TB per appliance. Currently, the Data Transfer Appliance service is available to customers in the United States and the European Union (EU).

The Data Transfer Disk service requires that you purchase your own hard drives to migrate data to the cloud. These hard drives are shipped back to you after the data is transferred successfully to your Object Storage or Archive Storage tenancy. The disk option is practical if you transfer only a relatively small set of data, -if you need more time than 30 days to copy your data for transfer, or if Data Transfer Appliance is not available to you.

This FAQ page covers Data Transfer Appliance. For more information about Data Transfer Disk, see the Data Transfer Disk FAQ webpage.

• Transfer job - A transfer job is the logical representation of a data migration to Oracle Cloud Infrastructure. A transfer job is associated with one transfer appliance.
• Transfer appliance - A transfer appliance is a high-capacity storage device that is specially prepared to copy and upload data securely to Oracle Cloud Infrastructure. You copy your data to one or more appliances and ship these appliances to Oracle to upload your data.

You create a Transfer Job of the type Appliance using the Console, and then click Request Transfer Appliance. Depending on how much data you want to transfer, you may need to order more than one transfer appliance. After Oracle receives and approves your request, a transfer appliance is shipped to the address you specified when creating the request. Download the Oracle Cloud Infrastructure command line interface (CLI) toolset on a Linux host computer at your site that is running a terminal emulator that can access the appliance's serial console. When you receive the transfer appliance, physically connect the appliance to the host computer with the provided USB-DB9 serial cable. Power on the appliance, configure the transfer appliance's networking, and then physically connect the appliance to your network. Initialize the transfer appliance using the Oracle Cloud Infrastructure CLI. Initializing the appliance sets up communication between the host computer (where you installed the CLI) and the transfer appliance. Then, initialize authentication and configure data encryption. Next, create the datasets and NFS mount points needed to write data to the transfer appliance.

After the transfer appliance configuration is complete, copy your data to the appliance using normal file system tools. Then, lock the transfer appliance and ship the appliance back to the Oracle transfer site. You can track the chain of custody of your data by monitoring the status of your transfer appliance using the Console or the CLI. Oracle regularly updates both the status of your transfer job and transfer appliance. After Oracle receives your transfer appliance and uploads your data, a detailed upload summary is generated and posted in the same Object or Archive Storage bucket where the data was uploaded. This report provides a detailed status on every object transferred to Oracle Cloud Infrastructure.

When you purchase Oracle Cloud Infrastructure services using Universal Credits Monthly Flex, you are eligible to use data transfer appliances to migrate your data. To initiate the data transfer process, first request Data Transfer Appliance entitlement through the Oracle Cloud Infrastructure console for your tenancy. The administrator for your tenancy will be required to e-sign a Terms and Conditions document. Once Oracle has confirmed signature of the document you can create a transfer job of type appliance using the Oracle Cloud Console, an easy-to-use, browser-based interface. Next, you request one or more transfer appliances. After Oracle receives and approves your requests, the transfer appliances are shipped to the address you specified when creating the request. You can track the status of your appliance request using either the Console or the CLI.

You can transfer up to 150 TB of data using a single transfer appliance. If you need to transfer more than 150 TB of data, request more than one transfer appliance. Make sure that your tenancy service limits are set appropriately before you request multiple transfer appliances. Review service limits documentation for more details.

The transfer appliance exposes an NFS mount point. You may use NFS version 3, 4, or 4,1 to copy data to the transfer appliance using normal file system commands that copy data to an NFS target.

To transfer a dataset larger than what can fit on a single transfer appliance, you must carefully segment your data into multiple logical datasets and then transfer these datasets using multiple data transfer appliances.

Data Transfer Appliance service is supported in us-phoenix-1, us-ashburn-1, eu-frankfurt-1, uk-london-1, and ap-osaka-1 Oracle Cloud Infrastructure regions. Note that data originating in EU can be shipped only to Frankfurt but then uploaded either to Frankfurt or London.

No. Unfortunately, due to various security and compliance mandates, Oracle does not support shipping the transfer appliance outside the United States, even if the data is meant to be uploaded to one of the Oracle's US regions. For transfers like these, we recommend using Data Transfer Disk service.

Yes, please refer to Data Export section of this document.

Your Linux host will need to have Python version 2.7.5 or 3.5 or later installed. For additional requirements, refer to Command Line Interface Requirements

You can use the Oracle Cloud Infrastructure CLI to validate the configuration of your transfer appliance before sending it to Oracle. This helps catch common mistakes and saves time.

Yes. You must keep a backup of your data until you have confirmed that your data has been successfully uploaded to the target bucket in your tenancy.

Files are uploaded to a target bucket as objects. The name of the object is the flattened path of the file.

If a file is being imported into a bucket and the bucket already has an object of the same name, the file fails to upload, and the existing object remains intact. The upload failure status of the file is logged in the upload summary report.

No. Filesystem metadata is not preserved when being imported to the target bucket. The object name becomes the flattened path to the file. The timestamp is the time the object was created.

Yes. Oracle rigorously maintains the state change of the transfer job and transfer appliance. You can review the status of the job and appliance using the Console or the Oracle Cloud Infrastructure CLI.

If you want to maintain source-side symbolic links, tar up the source directories and copy data over as a monolithic object.

Here are the things you can do if you change your mind about uploading your data to Oracle Cloud Infrastructure:

• You can delete a transfer job early in the transfer process. For example, you initiated the data transfer by creating a transfer job but changed your mind. If you want to delete a transfer job after you requested transfer appliances, you must first delete those appliance requests before you can delete the transfer job. A transfer job cannot be deleted after the job status changes.
• You can delete a transfer appliance request before Oracle approves the request—the status must be Requested. A transfer appliance request cannot be deleted after the appliance status changes to Processing.
• You can cancel the transfer appliance. You can only cancel a transfer appliance after you ship the appliance back to Oracle. Oracle does not process canceled transfer appliances.

You can use the Data Transfer Appliance service to transfer data into any Oracle Cloud Storage Infrastructure service. At the end of the upload process, the transferred data is first available in Object or Archive Storage. From there, customers can use Oracle Cloud Storage Infrastructure tools to copy the data to other services as needed. To get the best performance for copying your data to other services, upload your data to the same region as the target service.

To migrate Oracle databases, create a RMAN backup and choose the transfer appliance as the backup target. Once the appliance is shipped and the data uploaded to Object Storage, you can instantiate a new database instance on an Oracle Cloud Infrastructure compute instance and then restore data from the Object Storage.

You can keep the transfer appliance for 30 days, from when it is delivered to you. If you need to keep the appliance beyond the standard 30-day window, you must request an extension of up to 60 additional days. If you do not return the transfer appliance within 90 days from the time it was delivered to you, Oracle assumes that the appliance is lost and can initiate a transfer appliance recovery process. You may be charged for the full cost of the appliance.

The time it takes to transfer the data to Object Storage depends on the amount of data and the number of objects being transferred. The number of data transfer appliances in queue for processing can also impact how quickly your data is uploaded.

You can track the chain of custody of your data by monitoring the status of your transfer appliance from the Oracle Cloud Infrastructure Console or the Oracle Cloud Infrastructure CLI. Review the Data Transfer service product documentation for complete details.

The data transfer appliance is a purpose-built storage appliance. The appliance is shipped in a ruggedized transit case and special packaging designed to provide sufficient protection against the demands of traditional transportation. When you receive the appliance, you must retain all the original shipping materials and transit case. You will ship the transfer appliance back to Oracle using these same shipping materials.

You can track the transfer appliance shipment using the tracking ID that Oracle provides when the appliance is shipped from Oracle. You can retrieve the tracking ID using the Console or the Oracle Cloud Infrastructure CLI.

In the unlikely event of a transfer appliance being lost in transit, there is little risk of your data being compromised. All data stored on the transfer appliance is by default fully encrypted using AES 256-bit encryption. The encryption password is stored securely in the Oracle Cloud Infrastructure, separate from the transfer appliance. We designed the transfer appliance with security being front and center. Your data is in safe hands.

• If Oracle cannot import your data from the transfer appliance to the Oracle Cloud Infrastructure Object or Archive Storage, we reach out to you (by email and/or phone). We will send you a new transfer appliance to facilitate the data transfer.
• If Oracle is only partially able to upload data from the transfer appliance, you are able to review a comprehensive report of the list of files that we were unable to upload. This upload summary is posted in the same Object Storage bucket where your data was uploaded from the transfer appliance. You can then request additional transfer appliances to resend the data that could not be uploaded in the first attempt.

You can monitor the transfer job status using the Console or the Oracle Cloud Infrastructure CLI. The Transfer Appliance status of Complete indicates that the data has been uploaded successfully into Object or Archive Storage. After the data is uploaded, you are also able to review a detailed upload report that is posted in the same bucket as the data, which details the upload status of each object stored on the appliance.

In the unlikely event that a transfer appliance is damaged during the transit, Oracle sends you a new transfer appliance at no cost. A note of caution: make sure that you do not delete the primary copy of your data until you verify that your data has been fully uploaded to Oracle Cloud Infrastructure.

After your data has been uploaded to your Oracle Cloud Infrastructure tenancy, delete the temporary data transfer upload user. Deleting the data transfer upload user revokes Oracle's access to your data.

When you copy the data to the transfer appliance, a manifest file captures MD5 checksums of all the files. When data is uploaded to your bucket, we match the MD5 checksum from the manifest with the MD5 checksum of the uploaded data to ensure that the integrity of the data has not been compromised during the upload process.

Yes, you can request more than one transfer appliance per transfer job. Ensure that your Data Transfer Appliance service limits are appropriately set before requesting a data transfer appliance. Review service limits documentation for details.

Yes, you can create an unlimited number of Data Transfer Service resources. Review the default Data Transfer service limits.

If you want to raise the default limits for your tenancy, contact Oracle support.

Files up to 10 TiB can be uploaded. Files larger than 10 TiB are skipped in the import process.

File names up to 1024 characters are supported for upload into the Object Storage bucket.

Datasets associated with a specific transfer job can only be moved into one designated bucket. If you need to upload your data to multiple Object Storage buckets, you must create multiple transfer jobs.

Data Export is an offline data migration service that lets you use the Data Transfer Appliance to securely move data out of Oracle Cloud Infrastructure Object Storage or Archive Storage.

Data Export does not support exporting files directly from an Archive Storage bucket. Move your data from the Archive Storage bucket to an Object Storage bucket and then create an export job specifying the Object Storage bucket.

You should use Data Export when you have stored terabytes or petabytes of data in Oracle Cloud Infrastructure and need to retrieve it from Object Storage or Archive Storage more quickly than you could using the public internet. For example, you may have media content or processed datasets you need to share with a customer or business partner.

Data Export does not support exporting files directly from an Archive Storage bucket. Move your data from the Archive Storage bucket to an Object Storage bucket and then create an export job specifying the Object Storage bucket.

To initiate the Data Export process, first request Data Transfer Appliance entitlement through the Oracle Cloud Infrastructure console for your tenancy. The buyer of your tenancy will be required to e-sign a Terms and Conditions document. Once Oracle has confirmed signature of the document you can create a data export job using the Oracle Cloud Infrastructure Console or CLI. As part of your data export job you define boundaries indicating the objects in the bucket that you wish to be included in the export and use the CLI to create a manifest – a list of all objects that will be downloaded from the bucket. You also add policy language to temporarily grant Oracle read access to the bucket where your data resides.

Next, request a transfer appliance to export your data. You may export up to 150 TB of data with each export job. All the data you wish to export must reside in the same bucket. If you need to export more than 150 TB, or if you need to export from more than one bucket, you will need to create additional export jobs and request additional transfer appliances. Make sure that your tenancy service limits are set appropriately before you request multiple transfer appliances. After Oracle receives and approves your requests, your data is ready for Oracle to start the export process.

No. If you wish to export data from more than one bucket you will need to create a Data Export job for each of the buckets from which you wish to export data and will need to request additional transfer appliances. Make sure that your tenancy service limits are set appropriately before you request multiple transfer appliances.

You may not create an export job larger that the capacity of a single transfer appliance (150TB). The manifest file that you create using the CLI indicates the objects you wish to export from your bucket. As the CLI generates the manifest it adds up the capacity and, if it hits the upper limit, will cut off the manifest and let you know that you have reached the limit that can fit on the appliance. You can request additional data transfer appliances and create additional data export jobs to export the remaining amount.

Boundaries allow you to limit the set of objects you wish to export from a bucket. The following parameters are available to limit data included in the data export job:

prefix - The string to use for matching against the start of object names in a list query
start - Object names returned by a list query must be greater or equal to this parameter
end - Object names returned by a list query must be strictly less than this parameter

These parameters are same as the Object API ListObjects parameters.

Yes. You can track the status of your data export job from the CLI. Refer to the online documentation for specific details.

Although there is no rental fee associated with the Data Transfer Appliance, if you are using it for data export, you will incur fees associated with downloading the data from Oracle Cloud Infrastructure Object Storage. Refer to the pricing page.

Data Export service is supported in us-phoenix-1, us-ashburn-1, eu-frankfurt-1, uk-london-1, and ap-osaka-1 Oracle Cloud Infrastructure regions.

No. Unfortunately, due to various security and compliance mandates, Oracle does not support shipping the transfer appliance outside the United States, or outside the European Union or outside Japan.

After setting up NFS exports, you can use standard Linux commands to copy your data to your own systems. You should first make sure you have all your data copied off before deleting it from the appliance to ship back to Oracle.

The appliance itself is tamper evident and tamper resistant. All data stored on the transfer appliance is by default fully encrypted using AES 256-bit encryption. The encryption password is stored securely in the Oracle Cloud Infrastructure, separate from the transfer appliance. When you are ready to copy the data to your desired location, you will retrieve the decryption key from the cloud. Refer to the Security section of this document for more information.

After each use, the transfer appliance is secure wiped using industry-standard processes before the appliance is returned to usable inventory. The transfer appliance is secure wiped even if the same tenant is reusing the appliance for multiple transfer cycles. The secure wipe erasure process follows the NIST 800-88 standards.

The appliance is tamper-resistant in the following ways:

• The appliance's enclosure only exposes power, networking, and serial ports. No other ports are exposed or accessible to customers.
• The appliance's enclosure does not have any externally facing screws or access points. The skin around the enclosure is welded shut, so the only way to open the appliance is to physically break the enclosure.

The appliance is tamper-evident in the following ways:

• Because the enclosure is sealed around the appliance, any physical tampering to open the appliance is visually self-evident.
• The appliance implements digital security measures to enforce end-to-end system integrity.

Customer data stored on the appliance is encrypted using AES-256 encryption. The encryption keys are never stored on the appliance. The encryption keys are privately shared between the customer and Oracle using the Data Transfer service.

Data transfer appliance shipping is free. Oracle pays to ship the transfer appliance to you, and then back to a US or EU Oracle data transfer site.

In the event that your plans change and you are not ready to start using the transfer appliance, you should return the appliance to Oracle using the free return shipping process. You may request another transfer appliance when you are ready; this will help avoid Oracle initiating a transfer appliance recovery process for outstanding, presumed lost appliances – for which you may be charged the full cost of the appliance.

Yes, you can request that each transfer appliance be shipped to a different address. When you request a transfer appliance, you enter the address where that transfer appliance is to be shipped. The shipping address can be unique for each transfer appliance requested.

When you are ready to ship the transfer appliance back to Oracle, carefully pack the transfer appliance using the provided materials. Then ship it back to Oracle using the shipping label that was included in the transfer appliance case.

If you believe that your data transfer appliance is lost in transit, immediately file an Oracle Service Request.

Oracle Cloud Infrastructure customers can use the Data Transfer Appliance service for free. You are only charged for Object Storage usage once the data is successfully transferred to your designated Object Storage bucket. Although there is no rental fee associated with the Data Transfer Appliance, if you are using it for data export, you will incur fees associated with downloading the data from Oracle Cloud Infrastructure Object Storage. Refer to the pricing page.