-
Notifications
You must be signed in to change notification settings - Fork 626
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update mm-google-step2-scan-assess.md
large Drive migration guide needs update
- Loading branch information
Showing
1 changed file
with
12 additions
and
29 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -52,37 +52,20 @@ Summary and detailed scan reports are available to assist you in troubleshooting | |
|
||
Upon completing your scan, download the scan reports and review/address any large source data owners. | ||
|
||
The more users simultaneously being transferred, the higher our throughput for your migration. Users with large data sets should be broken into smaller Service Accounts to facilitate faster transfers. | ||
|
||
The more tasks simultaneously being transferred, the higher our throughput for your migration. To enable faster transfers, Drives with large data sets should be divided into smaller migration tasks based on their root folders. | ||
> [!IMPORTANT] | ||
> To maximize throughput, **users should not own greater than 100,000 items or 1 TB of data**. The more users you have, and the smaller the amounts of data they own, the faster your migration proceeds. | ||
**Examples**: | ||
|
||
|Size|Action| | ||
|---|---| | ||
|If a user owns more than 400,000 items|Divide the items between four users each with 100,000 items.| | ||
|If a user owns more than 5 TB of data|Divide between five users so that each user owns 1 TB. | | ||
|
||
To create Service Accounts, work with your G-Suite Admin to carry out the following steps: | ||
|
||
1. Once you have identified a large user, determine how many Service Accounts will be required (see example above). | ||
2. Create the Service Accounts in G-Suite and assign them a license. | ||
3. From the original large user, identify the folder(s) you would like to assign to the Service Account. | ||
4. Change the ownership of said folder(s) to the new Service Account. This may require that the original owner first share it with the new owner, where the new owner would have to accept, then the original owner will then have the option to select them as owner. The original owner becomes co-owner of the folder and the permissions will reflect that new status in the Source account. The Folder will no longer appear in their My Files folder but will now appear in Shared with me. | ||
5. When it comes to migrating the Service Account, create a corresponding OneDrive user/SharePoint site to migrate the new Service Account content to. | ||
|
||
When mapping please ensure that each Service Account has its own unique matching Destination account to optimize performance. | ||
|
||
|Source Path|Destination Path| | ||
|---|---| | ||
|[email protected]|[email protected]/[upload folder]*| | ||
|[email protected]|[email protected]/[upload folder]*| | ||
|[email protected]|[email protected]/[upload folder]*| | ||
|[email protected]|[email protected]/[upload folder]*| | ||
|
||
> To maximize throughput, **a migration task should not contain greater than 100,000 items or 1 TB of data**. | ||
To split a Drive into multiple migration tasks, follow these steps: | ||
1. Select **Add Drives** from the command bar. | ||
2. In the side panel that appears, select **Multiple specific Drives**. | ||
3. Download and edit the provided .csv template file to divide the Drive into multiple tasks. For example: | ||
- `[email protected]/folder01` | ||
- `[email protected]/folder02` | ||
- `[email protected]/folder03` | ||
- `[email protected]/folder04` | ||
4. Save the updated .csv file and upload it to create the divided migration tasks. | ||
|
||
Asterisk (*) = optional folder | ||
|
||
## Go to [**Step 3: Copy to migrations**](mm-Google-step3-copy-to-migrations.md) | ||
|