Share via

ASR -replication issue

jihad majed 400 Reputation points
Nov 11, 2024, 8:20 AM

I have an issue related to replication from HyperV to Azure. I did the configuration of the replication, and I have an issue related to the disk on the host. Every time I did the replication progress, the disk was full due to logs of ASR. How can I reduce that and fix this issue

Azure Site Recovery
Azure Site Recovery
An Azure native disaster recovery service. Previously known as Microsoft Azure Hyper-V Recovery Manager.
728 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. SadiqhAhmed-MSFT 46,866 Reputation points Microsoft Employee
    Nov 11, 2024, 1:45 PM

    @jihad majed Greetings!

    While using Azure Site Recovery for replication from Hyper-V to Azure, it's common to encounter disk space issues related to log accumulation. The replication process generates logs that track changes, and these logs can grow, consuming disk space on the host where ASR is running. To manage these issues, you can follow suggestions below:

    Azure Site Recovery maintains log files for several days by default. To mitigate the issue of excessive log growth, you can configure the log retention settings:

    • Open the Azure Site Recovery console.
    • Navigate to Recovery Plans and select the replication process.
    • In the configuration settings, find the Log Retention Period and adjust the setting to a lower value (e.g., keep logs for only 1-2 days).

    This will prevent the accumulation of unnecessary logs over time, thus saving disk space.

    Increase the disk space available for the ASR logs by adding a new drive or increasing the size of the existing disk.

    You can move the logs generated by ASR to a different location to free up disk space on the Hyper-V host. To do this, you can configure ASR to store the logs on a different disk or on a network share.

    Clear or delete logs: Navigate to the log folder C:\ProgramData\Microsoft\AzureSiteRecovery\Logs. Delete any logs that are no longer needed, but be cautious to leave the most recent logs intact, especially if troubleshooting is required.

    Refer to the troubleshooting guide - https://learn.microsoft.com/en-us/azure/site-recovery/hyper-v-azure-troubleshoot

    Hope this helps. Let us know if you need any further assistance.


    If the response helped, do "Accept Answer" and up-vote it

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.