Your search did not match any results.
We suggest you try the following to help find what you're looking for:
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. Looking at the following table, if you have a 100-Mb internet connection that you can solely dedicate to transferring 100 TB of data, it takes more than 100 days to complete data transfer over that connection. You can complete the same transfer using Data Transfer in about a week, including shipping.
|Approximate Data Upload Time*|
|Dataset Size||10 Mbps||100 Mbps||1 Gbps||10 Gbps||Data Transfer Service|
|10 TB||92 Days||9 Days||22 Hours||2 Hours||1 Week|
|100 TB||1,018 Days||101 Days||10 Days||24 Hours||1 Week|
|500 TB||5,092 Days||509 Days||50 Days||5 Days||1 Week|
|1 PB||10,185 Days||1,018 Days||101 Days||10 Days||2 Weeks|
*The data upload times depicted in the table are approximate and must not be construed to be an SLA for the Data Transfer service. The actual time it takes to upload data varies.
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.
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, and uk-london-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.
The Data Transfer Appliance service currently supports importing data from a customer datacenter to the Oracle Cloud Infrastructure. We anticipate data export capability to be supported at a later time.
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 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.
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.
Files up to 10 TB can be uploaded. Files larger than 10 TB are skipped in the import process.
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.
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 is tamper-evident in the following ways:
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.