Shulou(Shulou.com)06/03 Report--

The previous article shared how to bulk export PST files from Office365 users' mailboxes. This article goes on to share how to bulk upload PST files to a new subscription.

First of all, I applied for a new international Office365 subscription

And I have created four target accounts, which can be seen to be different from my source email account.

Then you still need to grant mailbox import export and retention management permissions to the Exchange administrator, please refer to the previous article. Then enter the Office365 Security and Compliance Center, find the data management, and select Import.

Then select the new import job and fill in the job name

Then the next step is critical, there are two ways, the first is to upload it yourself; the second is to send the hard drive to the nearest Microsoft global data center and ask the engineer to import it for you (this is a fee of $2 / 1GB, of which 1TB=1000GB). Of course, this hard disk will allow you to encrypt the data center engineers need to unlock the hard drive to prevent data leakage during the express delivery.

In line with the principle of free, I still choose the first way to upload PST files by myself. At this time, I need several things, the first PST file, the second user mapping CSV file, the third Azure AzCopy tool, the fourth SAS URL, and the fifth Azure Storage Explorer that is not listed. To put it simply, do your PST data transfer through the temporary storage in Azure, and then transfer it to the new Office365 subscription.

First of all, click "Show Network upload SAS URL" in the following picture, and the URL address will appear. This address is a bit noisy. Remember, this address is needed in many places behind.

The address shown is as follows

Then click next to download the Azure AzCopy tool

Install the tool after the download is complete

Then open the tool.

Execute the following command

AzCopy.exe / Source: / Dest: / V: / Y

Source is the address of the downloaded PST file. You need to add double quotation marks to Dest URL, which is the URL address saved in the above step. You can write any LOG path.

This is how I should fill in my environment.

AzCopy.exe / Source: "C:\ pst files\ export\ 12.20.2018-1126AM\ Exchange" / Dest: "https://cc97886c85ca4904a9d74f9.blob.core.windows.net/ingestiondata?sv=2015-04-05&sr=c&si=IngestionSasForAzCopy201812200748397830&sig=mSTykgu8zzFoknEp8igdKMikzKkzmO5W81t5TbdDnoY%3D&se=2019-01-19T07%3A48%3A42Z" / V:" c:\ pst\ log "/ Y

Wait for the upload to be completed after running the command

Next, you need to download and download Azure Storage Explorer to verify that PST has been uploaded to Azure temporary storage (you don't have to do this as a check, but it's always safe to check the data). Download link

Https://azure.microsoft.com/en-us/features/storage-explorer/

After you have downloaded it, install it.

SAS URL is required to log in to Azure Storage Explorer as a login account

After copy enters, click Next to proceed to the next step.

Then click on the Connect connection

Wait for the connection to succeed (and remember to click on the App) to enter local & Attached- > storage accounts-> (SAS-attached Services)-> Blob Containers-> WangYuan

You can see that the pst file I uploaded with Azure AzCopy has been uploaded.

Then download the CSV template map: https://go.microsoft.com/fwlink/p/?LinkId=544717

Workload can only be Exchange,name which refers to the source PST file, and Mailbox refers to the destination email address. If IsArchive is FALSE, the original mailbox data will not be imported into the archive mailbox of the destination data.

Hit the key point: Name inside the PST file, must pay attention to uppercase, if the file name is uppercase, but use lowercase letters in CSV, will fail! Also, if you want to specify the FilePath parameter, you must pay attention to the difference between PSTfiles and pstfiles, otherwise you are all doing useless work! For more information on how to adjust the parameters in the CSV file, please refer to the following link:

Https://docs.microsoft.com/zh-cn/office365/securitycompliance/use-network-upload-to-import-pst-files?redirectSourcePath=%252farticle%252f103f940c-0468-4e1a-b527-cc8ad13a5ea6#step-4-create-the-pst-import-mapping-file

Next, go back to the upload page of the Security and Compliance Center.

Then upload the csv file next

As a result, the following error was reported, indicating that my PST has not been completely uploaded.

The possible reason is that the temporary storage of Azure to Office365 has not yet been replicated, and it is basically normal after waiting for a few hours. You can't refresh the page or close the page while waiting, or you'll have to regenerate the SAS URL and then, redo it!

After a long wait (about 7 hours), the CSV file is finally verified! Then click Save.

It is indicated that the upload to the cloud is successful.

Then continue to wait for the data analysis of the PST file.

Prepare to filter files and upload after the analysis is complete.

Select Import to Office365

Do the screening according to the actual situation

Then click next.

Next, start importing data.

Indicates that the task was created successfully, but the data was not actually uploaded to Office365

Next, we can check the upload progress.

Then, while waiting slowly, I checked the principle of import, as shown in the following figure.

Download the PST import tool and key to the private Azure storage location-the first step is to download the Azure AzCopy command line tool and the access key for uploading the PST file to the Azure storage location in the Microsoft cloud. You can obtain this content from the Import page of the Office 365Security and Compliance Center. Keys, called secure access signing (SAS) keys, provide you with the permissions you need to upload PST files to a dedicated and secure Azure storage location. This access key is unique to your organization and helps prevent unauthorized access to your PST files, which have been uploaded to the Microsoft cloud. Note that importing PST files into Office 365 does not require your organization to have separate Azure subscriptions.

Upload the PST file to the Azure storage location-the next step is to use the AzCopy.exe tool to upload the PST file and store it in the Azure storage location, which is located in the same area where your Office is located. The Microsoft data center 365 organization is located. To upload them, the PST file that you want to import into Office 365 must be on your organization's file share or file server.

Note that you can perform an optional step to view PST files after they have been uploaded to the Azure storage location.

Create PST Import Mapping File-after uploading the PST file to the Azure storage location, the next step is to create a comma separated value (CSV) file that specifies which user mailboxes to import the PST file into, and note that the PST file can be imported into the user's primary mailbox or its archive mailbox. The Office 365Import service imports the PST file using the information in the CSV file.

Create a PST import job-the next step is to create a PST import job on the Import page of the Security and Compliance Center and submit the PST import mapping file you created in the previous step. After you create an import job, Office 365 analyzes the data in the PST file and then gives you the opportunity to set filters to control the data that is actually imported into the mailbox specified in the PST import mapping file.

Filter the PST data to be imported into the mailbox-after you create and start the import job, Office 365 analyzes the data (secure and reliable) files in the PST file by identifying the age of the project and the different types of messages contained in the PST. After the analysis is complete and you are ready to import the data, you can choose to import all the data contained in the PST file, or you can trim the imported data by setting filters that control the imported data.

Start the PST import job-after starting the import job, Office 365 uses the information in the PST import mapping file to import the PST file from the Azure storage location into the user mailbox. Information about the status of the import job, including information about each PST file to be imported, is displayed on the Import page of the Security and Compliance Center. When the import job is complete, the status of the job is set to complete.

After nearly an hour of waiting, three of the PST files were finally uploaded.

Next, let's log in to the corresponding xiaoa@wy999.onmicrosoft.com account of this account to check, um, we have the previous data!

All right, which account is left for him to upload slowly.

Therefore, when writing this blog, the high-frequency word is: wait!

Because this speed is really too slow, the efficiency is really too low. You can see from the article that there are only 4 accounts in total, and the amount of data is less than 3MB! But it took a whole day! So it is really necessary to do the migration of PST, is this way really acceptable?

This depends on whether the customer will pay the service charge, or how much the service charge will be paid.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.