ASR: How to Enable Debug Logging for the Azure Site Recovery in Hyper-V Site Protection

Summary
This article describes how to enable debug logging (also known as ETL tracing) for Microsoft Azure Site Recovery (ASR) in Hyper-V Site to Azure protection scenerios running on a Windows Server 2012 R2 Hyper-V server. You may use the steps in this article for ASR configured using the Setup Recovery Between an on-premises Hyper-V site and Azure option in the Azure management portal. ASR installations that use Microsoft System Center 2012 R2 Virtual Machine Manager (SC 2012 R2 VMM) should enable VMM Debug Logging instead.

Note: This functionality is enabled by default in the Support Diagnostic Package (SDP) for ASR in Hyper-V. The tool can be downloaded from this link.


More information
To enable debug logging for the ASR Provider, use the following steps:

  1. Open an elevated PowerShell Window and then run the following commands to create your trace definition:
    logman create trace ASRDebug -v mmddhhmm -o C:\temp\asr.etl -cnf 01:00:00 -nb 10 250 -bs 16 -ow -ylogman update ASRDebug -p "Microsoft-Azure Site Recovery-Provider" 0x8000000000000000 0x5logman update ASRDebug -p "MicrosoftAzureRecoveryServices" 0xC000000000000000 0x5 
    Note: The default location specified above is C:\temp. You may safely change this value if needed. The folder will be created if it does not exist.
  2. Start the trace by typing the following command in the elevated Windows PowerShell window:
    logman start ASRDebug
  3. Reproduce your issue.
  4. As soon as you reproduce your issue, stop the trace by typing the following command:
    logman stop ASRDebug
  5. Convert the trace to readable text, type
    netsh trace convert <filename>
    Note: In this command, the placeholder < filename > represents the name of the ETL that you found in step 5. The converted trace file will have a name in the format < filename >.txt.
  6. Collect debug logs from the folder <installation folder>\Temp. The default location will be C:\Program Files\Microsoft Azure Recovery Services Agent\Temp.
  7. Use these steps to collect SRS logs from the Azure Site Recovery portal:
    1. Log on to the Microsoft Azure Portal.
    2. Click Recovery Services.
    3. Select the vault that hosts your ASR data.
    4. Click Jobs.
    5. Click Export Jobs to begin the export process.
    6. Specify a file location, and then click Save to export the job details to an .xlsx file.
  8. wevtutil el | findstr /i microsoftazurerecoveryservices-replication | % { wevtutil qe $_ /f:text}
  9. Run the following PowerShell command to collect Hyper-V logs: wevtutil el | findstr /i hyper-v-vmms | % { wevtutil qe $_ /f:text}
  10. Run the following PowerShell command to collect Hyper-V logs: wevtutil el | findstr /i "microsoft-azure site recovery-provider" | % { wevtutil qe $_ /f:text}

    For additional troubleshooting steps and help in interpreting error messages, please reference this article: https://azure.microsoft.com/documentation/articles/site-recovery-monitoring-and-troubleshooting/#reaching-out-for-microsoft-support


ASR Hyper-V SDP debug logging debug trace ETL ETW logman hyperv azure recovery services azure site recovery
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.
Properties

Article ID: 3033922 - Last Review: 08/24/2015 22:28:00 - Revision: 14.0

Microsoft Azure Recovery Services, Windows Server 2012 R2 Standard

  • kbnosurvey kbprb KB3033922
Feedback