Merge pull request #96083 from mayurigupta13/master

log analytics, storage on vnet, sles 12

Author: PRMerger16

articles/site-recovery/azure-to-azure-support-matrix.md

@@ -5,7 +5,7 @@ author: rayne-wiselman
 manager: carmonm
 ms.service: site-recovery
 ms.topic: article
-ms.date: 11/12/2019
+ms.date: 11/15/2019
 ms.author: raynew
 
 ---
@@ -68,7 +68,7 @@ This table summarizes support for the cache storage account used by Site Recover
 --- | --- | ---
 General purpose V2 storage accounts (Hot and Cool tier) | Supported | Usage of GPv2 is not recommended because transaction costs for V2 are substantially higher than V1 storage accounts.
 Premium storage | Not supported | Standard storage accounts are used for cache storage, to help optimize costs.
-Azure Storage firewalls for virtual networks  | Supported | If you are using firewall enabled cache storage account or target storage account, ensure you ['Allow trusted Microsoft services'](https://docs.microsoft.com/azure/storage/common/storage-network-security#exceptions).
+Azure Storage firewalls for virtual networks  | Supported | If you are using firewall enabled cache storage account or target storage account, ensure you ['Allow trusted Microsoft services'](https://docs.microsoft.com/azure/storage/common/storage-network-security#exceptions).<br></br>Also, ensure that you allow access to at least one subnet of source Vnet.
 
 
 ## Replicated machine operating systems

articles/site-recovery/monitor-log-analytics.md

@@ -5,7 +5,7 @@ author: rayne-wiselman
 manager: carmonm
 ms.service: site-recovery
 ms.topic: conceptual
-ms.date: 11/12/2019
+ms.date: 11/15/2019
 ms.author: raynew
 
 ---
@@ -23,7 +23,7 @@ For Site Recovery, you can Azure Monitor Logs to help you do the following:
 Using Azure Monitor Logs with Site Recovery is supported for **Azure to Azure** replication, and **VMware VM/physical server to Azure** replication.
 
 > [!NOTE]
-> The churn data logs and upload rate logs are only available for Azure VMs replicating to a secondary Azure region.
+> To get the churn data logs and upload rate logs for VMware and physical machines, you need to install a Microsoft monitoring agent on the Process Server. This agent sends the logs of the replicating machines to the workspace.
 
 ## Before you start
 
@@ -50,6 +50,24 @@ We recommend that you review [common monitoring questions](monitoring-common-que
 
 The Site Recovery logs start to feed into a table (**AzureDiagnostics**) in the selected workspace.
 
+## Configure Microsoft monitoring agent on the Process Server to send churn and upload rate logs
+
+You can capture the data churn rate information and source data upload rate information for your VMware/physical machines at on-premises. To enable this, a Microsoft monitoring agent is required to be installed on the Process Server.
+
+1. Go to the Log Analytics workspace and click on **Advanced Settings**.
+2. Click on **Connected Sources** page and further select **Windows Servers**.
+3. Download the Windows Agent (64 bit) on the Process Server. 
+4. [Obtain the workspace ID and key](../azure-monitor/platform/agent-windows.md#obtain-workspace-id-and-key)
+5. [Configure agent to use TLS 1.2](../azure-monitor/platform/agent-windows.md#configure-agent-to-use-tls-12)
+6. [Complete the agent installation](../azure-monitor/platform/agent-windows.md#install-the-agent-using-setup-wizard) by providing the obtained workspace ID and key.
+7. Once the installation is complete, go to Log Analytics workspace and click on **Advanced Settings**. Go to the **Data** page and further click on **Windows Performance Counters**. 
+8. Click on **'+'** to add the following two counters with sample interval of 300 seconds:
+
+        ASRAnalytics(*)\SourceVmChurnRate 
+        ASRAnalytics(*)\SourceVmThrpRate 
+
+The churn and upload rate data will start feeding into the workspace.
+
 
 ## Query the logs - examples
 
@@ -169,12 +187,9 @@ AzureDiagnostics  
 ```
 ![Query machine RPO](./media/monitoring-log-analytics/example2.png)
 
-### Query data change rate (churn) for a VM
-
-> [!NOTE] 
-> The churn information is only available for Azure VMs replicating to a secondary Azure region.
+### Query data change rate (churn) and upload rate for an Azure VM
 
-This query plots a trend graph for a specific Azure VM (ContosoVM123), that tracks the data change rate (Write Bytes per Second), and data upload rate. 
+This query plots a trend graph for a specific Azure VM (ContosoVM123), that represents the data change rate (Write Bytes per Second), and data upload rate. 
 
 ```
 AzureDiagnostics   
@@ -189,6 +204,23 @@ Category contains "Upload", "UploadRate", "none") 
 ```
 ![Query data change](./media/monitoring-log-analytics/example3.png)
 
+### Query data change rate (churn) and upload rate for a VMware or physical machine
+
+> [!Note]
+> Ensure you set up the monitoring agent on the Process Server to fetch these logs. Refer [steps to configure monitoring agent](#configure-microsoft-monitoring-agent-on-the-process-server-to-send-churn-and-upload-rate-logs).
+
+This query plots a trend graph for a specific disk **disk0** of a replicated item **win-9r7sfh9qlru**, that represents the data change rate (Write Bytes per Second), and data upload rate. You can find the disk name on **Disks** blade of the replicated item in the recovery services vault. Instance name to be used in the query is DNS name of the machine followed by _ and disk name as in this example.
+
+```
+Perf
+| where ObjectName == "ASRAnalytics"
+| where InstanceName contains "win-9r7sfh9qlru_disk0"
+| where TimeGenerated >= ago(4h) 
+| project TimeGenerated ,CounterName, Churn_MBps = todouble(CounterValue)/5242880 
+| render timechart
+```
+Process Server pushes this data every 5 minutes to the Log Analytics workspace. These data points represent the average computed for 5 minutes.
+
 ### Query disaster recovery summary (Azure to Azure)
 
 This query plots a summary table for Azure VMs replicated to a secondary Azure region.  It shows VM name, replication and protection status, RPO, test failover status, Mobility agent version, any active replication errors, and the source location.

articles/site-recovery/vmware-physical-azure-support-matrix.md

@@ -5,7 +5,7 @@ author: rayne-wiselman
 manager: carmonm
 ms.service: site-recovery
 ms.topic: conceptual
-ms.date: 11/12/2019
+ms.date: 11/15/2019
 ms.author: raynew
 
 ---
@@ -203,7 +203,7 @@ Guest/server - exclude disk | Yes
 Guest/server multipath (MPIO) | No
 Guest/server GPT partitions | Five partitions are supported from [Update Rollup 37](https://support.microsoft.com/help/4508614/) (version 9.25 of the Mobility service) onwards. Previously four were supported.
 ReFS | Resilient File System is supported with Mobility service version 9.23 or higher
-Guest/server EFI/UEFI boot | - Supported for Windows Server 2012 or later, SLES SP4 and RHEL 8.0 <br/> - Secure UEFI boot type is not supported. 
+Guest/server EFI/UEFI boot | - Supported for Windows Server 2012 or later, SLES 12 SP4 and RHEL 8.0 <br/> - Secure UEFI boot type is not supported. 
 
 ## Replication channels