Microsoft Server 2012 Migration to Azure Issues

Question

Microsoft Server 2012 Migration to Azure Issues

Serverguy_404 0

I'm trying to migrate a few servers to Azure that are running Windows Server 2012. I've installed the appliances and discovered all of my assets just fine. However, I'm getting the below error on 3 of my machines.

Error ID

78143

Error Message No crash consistent recovery point available for the VM in the last 60 minutes. I noticed that I can't reach this Azure Fabric IP on the problematic machines. (Wireserver 168.63.129.16) I can't reach this IP from my own network let alone the server network and there is nothing in place that would be stopping this from happening so I'm thinking this could be the issue, but I could be wrong. Upgrading the servers is out of the question. What could be going wrong?

I've followed all of the troubleshooting steps below and I can't seem to figure out the issue.

Possible causes

Replication is delayed due to network connectivity issues or low bandwidth availability. Upgrade to 9.28 or above to get network latency related errors.
Process Server is not able to achieve the required bandwidth. Check Process Server related alerts. Upgrade to 9.27 or above to get PS related errors.
The data change rate (write bytes/sec) for one or more disks of the source machine has exceeded ASR supported limits. Refer https://aka.ms/asr-v2a-target-limits.

Recommendation
1. Network connectivity exists between the source machine and the process server, between the source machine and the Configuration Server and also between the Process Server and Azure storage account.
2. There is sufficient network bandwidth available between the protected machine and the process server, and the process server and Azure. 3. Ensure that the target storage type (Standard or Premium) is provisioned as per the churn rate requirement at source.
3. Look for any associated events in the ASR events table and also any errors on the Site Recovery vault overview blade, and resolve them if any
4. If the issue persists contact support.

Serverguy_404 0 Reputation points

2025-03-18T13:34:18.75+00:00

So I'm still troubleshooting this issue and there is nothing configured within any appliance in my environment that would be blocking access to this IP. However, I've upgraded my MARS agent on my process server and I'm unable to upload my configuration files from my vault. I even changed vaults and I'm getting the same error:

08:45:23:SettingFileException object Status - CorruptFile

08:45:23:Return value override already set to 'CorruptVaultCreds', hence not overriding with 'CorruptVaultCreds'.

08:45:23:The vault credentials currently used for registration isn’t supported anymore. Download new vault credentials from the Azure Site Recovery portal and retry the operation. If you are using PowerShell, please upgrade to the latest version (https://aka.ms/latestpowershell), download new vault credentials and retry the operation.

Re-registering my vault via the Configuration manager doesn't work either. I've thrown my hands up at this point. It can't be my vault credentials because everything is updated, and the credentials are fresh. Don't know if this is what's causing my replication issues or the IP address issue.

HELP!

1 answer

Your answer

Serverguy_404 0 Reputation points

2025-03-18T13:34:18.75+00:00

So I'm still troubleshooting this issue and there is nothing configured within any appliance in my environment that would be blocking access to this IP. However, I've upgraded my MARS agent on my process server and I'm unable to upload my configuration files from my vault. I even changed vaults and I'm getting the same error:

08:45:23:SettingFileException object Status - CorruptFile

08:45:23:Return value override already set to 'CorruptVaultCreds', hence not overriding with 'CorruptVaultCreds'.

08:45:23:The vault credentials currently used for registration isn’t supported anymore. Download new vault credentials from the Azure Site Recovery portal and retry the operation. If you are using PowerShell, please upgrade to the latest version (https://aka.ms/latestpowershell), download new vault credentials and retry the operation.

Re-registering my vault via the Configuration manager doesn't work either. I've thrown my hands up at this point. It can't be my vault credentials because everything is updated, and the credentials are fresh. Don't know if this is what's causing my replication issues or the IP address issue.

HELP!

Answer 1

Molly Lu-MSFT 2,586 Microsoft External Staff

Hello,

Thank you for posting in Microsoft Q&A.

Based on the description, I understand your question is related to Azure.

Check that your firewall is not blocking outbound traffic to the IP address 168.63.129.16 on ports 80 and 32526. This IP address is used by the Azure platform for various operations, including VM Agent communication.

Check your Network Security Groups (NSGs) are not blocking traffic to 168.63.129.16. NSGs should allow outbound traffic to this IP address.

If your network uses a proxy, make sure that the proxy settings are correctly configured to allow traffic to 168.63.129.16.

Check if Azure VM Agent is installed and running on your VMs. The VM Agent is necessary for communication with the Azure platform.

Test the network connectivity from your VMs to the Azure Fabric IP. You can run ping command to check if the IP is reachable.

Have a nice day.

Best Regards,

Molly

============================================

If the Answer is helpful, please click "Accept Answer" and upvote it

Serverguy_404 0 Reputation points

2025-03-18T12:41:42.79+00:00

Hello,

So the agent's on my vm's have been upgraded and are working just fine. There is no firewall or any other appliance with any rules set that would block communication to this ip address. Also, I can't even ping this IP address from a separate network with no firewall rules so I'm not sure what's going on.
Molly Lu-MSFT 2,586 Reputation points Microsoft External Staff

2025-03-24T09:25:53.0266667+00:00

It is recommended to report this issue to Microsoft, use the Feedback Hub app. To learn more, see Send feedback to Microsoft with the Feedback Hub app:

https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332

Share via

Microsoft Server 2012 Migration to Azure Issues

1 answer

Your answer