| title | description | author | manager | editor | services | documentationcenter | ms.assetid | ms.service | ms.workload | ms.tgt_pltfrm | ms.devlang | ms.topic | ms.date | ms.author |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Troubleshooting the Azure Import-Export Tool | Microsoft Docs |
Learn about common issues users run into using the Import-Export Tool and how to handle them. |
renashahmsft |
aungoo |
tysonn |
storage |
b91ca5eb-c557-460a-9afc-0590b38471f9 |
storage |
storage |
na |
na |
article |
05/25/2015 |
renash |
The Microsoft Azure Import/Export tool returns error messages if it runs into issues. This topic lists some common issues that users may run into.
When a copy session fails, there are two options:
If the error is retryable, for example if the network share was offline for a short period and now is back online, you can resume the copy session. If the error is not retryable, for example if you specified the wrong source file directory in the command line parameters, you need to abort the copy session. See Preparing Hard Drives for an Import Job for more information about resuming and aborting copy sessions.
If the copy session is the first copy session for a drive, then the error message should state: "The first copy session cannot be resumed or aborted." In this case, you can delete the old journal file and rerun the command.
If a copy session is not the first one for a drive, it can always be resumed or aborted.
The journal file for a drive contains the complete information of copying data to this drive, and it is needed to add more files to the drive and will be used to create an import job. If the journal file is lost, you will have to redo all the copy sessions for the drive.
Setting Up the Azure Import-Export Tool
Preparing Hard Drives for an Import Job
Reviewing Job Status with Copy Log Files
Repairing an Import Job
Repairing an Export Job