ASR Error ID 325097: RPO issue due to system clock

Question

ASR Error ID 325097: RPO issue due to system clock

Justin Sulser 20

Error ID

325097

Error Message

The operating system clock on the machine is skewed by more than 10 minutes.

I'm receiving this error ID on a VMWare server that we have replicated in a site recovery vault. We've confirmed that the system clock is current. Other machines in the vault are also on current time and do not have an issue.

We've re-replicated the machine (disabled and re-enabled replication, did not fully uninstall agent, will be doing that today) and the issue still persists.

Can't seem to find any info online about this, any help?

SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-11-22T19:52:37.3966667+00:00

Hello @Justin Sulser Thank you for reaching out to us with your concern on Microsoft Q&A platform. Happy to assist you!

I see that you have VMware servers replicating to Azure and it started erroring out.

Azure Site Recovery (ASR) Error ID 325097 typically indicates that there is an issue with the configuration of the ASR replication policy. Specifically, this error may occur if the replication policy is configured to use a storage account that is not accessible or has been deleted.

To resolve this issue, you can try the following steps:

Verify that the storage account specified in the ASR replication policy is accessible and has not been deleted. You can do this by navigating to the storage account in the Azure portal and checking its status.

If the storage account has been deleted or is not accessible, update the ASR replication policy to use a different storage account. You can do this by editing the replication policy in the Azure portal or using PowerShell.

If the issue persists, try deleting and recreating the ASR replication policy. This can help to ensure that the policy is configured correctly and is using a valid storage account.

If none of these steps resolve the issue, you may need to contact Microsoft Azure technical support for further assistance.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-11-24T12:49:58.9266667+00:00

@Justin Sulser Have you had a chance to see the previous response? If the suggestions were helpful, click “Accept Answer” and Up-Vote. Feel free to reach out to us if you've additional questions in this regard.
Justin Sulser 20 Reputation points

2023-11-27T14:18:36.6333333+00:00

Hey @SadiqhAhmed-MSFT unfortunately I wasn't able to test those possibilities before I uninstalled, rebooted, and re-installed the Azure Site Replication agent. However, given the fact that I had 5 other servers in Site Replication that had no issues and no changes to replication policies or storage accounts, would that still be the case? In fact, to my knowledge, the server I was having issues with was still uploading to the (modern) Appliance, so I would assume it was reaching the storage account in Azure.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-11-28T06:21:54.1833333+00:00

@Justin Sulser It is strange to know if other 5 servers part of the same replication policy are working properly. If this is the then this could be machine specific issue. Since, you have already performed uninstallation, rebooted server and re-installed the ASR agent. This should help resolve the issue.

Let us know how it goes!
Justin Sulser 20 Reputation points

2023-11-28T14:57:07.8566667+00:00

Thanks, RPO reporting has seemed stable since last week when I uninstalled, rebooted, and re-replicated it, so it was probably something specific to the machine. If the issue ever pops up again, I'll keep your suggestion in mind and maybe we can find the root cause then.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-11-28T15:51:18.3366667+00:00

@Justin Sulser Sure! :)

Accepted answer

0 additional answers

Your answer

SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-11-22T19:52:37.3966667+00:00

Hello @Justin Sulser Thank you for reaching out to us with your concern on Microsoft Q&A platform. Happy to assist you!

I see that you have VMware servers replicating to Azure and it started erroring out.

Azure Site Recovery (ASR) Error ID 325097 typically indicates that there is an issue with the configuration of the ASR replication policy. Specifically, this error may occur if the replication policy is configured to use a storage account that is not accessible or has been deleted.

To resolve this issue, you can try the following steps:

Verify that the storage account specified in the ASR replication policy is accessible and has not been deleted. You can do this by navigating to the storage account in the Azure portal and checking its status.

If the storage account has been deleted or is not accessible, update the ASR replication policy to use a different storage account. You can do this by editing the replication policy in the Azure portal or using PowerShell.

If the issue persists, try deleting and recreating the ASR replication policy. This can help to ensure that the policy is configured correctly and is using a valid storage account.

If none of these steps resolve the issue, you may need to contact Microsoft Azure technical support for further assistance.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-11-24T12:49:58.9266667+00:00

@Justin Sulser Have you had a chance to see the previous response? If the suggestions were helpful, click “Accept Answer” and Up-Vote. Feel free to reach out to us if you've additional questions in this regard.
Justin Sulser 20 Reputation points

2023-11-27T14:18:36.6333333+00:00

Hey @SadiqhAhmed-MSFT unfortunately I wasn't able to test those possibilities before I uninstalled, rebooted, and re-installed the Azure Site Replication agent. However, given the fact that I had 5 other servers in Site Replication that had no issues and no changes to replication policies or storage accounts, would that still be the case? In fact, to my knowledge, the server I was having issues with was still uploading to the (modern) Appliance, so I would assume it was reaching the storage account in Azure.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-11-28T06:21:54.1833333+00:00

@Justin Sulser It is strange to know if other 5 servers part of the same replication policy are working properly. If this is the then this could be machine specific issue. Since, you have already performed uninstallation, rebooted server and re-installed the ASR agent. This should help resolve the issue.

Let us know how it goes!
Justin Sulser 20 Reputation points

2023-11-28T14:57:07.8566667+00:00

Thanks, RPO reporting has seemed stable since last week when I uninstalled, rebooted, and re-replicated it, so it was probably something specific to the machine. If the issue ever pops up again, I'll keep your suggestion in mind and maybe we can find the root cause then.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-11-28T15:51:18.3366667+00:00

@Justin Sulser Sure! :)

Answer 1

Hello @Justin Sulser Thank you for your patience throughout the duration of the issue. I'm re-posting the solution below that worked for you. Because the original poster cannot post the solution and "accept the answer". By this the relevancy of this post will improve when anyone in the community search for a similar query.

<< Sharing the solution below with the broader community >>

Uninstall the Azure Site Replication agent.
Reboot the server
Re-install the Azure Site Replication agent

Note: RPO reporting seemed stable after performing the mentioned steps.

Conclusion: The issue could probably be something specific to the machine.

Hope this helps others who may be looking for solution to the similar issue on this (Microsoft Q&A) forum.

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

Share via

ASR Error ID 325097: RPO issue due to system clock

0 additional answers

Your answer