I was trying to protect Physical Server to Azure and wasn't able to enable replication from the portal..

Hello @Diana Piloya Thank you for contacting us. I see that you are trying to enable replication for your physical and being blocked with errors.

The error codes 539 and 322001 in Azure Site Recovery indicate that there is an issue with the configuration server or the process of enabling replication for a physical server. Here are some steps you can take to troubleshoot these errors:

1. Verify that the configuration server is healthy and running. You can check the status of the configuration server by logging into the server and checking the Azure Site Recovery Configuration Manager. Ensure that the server is connected to the internet and can communicate with the Azure Site Recovery service.
2. Check the credentials used to enable replication. Ensure that the credentials used to enable replication have the necessary permissions to access the physical server. The account used to enable replication should have local administrator privileges on the physical server.
3. Check the firewall settings on the physical server. Ensure that the necessary ports are open on the firewall to allow communication between the physical server and the configuration server. The following ports need to be open on the physical server:
   • TCP 443 (HTTPS)
     • TCP 9443 (HTTPS)
       • TCP 9444 (HTTPS)
4. Check the version of the Azure Site Recovery Mobility service installed on the physical server. Ensure that the latest version of the Mobility service is installed on the physical server. You can download the latest version of the Mobility service from the Azure Site Recovery portal.
5. Check the status of the Azure Site Recovery service. Ensure that the Azure Site Recovery service is running and there are no issues with the service. You can check the status of the service from the Azure portal.

If the above steps do not resolve the issue, you can try disabling and re-enabling replication for the physical server. This will create a new replication policy and may resolve any issues with the existing policy.

Update:

Error 325091: Try the following:

1. Check the replication policy for the server. Ensure that the replication policy is configured correctly and that the RPO is set to a value that is appropriate for the server. If the RPO is set to 5 days, ensure that the server is being replicated at least once every 5 days.
2. Check the replication status for the server. Ensure that the server is replicating successfully and that there are no errors or warnings in the replication status. If there are errors or warnings, address them accordingly.
3. If the issue persists, you can try to force a replication of the server to create a new recovery point. To do this, you can follow these steps:

a. Open the Azure Site Recovery portal and navigate to the replication policy for the server.

b. Click on "Replicate application" and select "Replicate now".

c. Select the server that you want to replicate and click on "OK".

d. Wait for the replication to complete and check the replication status for the server.

For disk high churn rate:
There are no separate or specific guidance from Azure/ASR on re-partitioning disk. One thing, I can tell you that Azure Site Recovery does not support repartitioning disks during replication. If you need to repartition a disk, you should do so before enabling replication. Once replication is enabled, you cannot change the partitioning of the disk.

Here are the general steps to repartition a disk:

1. Open the Disk Management tool by right-clicking on the Start menu and selecting Disk Management.
2. Locate the disk you want to repartition and right-click on it.
3. Select "Shrink Volume" to reduce the size of the existing partition.
4. Once the partition has been shrunk, right-click on the unallocated space and select "New Simple Volume".
5. Follow the prompts to create a new partition with the desired size and format.

It's important to note that repartitioning a disk can result in data loss, so it's important to back up any important data before proceeding. Additionally, as I mentioned earlier, you should repartition the disk before enabling replication with Azure Site Recovery.

Hope this helps. If the problem persists, please contact Microsoft Azure technical support team for further assistance!

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