You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/apis/migration-api-overview.md
+60-10Lines changed: 60 additions & 10 deletions
Original file line number
Diff line number
Diff line change
@@ -7,18 +7,21 @@ manager: serdars
7
7
search.appverid: MET150
8
8
description: "This document is to give more in depth information about how to use the SPO Migration API."
9
9
localization_priority: Priority
10
+
ms.service: sharepoint-online
10
11
---
11
12
# SharePoint Import Migration API (CreationMigrationJob)
12
13
13
14
## API Documention
14
15
15
-
The following API description is based upon use of the SharePoint Client Side Object Model (CSOM). We do recommend using NuGet packages when you reference CSOM in your solution. You can find latest version of the SharePoint Online CSOM package from the NuGet library using id of `Microsoft.SharePointOnline.CSOM`.
16
+
The following API description is based upon use of the SharePoint Client Side Object Model (CSOM). We do recommend using NuGet packages when you reference CSOM in your solution.
16
17
17
-
> [!NOTE]
18
-
> You can find latest version of the SharePoint Online Client Side Object Model from [NuGet gallery](https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM/).
18
+
You can find latest version of the SharePoint Online Client Side Object Model (CSOM) package from the [NuGet gallery](https://www.nuget.org/packages/Microsoft.SharePointOnline.CSOM/). Use the ID `Microsoft.SharePointOnline.CSOM`.
19
+
20
+
>[!Important]
21
+
> **Pending change:** Files larger than 15 GB must now create the required checksum using [QuickXorHash](https://docs.microsoft.com/en-us/onedrive/developer/code-snippets/quickxorhash?view=odsp-graph-online). We have provided an example [here](#what-is-stored-in-those-azure-blob-containers).
22
+
>
23
+
>The previous method of MD5Hash is still required for files smaller than 2 GB; however this requirement will be removed at some point in the future.
19
24
20
-
> [!NOTE]
21
-
> The **SharePoint Migration Tool** is not available for users of Office 365 operated by 21Vianet in China. It is also not available for users of Office 365 with the German cloud using the data trustee, *German Telekom*. However, it is supported for users in Germany whose data ___location is not in the German data center.
22
25
23
26
## Methods
24
27
@@ -384,11 +387,13 @@ Several log types can be included such as the full import log, along with warnin
384
387
385
388
## Changes for those using the "Ship Disk" option
386
389
387
-
To use the Migration API, you must have a temporary storage container in Azure. When uploading files into the temporary storage, an MD5 is required as a property on every file. However, when shipping the data on hard drives this MD5 property doesn’t get assigned automatically. As a work around, we have adapted the Migration API to allow the MD5 to be passed for every file as part of the manifest. This also applies for IV values when encrypting the data.
390
+
To use the Migration API, you must have a temporary storage container in Azure. When uploading files into the temporary storage, a checksum is required as a property on every file. For files larger than 15GB, this is done using QuickXorHash (see example below). For files 2 GB or smaller, MD5 is required as a property on every file.
391
+
392
+
However, when shipping the data on hard drives this property doesn’t get assigned automatically. As a work around, we have adapted the Migration API to allow the checksum to be passed for every file as part of the manifest. This also applies for IV values when encrypting the data.
388
393
389
394
Since the MD5 is generated at the source instead of at the upload time in Azure, Microsoft can confirm the integrity of the file directly against the source MD5.
390
395
391
-
###What is stored in those Azure Blob Containers?
396
+
## What is stored in those Azure Blob Containers?
392
397
393
398
The Migration API requires the Azure Container for content passing and also for log and queue reporting. It can be split down as a summary as follows:<br>
394
399
@@ -398,15 +403,60 @@ The Migration API requires the Azure Container for content passing and also for
398
403
399
404
There are two new optional parameters in manifest.xml:
400
405
406
+
- QuickXorHash
401
407
- MD5Hash
402
408
- InitializationVector
403
409
404
-
####Preparing the package
410
+
### Preparing the package
405
411
The method for calling the migration job doesn’t change; only the package generation needs to be changed.
406
412
407
-
In the Manifest container one file is named Manifest.xml. There are 2 optional attributes added to the file node: *MD5Hash* and *InitializationVector*. <br>
413
+
In the Manifest container one file is named Manifest.xml. There are 2 optional attributes added to the file node: *QuickXorHash*,*MD5Hash* and *InitializationVector*. <br>
0 commit comments