Microsoft Azure Recovery Services Agent was unable to initialize a backup storage location due to unresponsive VDS service.

Question

Microsoft Azure Recovery Services Agent was unable to initialize a backup storage location due to unresponsive VDS service.

jihad majed 500

SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-16T13:17:32.3933333+00:00
@jihad majed Thank you for reaching out to us with your concern.

If you're seeing the error message "Microsoft Azure Recovery Services Agent was unable to initialize a backup storage location due to unresponsive VDS service" during a backup operation, it means that the Volume Shadow Copy Service (VSS) on the source server is not responding.

Here are some troubleshooting steps you can try:

Restart the VSS service on the source server. You can do this by opening the Services console on the source server, locating the "Volume Shadow Copy" service, and restarting it.

Check the status of the VSS writers on the source server. You can do this by opening a command prompt on the source server and running the command "vssadmin list writers". This will show you the status of all VSS writers on the server. If any writers are in a failed state, you may need to troubleshoot them individually.

Check the event logs on the source server for any VSS-related errors. Look for any errors or warnings related to VSS in the Application or System event logs.

Ensure that the source server meets the system requirements for Azure Backup. Check the Azure Backup documentation for the system requirements for the version of the agent you're using.

Ensure that the latest version of the Azure Recovery Services agent is installed on the source server. You can download the latest version from the Azure portal.

Let us know if that helps!
jihad majed 500 Reputation points

2023-08-17T06:56:38.8533333+00:00

Now we find this error:

The current operation failed due to an internal service error "Invalid input error". Please retry the operation after some time.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-17T07:46:07.4266667+00:00

@jihad majed Can you check CBEngine logs from C:\program files\Microsoft Azure Recovery Services Agent\Temp and see if there are any errors that helps you find the cause of the issue?

If possible, please share the logs with us.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-18T10:59:30.5266667+00:00

@jihad majed Did you find any errors? If possible, share the logs with us via email. Send us an email at AzCommunity @ Microsoft dot com with subject: Attn: Sadiqh Ahmed and a link to this forum thread for context.
jihad majed 500 Reputation points

2023-08-21T05:48:12.9366667+00:00

yes i sent
jihad majed 500 Reputation points

2023-08-21T06:48:36.71+00:00

could you please a tools fo read error file ?
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-21T10:19:28.3533333+00:00

@jihad majed I did not receive any email from you. Could you please send it once again?
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-24T06:37:01.2033333+00:00

@jihad majed Thanks for sending the logs. I reviewed it and couldn't find any specific errors that guides us to the problem or to drive resolution. I suggest reaching out to Azure technical support team to investigate this further.

Let us know if there are any chanllenges contacting Azure technical support team.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-28T06:22:34.92+00:00

@jihad majed Did you get a chance to contact Azure technical support team?
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-29T08:56:23.2+00:00

@jihad majed We haven't heard back from you. Please provide an update on any progress on the issue.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-30T14:12:26.1633333+00:00

@jihad majed Thanks for sharing the summary of the issue and the solution proposed by support.

Please keep us posted on the progress.

We look forward to hearing a good news from you!
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-09-01T10:47:46.2666667+00:00

@jihad majed Any progress on this?
jihad majed 500 Reputation points

2023-09-04T10:47:39.46+00:00

Yes, I have upgraded to a new version of the OS, and the MARS agent is done and works normally, providing that the problem was internal to the operating system.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-09-04T14:11:13.08+00:00

@jihad majed Thanks for the update!

1 answer

Your answer

SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-16T13:17:32.3933333+00:00

@jihad majed Thank you for reaching out to us with your concern.

If you're seeing the error message "Microsoft Azure Recovery Services Agent was unable to initialize a backup storage location due to unresponsive VDS service" during a backup operation, it means that the Volume Shadow Copy Service (VSS) on the source server is not responding.

Here are some troubleshooting steps you can try:

Restart the VSS service on the source server. You can do this by opening the Services console on the source server, locating the "Volume Shadow Copy" service, and restarting it.

Check the status of the VSS writers on the source server. You can do this by opening a command prompt on the source server and running the command "vssadmin list writers". This will show you the status of all VSS writers on the server. If any writers are in a failed state, you may need to troubleshoot them individually.

Check the event logs on the source server for any VSS-related errors. Look for any errors or warnings related to VSS in the Application or System event logs.

Ensure that the source server meets the system requirements for Azure Backup. Check the Azure Backup documentation for the system requirements for the version of the agent you're using.

Ensure that the latest version of the Azure Recovery Services agent is installed on the source server. You can download the latest version from the Azure portal.

Let us know if that helps!
jihad majed 500 Reputation points

2023-08-17T06:56:38.8533333+00:00

Now we find this error:

The current operation failed due to an internal service error "Invalid input error". Please retry the operation after some time.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-17T07:46:07.4266667+00:00

@jihad majed Can you check CBEngine logs from C:\program files\Microsoft Azure Recovery Services Agent\Temp and see if there are any errors that helps you find the cause of the issue?

If possible, please share the logs with us.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-18T10:59:30.5266667+00:00

@jihad majed Did you find any errors? If possible, share the logs with us via email. Send us an email at AzCommunity @ Microsoft dot com with subject: Attn: Sadiqh Ahmed and a link to this forum thread for context.
jihad majed 500 Reputation points

2023-08-21T05:48:12.9366667+00:00

yes i sent
jihad majed 500 Reputation points

2023-08-21T06:48:36.71+00:00

could you please a tools fo read error file ?
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-21T10:19:28.3533333+00:00

@jihad majed I did not receive any email from you. Could you please send it once again?
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-24T06:37:01.2033333+00:00

@jihad majed Thanks for sending the logs. I reviewed it and couldn't find any specific errors that guides us to the problem or to drive resolution. I suggest reaching out to Azure technical support team to investigate this further.

Let us know if there are any chanllenges contacting Azure technical support team.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-28T06:22:34.92+00:00

@jihad majed Did you get a chance to contact Azure technical support team?
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-29T08:56:23.2+00:00

@jihad majed We haven't heard back from you. Please provide an update on any progress on the issue.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-08-30T14:12:26.1633333+00:00

@jihad majed Thanks for sharing the summary of the issue and the solution proposed by support.

Please keep us posted on the progress.

We look forward to hearing a good news from you!
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-09-01T10:47:46.2666667+00:00

@jihad majed Any progress on this?
jihad majed 500 Reputation points

2023-09-04T10:47:39.46+00:00

Yes, I have upgraded to a new version of the OS, and the MARS agent is done and works normally, providing that the problem was internal to the operating system.
SadiqhAhmed-MSFT 49,331 Reputation points Microsoft Employee Moderator

2023-09-04T14:11:13.08+00:00

@jihad majed Thanks for the update!

Answer 1

As discussed, we were facing difficulties that impacted the performance and functionality of our system. To address these concerns, I reached out to Azure Support to investigate the matter thoroughly. After a comprehensive review and diagnostics, it has been determined that the root cause of the problems lay in a combination of factors.

Windows 2008 R2 Update: It was identified that the underlying issue stemmed from an outdated version of Windows Server 2008 R2. The system had not received the necessary updates, which led to compatibility issues with certain components and services.

Internal Problems: Additionally, internal issues within our system configuration were contributing to the instability and performance degradation.

Solution: To rectify the situation and ensure the optimal functioning of our system, Azure Support recommended the following steps:

Windows Updates: Upgrading the Windows Server 2008 R2 to the latest version is paramount. This will address the compatibility issues and provide enhanced security and stability.

Internal Configuration Review: We will conduct a thorough internal review of our system configuration to identify and address any further underlying issues contributing to the performance degradation.

Action Plan: We have already initiated the process of updating Windows Server 2008 R2 to the latest version. Our team will work closely with Azure Support to ensure a seamless and successful update process. Additionally, we will undertake the internal configuration review to identify and address any other potential areas of concern.

Share via

Microsoft Azure Recovery Services Agent was unable to initialize a backup storage location due to unresponsive VDS service.

1 answer

Your answer