The following are questions and answers that you might have when you use your Azure Import/Export service to transfer data into Azure storage.
Yes. The Azure Import/Export service supports import into Azure Files storage, but it doesn't support data export from Azure Files at this time.
Yes. Azure Import/Export service supports Cloud Solution Providers (CSP) subscriptions.
Can I use the Azure Import/Export service to copy PST mailboxes and SharePoint data to Microsoft 365?
Yes. For more information, go to Overview of importing your organization's PST files.
Yes. For more information, go to Offline Backup workflow in Azure Backup.
No. You need to ship your own drives for import and export jobs.
No. Any drive used to import data must be prepared using the Azure WAImportExport tool. Use the tool to also copy data to the drive.
No. Some prechecks are recommended. To check the number of disks required, use the WAImportExport tool's PreviewExport command. For more information, see Previewing Drive Usage for an Export Job. The command helps you preview drive usage for the selected blobs, based on the size of the drives you are going to use. Also check that you can read from and write to the hard drive that is shipped for the export job.
Yes. You can cancel a job while it has Creating status. However, after you enter tracking information, a job's status changes to Shipping, and the job can no longer be canceled.
You can view the status for completed jobs for up to 90 days. Completed jobs are deleted after 90 days.
One import or export job can reference only 10 drives in a single job. To ship more than 10 drives, you should create multiple jobs. Drives associated with the same job must be shipped together in the same package. For more information and guidance when data capacity spans multiple disk import jobs, contact Azure Support.
No The current versions of the Azure ImportExport tool (version 1.5.0.300 for blobs and version 2.2.0.300 for files) don't support job repair. You'll need to create a new Import/Export job after you resolve the issues. See Create an import job for blobs or Create an import job for files.
You can ignore the Lease Expired field. Import/Export takes lease on the blob during upload to make sure that no other process can update the blob in parallel. Lease Expired implies that the import or export is no longer uploading to the blob, and the blob is available for your use.
There's no limit to the number of hard disk drives (HDDs) in one shipment. If the disks belong to multiple jobs, we recommend that you:
- Label the disks with corresponding job names.
- Update the jobs with a tracking number suffixed with -1, -2, etc.
Ship only your hard drives in the shipping package. Don't include items like power supply cables or USB cables.
When creating a job, the shipping address is a location that is different from my storage account location. What should I do?
Some storage account locations are mapped to alternate shipping locations. Previously available shipping locations can also be temporarily mapped to alternate locations. Always check the shipping address provided during job creation before shipping your drives.
When shipping my drive, the carrier asks for the data center contact address and phone number. What should I provide?
The phone number and DC address are provided as part of job creation.
After the carrier delivers a physical device, it takes 1 to 3 business days for the delivery to be processed in Azure Import/Export. When processing completes, the order's status changes to Received.
The Azure data center returns the drive that doesn't conform to the supported requirements to you. If only some of the drives in the package meet the support requirements, those drives are processed, and the drives that do not meet the requirements will be returned to you.
No. All drives are encrypted with BitLocker.
Use the Azure portal or Storage Explorer to access the data under your Azure storage account.
After the import is complete, what does my data look like in the storage account? Is my directory hierarchy preserved?
When preparing a hard drive for an import job, the destination is specified by the DstBlobPathOrPrefix field in the dataset CSV. That is the destination container in the storage account to which data from the hard drive is copied. Within this destination container, virtual directories are created for folders from the hard drive and blobs are created for files.
If a drive has files that already exist in my storage account, does the service overwrite existing blobs or files?
Yes. The most recent releases of the Azure ImportExport tool - versions 1.5.0.300 (for blobs) and 2.2.0.300 (for files) - automatically overwrite blobs or files that already exist in your storage if an import includes a file or blob with the same name.
Earlier tool versions renamed an incoming file by default if an existing blob or file had the same name. A Disposition field in the dataset CSV file lets you specify whether to rename, not overwrite, or overwrite the destination file or blob. The Disposition field had this format: Disposition:<rename|no-overwrite|overwrite>.
You can still use the old Azure Import/Export tool with your existing jobs. However, we strongly suggest you move to the current tool version for new import/export jobs because the old tool is being phased out. You'll get a notification in the Azure portal when the old tool is no longer supported. Here's where to find the current tool versions. Download WAImportExport version 1.5.0.300, for blobs. Download WAImportExport version 2.2.0.300, for files.
No. The WAImportExport tool is only compatible with 64-bit Windows operating systems. For a complete list of Supported OS, go to Supported Operating Systems.
- Max Block Blob size is approximately 4.768 TB or 5,000,000 MB.
- Max Page Blob size is 8 TB.
Yes. Azure Import/Export service uses AES-256 BitLocker encryption.