Acrolinx

Author: whhender

articles/purview/concept-best-practices-migration.md

@@ -11,18 +11,18 @@ ms.date: 12/09/2021
 
 # Microsoft Purview backup and recovery for migration best practices  
 
-This article provides guidance on backup and recovery strategy when your organization has Microsoft Purview in production deployment. You can also use this general guideline to implement account migration. The scope of this article is to cover [manual BCDR methods](disaster-recovery.md) where you could automate using APIs. There is some key information to consider upfront: 
+This article provides guidance on backup and recovery strategy when your organization has Microsoft Purview in production deployment. You can also use this general guideline to implement account migration. The scope of this article is to cover [manual BCDR methods](disaster-recovery.md) where you could automate using APIs. There's some key information to consider upfront: 
 
-- It is not advisable to back up "scanned" assets' details. You should only back up the curated data such as mapping of classifications and glossaries on assets. The only case when you need to back up assets' details is when you have custom assets via custom `typeDef`.
+- It isn't advisable to back up "scanned" assets' details. You should only back up the curated data such as mapping of classifications and glossaries on assets. The only case when you need to back up assets' details is when you have custom assets via custom `typeDef`.
 
-- The backed-up asset count should be fewer than 100,000 assets. The main driver is that you have to use the search query API to get the assets, which has limitation of 100,000 assets returned. However, if you are able to segment the search query to get smaller number of assets per API call, it is possible to back up more than 100,000 assets.
+- The backed-up asset count should be fewer than 100,000 assets. The main driver is that you have to use the search query API to get the assets, which have limitation of 100,000 assets returned. However, if you're able to segment the search query to get smaller number of assets per API call, it's possible to back up more than 100,000 assets.
 
-- The goal is to perform one time migration. If you wish to continuously "sync" assets between two accounts, there are other steps which will not be covered in detail by this article. You have to use [Microsoft Purview's Event Hub to subscribe and create entities to another account](manage-kafka-dotnet.md). However, Event Hub only has Atlas information. Microsoft Purview has added other capabilities such as **glossaries** and **contacts** which won't be available via Event Hub.
+- The goal is to perform one time migration. If you wish to continuously "sync" assets between two accounts, there are other steps that won't be covered in detail by this article. You have to use [Microsoft Purview's Event Hubs to subscribe and create entities to another account](manage-kafka-dotnet.md). However, Event Hubs only has Atlas information. Microsoft Purview has added other capabilities such as **glossaries** and **contacts** which won't be available via Event Hubs.
 
 ## Identify key requirements
 Most of enterprise organizations have critical requirement for Microsoft Purview for capabilities such as Backup, Business Continuity, and Disaster Recovery (BCDR). To get into more details of this requirement, you need to differentiate between Backup, High Availability (HA), and Disaster recovery (DR).
 
-While they are similar, HA will keep the service operational if there was a hardware fault, for example, but it would not protect you if someone accidentally or deliberately deleted all the records in your database. For that, you may need to restore the service from a backup. 
+While they're similar, HA will keep the service operational if there was a hardware fault, for example, but it wouldn't protect you if someone accidentally or deliberately deleted all the records in your database. For that, you may need to restore the service from a backup. 
 
 ### Backup 
 You may need to create regular backups from a Microsoft Purview account and use a backup in case a piece of data or configuration is accidentally or deliberately deleted from the Microsoft Purview account by the users.
@@ -50,7 +50,7 @@ There are three main requirements to take into consideration:
 * **Recovery Level Object (RLO)** – This defines the granularity of the data being restored. It could be a SQL server, a set of databases, tables, records, etc.
 
 ### High availability
-In computing, the term availability is used to describe the period of time when a service is available, and the time required by a system to respond to a request made by a user. For Microsoft Purview, high availability means ensuring that Microsoft Purview instances are available in the case of a problem that is local to a data center or single region in the cloud region.
+In computing, the term availability is used to describe the period of time when a service is available, and the time required by a system to respond to a request made by a user. For Microsoft Purview, high availability means ensuring that Microsoft Purview instances are available if there's a problem that is local to a data center or single region in the cloud region.
 
 #### Measuring availability
 Availability is often expressed as a percentage indicating how much uptime is expected from a particular system or component in a given period of time, where a value of 100% would indicate that the system never fails. 
@@ -88,10 +88,10 @@ This section provides high level guidance on required tasks to copy assets, glos
 1.  Assign contacts to assets
 
 ### Create the new account
-You will need to create a new Microsoft Purview account by following below instruction:
+You'll need to create a new Microsoft Purview account by following below instruction:
 * [Quickstart: Create a Microsoft Purview account in the Azure portal](create-catalog-portal.md)
 
-It’s crucial to plan ahead on configuration items that you cannot change later:
+It’s crucial to plan ahead on configuration items that you can't change later:
 * Account name
 * Region
 * Subscription
@@ -107,20 +107,20 @@ Below steps are referring to [Microsoft Purview API documentation](/rest/api/pur
 |**Scan rule set**|Create and maintain custom scan rule sets. You need to call [List all custom scan rule sets API](/rest/api/purview/scanningdataplane/scan-rulesets/list-all) and get details by calling [Get scan rule set API](/rest/api/purview/scanningdataplane/scan-rulesets/get)|
 |**Manual classifications**|Get a list of all manual classifications by calling get classifications APIs and get details of each classification|
 |**Resource set rule**|Create and maintain resource set rule. You can call the [Get resource set rule API](/rest/api/purview/accountdataplane/resource-set-rules/get-resource-set-rule) to get the rule details|
-|**Data sources**|Call the [Get all data sources API](/rest/api/purview/scanningdataplane/scans/list-by-data-source) to list data sources with details. You also have to get the triggers by calling [Get trigger API](/rest/api/purview/scanningdataplane/triggers/get-trigger). There is also [Create data sources API](/rest/api/purview/scanningdataplane/data-sources/create-or-update) if you need to re-create the sources in bulk in the new account.|
-|**Credentials**|Create and maintain credentials used while scanning. There is no API to extract credentials, so this must be redone in the new account.|
+|**Data sources**|Call the [Get all data sources API](/rest/api/purview/scanningdataplane/scans/list-by-data-source) to list data sources with details. You also have to get the triggers by calling [Get trigger API](/rest/api/purview/scanningdataplane/triggers/get-trigger). There's also [Create data sources API](/rest/api/purview/scanningdataplane/data-sources/create-or-update) if you need to re-create the sources in bulk in the new account.|
+|**Credentials**|Create and maintain credentials used while scanning. There's no API to extract credentials, so this must be redone in the new account.|
 |**Self-hosted integration runtime (SHIR)**|Get a list of SHIR and get updated keys from the new account then update the SHIRs. This must be done [manually inside the SHIRs' hosts](manage-integration-runtimes.md#create-a-self-hosted-integration-runtime).|
 |**ADF connections**|Currently an ADF can be connected to one Microsoft Purview at a time. You must disconnect ADF from failed Microsoft Purview account and reconnect it to the new account later.|
 
 
 ### Run scans
 This will populate all assets with default `typedef`. There are several reasons to run the scans again vs. exporting the existing assets and importing to the new account:
 
-* There is a limit of 100,000 assets returned from the search query to export assets.
+* There's a limit of 100,000 assets returned from the search query to export assets.
 
 * It's cumbersome to export assets with relationships. 
 
-* When you rerun the scans, you will get all relationships and assets details up to date.
+* When you rerun the scans, you'll get all relationships and assets details up to date.
 
 * Microsoft Purview comes out with new features regularly so you can benefit from other features when running new scans.
 
@@ -143,7 +143,7 @@ There are several ways to scope down the search query to get a subset of assets:
 
 *	**Using `Filter`**: Include `assetType` with the specific custom `typedef` in your search such as `"assetType": "<custom_typedef>"`
 
-Here is an example of a search payload by customizing the `keywords` so that only assets in specific storage account (`exampleaccount`) are returned:
+Here's an example of a search payload by customizing the `keywords` so that only assets in specific storage account (`exampleaccount`) are returned:
 
 ```json
 {
@@ -301,9 +301,9 @@ When you re-create the custom entities, you may need to prepare the payload prio
 
 * All `timestamp` value must be null such as `updateTime`, `updateTime`, and `lastModifiedTS`.
 
-* The `guid` cannot be regenerated exactly as before so you have to pass in a negative integer such as "-5000" to avoid error.
+* The `guid` can't be regenerated exactly as before so you have to pass in a negative integer such as "-5000" to avoid error.
 
-* The content of `relationshipAttributes` should not be a part of the payload to avoid errors since it's possible that the `guids` are not the same or have not been created yet. You have to turn `relationshipAttributes` into an empty array prior to submitting the payload. 
+* The content of `relationshipAttributes` shouldn't be a part of the payload to avoid errors since it's possible that the `guids` aren't the same or haven't been created yet. You have to turn `relationshipAttributes` into an empty array prior to submitting the payload. 
 
   * `meanings` contains all glossary mappings, which will be updated in bulk after the entities are created.
 
@@ -315,7 +315,7 @@ To complete the asset migration, you must remap the relationships. There are thr
 
 1. Call the [relationship API](/rest/api/purview/catalogdataplane/relationship/get) to get relationship information between entities by its `guid`
 
-1. Prepare the relationship payload so that there is no hard reference to old `guids` in the old Microsoft Purview accounts. You need to update those `guids` to the new account's `guids`.
+1. Prepare the relationship payload so that there's no hard reference to old `guids` in the old Microsoft Purview accounts. You need to update those `guids` to the new account's `guids`.
 
 1. Finally, [Create a new relationship between entities](/rest/api/purview/catalogdataplane/relationship/create)
 
@@ -347,7 +347,7 @@ Once you have the `glossaryGuid`, you can start to migrate the terms via two ste
 > [!Note]
 > The prerequisite for this step is to have all classifications available in the new account from [Migrate configuration items]() step.
 
-You must call the [discovery API](/rest/api/purview/catalogdataplane/discovery/query) to get the classification assignments to assets. This is applicable to all assets. If you have migrated the custom assets, the information about classification assignments is already available in `classifications` property. Another way to get classifications is to [list classification per `guid`](/rest/api/purview/catalogdataplane/entity/get-classifications) in the old account.
+You must call the [discovery API](/rest/api/purview/catalogdataplane/discovery/query) to get the classification assignments to assets. This is applicable to all assets. If you've migrated the custom assets, the information about classification assignments is already available in `classifications` property. Another way to get classifications is to [list classification per `guid`](/rest/api/purview/catalogdataplane/entity/get-classifications) in the old account.
 
 To assign classifications to assets, you need to [associate a classification to multiple entities in bulk](/rest/api/purview/catalogdataplane/entity/add-classification) via the API.