Merge pull request #104606 from rayne-wiselman/raynefebruary17-2

fixing metadata issues

Author: ktoliver

articles/migrate/common-questions-appliance.md

@@ -2,40 +2,45 @@
 title: Common questions about the Azure Migrate appliance
 description: Get answers to common questions about the Azure Migrate appliance
 ms.topic: conceptual
-ms.date: 11/21/2019
+ms.date: 02/17/2020
 ---
 
 # Azure Migrate appliance: Common questions
 
-This article answers common questions about the Azure Migrate appliance. If you have further queries after reading this article, post them on the [Azure Migrate forum](https://aka.ms/AzureMigrateForum). If you have other questions, review these articles:
+This article answers common questions about the Azure Migrate appliance. If you have other questions, review these articles:
 
 - [General questions](resources-faq.md) about Azure Migrate.
 - [Questions](common-questions-discovery-assessment.md) about the discovery, assessment, and dependency visualization.
 - [Questions](common-questions-server-migration.md) about server migration.
+- Get questions answered on the [Azure Migrate forum](https://aka.ms/AzureMigrateForum). 
 
 
 ## What is the Azure Migrate appliance?
 
-The Azure Migrate appliance is a lightweight appliance used by the Azure Migrate: Server Assessment tool to discover and assess on-premises servers, and used by the Azure Migrate: Server Migration tool for agentless migration of on-premises VMware VMs. 
+The Azure Migrate appliance is a lightweight appliance used by the Azure Migrate:Server Assessment tool to discover and assess on-premises servers. The appliance is also used by the Azure Migrate:Server Migration tool, for agentless migration of on-premises VMware VMs. 
 
-The appliance is deployed on-premises as a VM or physical machine. The appliance discovers on-premises machines, and continually sends machine metadata and performance data to Azure Migrate. Appliance discovery is agentless. Nothing is installed on discovered machines. [Learn more](migrate-appliance.md) about the appliance.
+- The appliance is deployed on-premises as a VM or physical machine.
+- The appliance discovers on-premises machines, and continually sends machine metadata and performance data to Azure Migrate.
+- Appliance discovery is agentless. Nothing is installed on discovered machines.
+
+[Learn more](migrate-appliance.md) about the appliance.
 
 ## How does the appliance connect to Azure?
 
-The connection can be over the internet, or use Azure ExpressRoute with public/Microsoft peering.
+The appliance can connect over the internet, or using Azure ExpressRoute with public/Microsoft peering.
 
 ## Does appliance analysis impact performance?
 
-The Azure Migrate appliance profiles on-premises machines continuously to measure VM performance data. This profiling has almost no performance impact on the Hyper-V/ESXi hosts or on VMware vCenter Server.
+The Azure Migrate appliance profiles on-premises machines continuously to measure performance data. This profiling has almost no performance impact profiled machines.
 
 ### Can I harden the appliance VM?
 
-When you create the appliance VM using the downloaded template, you can add components (for example an antivirus) to the template, as long as you leave the communication and firewall rules required for the Azure Migrate appliance as-is.
+When you create the appliance VM using the downloaded template, you can add components (for example an antivirus) to the template, as long as you leave the communication and firewall rules required for the Azure Migrate appliance in place.
 
 
 ## What network connectivity is needed?
 
-Review the following:
+Review information about network connectivity:
 - VMware assessment using the Azure Migrate appliance: [URL](migrate-appliance.md#url-access) and [port](migrate-support-matrix-vmware.md#port-access) access requirements.
 - VMware agentless migration using the Azure Migrate appliance: [URL](migrate-appliance.md#url-access) and [port](migrate-support-matrix-vmware-migration.md#agentless-ports) access requirements.
 - Hyper-V assessment using the Azure Migrate appliance: [URL](migrate-appliance.md#url-access) and [port](migrate-support-matrix-hyper-v.md#port-access) access requirements.
@@ -51,14 +56,14 @@ Review the collected data:
 
 ## How is data stored?
 
-Data collected by the Azure Migrate appliance is stored in the Azure location that you choose when you created the migration project. 
+Data collected by the Azure Migrate appliance is stored in the Azure location in which you created the Azure Migrate project. 
 
 - The data is securely stored in a Microsoft subscription, and is deleted when you delete the Azure Migrate project.
 - If you use [dependency visualization](concepts-dependency-visualization.md), the data collected is stored in the United States, in a Log Analytics workspace created in the Azure subscription. This data is deleted when you delete the Log Analytics workspace in your subscription.
 
 ## How much data is uploaded in continuous profiling?
 
-The volume of data sent to Azure Migrate depends on a number of parameters. To give you a sense of the volume, an Azure Migrate project with 10 machines (each with one disk and one NIC) sends around 50 MB per day. This value is approximate, and changes based on the number of data points for the NICs and disks. The increase in data sent is non-linear if there's an increase in the number of machines, NICs, or disks.
+The volume of data sent to Azure Migrate depends on a number of parameters. To give you a sense, an Azure Migrate project with 10 machines (each with one disk and one NIC) sends around 50 MB per day. This value is approximate, and changes, based on the number of data points for the NICs and disks. The increase in data sent is non-linear if there's an increase in the number of machines, NICs, or disks.
 
 ## Is data encrypted at-rest/in-transit?
 
@@ -73,37 +78,37 @@ Yes, for both.
 1. The appliance connects to vCenter Server (port 443), using the credentials you provided when you set up the appliance.
 2. The appliance uses VMware PowerCLI to query vCenter Server, to collect metadata about the VMs managed by vCenter Server.
 3. The appliance collects configuration data about VMs (cores, memory, disks, NICs) and the performance history of each VM for the past month.
-4. The collected metadata is ent to Azure Migrate: Server Assessment (over the internet via HTTPS) for assessment.
+4. The collected metadata is sent to Azure Migrate: Server Assessment (over the internet via HTTPS) for assessment.
 
 ## Can I connect the appliance to multiple vCenter Servers?
 
 No. There's a one-to-one mapping between an appliance and vCenter Server. To discover VMs on multiple vCenter Server instances, you need to deploy multiple appliances.
 
-### How many VMs or servers can I discover with an appliance?
+## How many VMs or servers can I discover with an appliance?
 
-You can discover up to 10,000 VMware VMs, up to 5,000 Hyper-V VMs and up to 250 servers with a single appliance. If you have more machines in your on-premises environment, read about scaling [Hyper-V](scale-hyper-v-assessment.md), [VMware](scale-vmware-assessment.md) and [physical](scale-physical-assessment.md) assessment.
+You can discover up to 10,000 VMware VMs, up to 5,000 Hyper-V VMs, and up to 250 physical servers with a single appliance. If you have more machines in your on-premises environment, read about scaling [Hyper-V](scale-hyper-v-assessment.md), [VMware](scale-vmware-assessment.md) and [physical](scale-physical-assessment.md) assessment.
 
 ## Can I delete an appliance?
 
-Currently deletion of appliance from the project isn't supported.
+Currently, deleting an appliance from the project isn't supported.
 
 - The only way to delete the appliance is to delete the resource group that contains the Azure Migrate project associated with the appliance.
 - However, deleting the resource group will also delete other registered appliances, the discovered inventory, assessments, and all other Azure components associated with the project in the resource group.
 
 
 ## Can I use the appliance with a different subscription/project?
 
-After using the appliance to initiate discovery, you can't reconfigure it with a different Azure subscription, or in a different Azure Migrate project. You also can't discover VMs on a different vCenter Server. Set up a fresh appliance for these tasks.
+After using the appliance to initiate discovery, you can't reconfigure it with a different Azure subscription, or use it in a different Azure Migrate project. You also can't discover VMs on a different vCenter Server. Set up a new appliance for these tasks.
 
 ## Can I set up the appliance on an Azure VM?
-Not currently supported. 
+No. This isn't currently supported. 
 
 ## Can I discover on an ESXi host?
-Not you need a vCenter Server to discover VMware VMs.
+No. You need a vCenter Server to discover VMware VMs.
 
 ## How do I update the appliance?
 
-By default, the appliance and its installed agents are updated automatically. The appliance checks for updates once every 24 hours. If there are any failures during the update process, there's a retry process. Automatic updates only update the appliance and appliance agents. The operating system isn't updated. Use Microsoft Updates to keep the operating system up-to-date.
+By default, the appliance and its installed agents are updated automatically. The appliance checks for updates once every 24 hours. If the update process fails, there's a retry. Automatic updates only update the appliance and appliance agents. The operating system isn't updated. Use Microsoft Updates to keep the operating system up-to-date.
 
 ## Can I check agent health?
 

articles/migrate/common-questions-discovery-assessment.md

@@ -2,17 +2,18 @@
 title: Common questions - discovery, assessment, and dependency analysis in Azure Migrate
 description: Get answers to common questions about discovery, assessment, and dependency analysis in Azure Migrate.
 ms.topic: conceptual
-ms.date: 12/29/2019
+ms.date: 02/17/2020
 
 ---
 
 # Common questions about discovery, assessment, and dependency analysis
 
-This article answers common questions about discovery, assessment, and dependency analysis in Azure Migrate. If you have further queries after reading this article, post them on the [Azure Migrate forum](https://aka.ms/AzureMigrateForum). If you have other questions, review these articles:
+This article answers common questions about discovery, assessment, and dependency analysis in Azure Migrate. If you have other questions, review these articles:
 
 - [General questions](resources-faq.md) about Azure Migrate.
 - [Questions](common-questions-appliance.md) about the Azure Migrate appliance.
 - [Questions](common-questions-server-migration.md) about server migration.
+- Post questions on the [Azure Migrate forum](https://aka.ms/AzureMigrateForum)
 
 
 

articles/migrate/common-questions-server-migration.md

@@ -1,56 +1,61 @@
 ---
 title: Common questions about Azure Migrate Server Migration
-description: Get answers to common questions about Azure Migrate Server Migration
+description: Get answers to common questions about migrating machines with Azure Migrate Server Migration
 ms.topic: conceptual
-ms.date: 02/06/2020
+ms.date: 02/17/2020
 ---
 
 # Azure Migrate Server Migration: Common questions
 
-This article answers common questions about the Azure Migrate: Server Migration. If you have further queries after reading this article, post them on the [Azure Migrate forum](https://aka.ms/AzureMigrateForum). If you have other questions, review these articles:
+This article answers common questions about the Azure Migrate:Server Migration tool. If you more questions after reading this article, review these articles:
 
 - [General questions](resources-faq.md) about Azure Migrate.
 - [Questions](common-questions-appliance.md) about the Azure Migrate appliance.
 - [Questions](common-questions-discovery-assessment.md) about the discovery, assessment, and dependency visualization.
+- Post questions on the [Azure Migrate forum](https://aka.ms/AzureMigrateForum).
 
 
 ## How does agentless VMware replication work?
 
-The agentless replication method for VMware uses VMware snapshots, and VMware changed block tracking (CBT). An initial replication cycle is scheduled when the user starts replication. In the initial replication cycle, a snapshot of the VM is taken, and this snapshot is used to replicate the VMs VMDKs (disks). 
-After the initial replication cycle is completed, delta replication cycles are scheduled periodically. In the delta replication cycle, a snapshot is taken, and data blocks that have changed since the previous replication cycle are replicated. VMware changed block tracking is used to determine blocks that have changed since the last cycle.
-The frequency of the periodic replication cycles is automatically managed by the service depending on how many other VMs/disks are concurrently replicating off the same datastore and in ideal conditions will eventually converge to 1 cycle per hour per VM.
+The agentless replication method for VMware uses VMware snapshots, and VMware Changed Block Tracking (CBT).
 
-When you migrate, an on-demand replication cycle is scheduled for the VM to capture any remaining data. You can choose to Shut down the VM as part of the migration to ensure zero data loss and application consistency.
+1. When you start replication, an initial replication cycle is scheduled. In the initial cycle, a snapshot of the VM is taken. This snapshot is used to replicate the VMs VMDKs (disks). 
+2. After the initial replication cycle finishes, delta replication cycles are scheduled periodically.
+    - During delta replication, a snapshot is taken, and data blocks that have changed since the previous replication cycle are replicated.
+    - VMware CBT is used to determine blocks that have changed since the last cycle.
+    - The frequency of the periodic replication cycles is automatically managed by the Azure Migrate, depending on how many other VMs/disks are concurrently replicating from the same datastore. In ideal conditions, replication eventually converges to one cycle per hour for each VM.
 
-## Why is the resynchronization option not exposed in agentless stack?
+When you migrate, an on-demand replication cycle is scheduled for the machine, to capture any remaining data. You can choose to shut down the machine during migration, to ensure zero data loss and application consistency.
 
-In agentless stack, in every delta cycle, we transfer the diff between the current snapshot and the previous snapshot that we had taken. Since it is always a diff between snapshots, this gives the advantage of folding the data (i.e. if a particular sector is written 'n' times between the snapshots, we only need to transfer the last write, as we are interested only in the last sync). This is different from the agent-based stack in which we track every write and apply them. This means every delta cycle is a resynchronization. Hence, there is no resynchronization option exposed. 
+## Why isn't resynchronization exposed?
 
-If ever the disks are out of sync because of a failure, it is fixed in the next cycle. 
+During agentless migration, in every delta cycle the difference between the current snapshot and the previously taken snapshot is written. Since it's always the difference between snapshots, folding data in. So that if a particular sector is written N times between snapshots, only the last write needs to be transferred, as we are interested only in the last sync. This differs from agent-based replication, where we track and apply every write. This means every delta cycle is a resynchronization. Hence, there is no resynchronization option exposed. If ever the disks aren't synchronized because of a failure, it's fixed in the next cycle. 
 
-## What is the impact of churn rate if I use agentless replication?
+## How does churn rate impact agentless replication?
 
-Since the stack is dependent on the data being folded, more than the churn rate, the churn pattern is what matters in this stack. A pattern in which a file is being written again and again doesn’t have much impact. However, a pattern in which every other sector is written will cause high churn in the next cycle. Since we minimize the amount of data we transfer, we allow the data to fold as much as possible before scheduling the next cycle.  
+Since agentless replication folds date, the churn pattern is more important that the churn rate. When a file is written again and again, the rate doesn’t have much impact. However, a pattern in which every other sector is written causes high churn in the next cycle. Since we minimize the amount of data we transfer, we allow the data to fold as much as possible before scheduling the next cycle.  
 
 ## How frequently is a replication cycle scheduled?
 
-The formula to schedule the next replication cycle is this: (Previous cycle time / 2) or 1 hour whichever is higher. For example, if a VM took four hours for a delta cycle, we'll schedule its next cycle in 2 hours and not in the next hour. This is different when the cycle is immediately after IR, where we schedule the first delta cycle immediately.
+The formula to schedule the next replication cycle: (Previous cycle time / 2) or 1 hour, whichever is higher.
 
-## What is the impact on performance of vCenter Server or ESXi host while using agentless replication?
+For example, if a VM takes four hours for a delta cycle, the next cycle is scheduled in two hours, and not in the next hour. This is differs immediately after initial replication, where the first delta cycle is scheduled immediately.
 
-Since agentless replication uses snapshots, there will be IOPs consumption on storage, and customers will need some IOPs headroom on the storage. We don’t recommend using this stack on storage/IOPs constrained environment.
+## How does agentless replication impact VMware servers?
 
-## Does agentless migration stack support migration of UEFI VMs to Azure Gen 2 VMs?
+There is some performance impact on vCenter Server/ESXi hosts. Since agentless replication uses snapshots, it consumes IOPs on storage, and some IOPS storage bandwidth is needed. We don’t recommend using agentless replication if there are constraints on storage/IOPs in your environment.
 
-No, you must use Azure Site Recovery to migrate these VMs to Gen 2 Azure VMs. 
+## Can I do agentless migration of UEFI VMs to Azure Gen 2?
 
-## Can I pin my VMs to Azure Availability Zones when I migrate?
+No. Use Azure Site Recovery to migrate these VMs to Gen 2 Azure VMs. 
 
-No, support for Azure Availability Zones is not there.
+## Can I pin VMs to Azure Availability Zones when I migrate?
+
+No, Azure Availability Zones aren't supported.
 
 ## Which transport protocol is used by Azure Migrate during replication?
 
-Azure Migrate uses Network Block Device (NBD) protocol with SSL encryption.
+Azure Migrate uses the Network Block Device (NBD) protocol with SSL encryption.
 
 ## What is the minimum vCenter Server version required for migration?
 
@@ -60,10 +65,10 @@ You need to have at least vCenter Server 5.5 and VMware vSphere ESXi host versio
 
 No. Azure Migrate supports migration only to managed disks (standard HDD, premium SSD).
 
-## How many VMs can replicate simultaneously using agentless VMware stack?
-
-Currently, customers can migrate 100 VMs per vCenter Server simultaneously. This can be done in batches of 10 VMs.
+## How many VMs can I replicate together with agentless migration?
 
+Currently, you can migrate 100 VMs per vCenter Server simultaneously. Migrate in batches of 10 VMs.
+