Initial replication from on-premises to Azure failed with error 78024

VJ-8370 446

Hi,

Initial replication from on-premises (VMware) to Azure failed with the error 78024 and required resynchronization.

The size of the disks on the VM are approximately 1TB and the initial replication has almost completed 85% and then it failed with this error.

Resynchronization button is not enabled and I tried restarting the "InMage Scout VX Agent - Sentinel/Outpost" service as well on the on-premises VM.

Is there a way where I can initiate replication so that it starts from where it left off?

Regards,
VJ

SadiqhAhmed-MSFT 45,181 Reputation points Microsoft Employee

2021-02-09T15:00:11.283+00:00

Hello @VJ-8370
Ensure that there are no connectivity, bandwidth or time sync related issues.
Ensure no anti-virus software is blocking Azure Site Recovery. Learn more on folder exclusions required for Azure Site Recovery.

----------------------------------------------------------------------------------------------------------------------

If the response helped, do "Accept Answer" and up-vote it
VJ-8370 446 Reputation points

2021-02-09T15:05:29.197+00:00

Hi Sadiq,

I have checked on the server and the Azure Site Recovery folder is excluded from it. (If it is blocked, it would not have synced 85% of the disks). Also, other VMs are getting replicated without any issue.

Is there a way where we can perform resync during initial replication, rather than disable the entire replication and then reinitiating it?

Regards,
VJ
SadiqhAhmed-MSFT 45,181 Reputation points Microsoft Employee

2021-02-11T07:20:20.697+00:00

@VJ-8370 Resynchronization will be automatically triggered during initial replication, if required. Manual step would not be required.
VJ-8370 446 Reputation points

2021-02-11T17:56:11.297+00:00

Hi Sadiq,

It did not trigger automatically. I waited for entire one day and eventually had to disable the replication and reenable the protection.

Would really appreciate if you can share any workaround so that any such instances/situations can be taken care of in future.

We have many more servers lined up which are in TBs. Kindly share your inputs.

Regards,
VJ
SadiqhAhmed-MSFT 45,181 Reputation points Microsoft Employee

2021-02-15T13:58:28.07+00:00

@VJ-8370 The quicker way to resolve these issues is to loop in support team at the earliest. It won’t be possible to suggest the issue/workaround without understanding the root cause of the issue.
VJ-8370 446 Reputation points

2021-02-17T07:23:48.67+00:00

Ok Sadiq. I was checking if there is any way to resume from where it left off

One example scenario I can think of is - After initiating initial replication, when the VM is replicated 85% and at this point of time if a disk is detached at on-premises, the replication has stopped. Is there a way it can resume without that disk? (I know we select the list of disks which are to be replicated)

If the next issue occurs, I shall report to support team.

Regards,
VJ

1 answer

SadiqhAhmed-MSFT 45,181 Reputation points Microsoft Employee

2021-02-18T09:32:16.907+00:00

@VJ-8370 Removing a disk after enabling replication is not a supported scenario. So, in this situation, disabling the replication is required. In case of disk re-size or unexpected shutdown or any other interruption that can cause intermittent data loss, resynchronization will be automatically triggered by ASR.
Please sign in to rate this answer.
VJ-8370 446 Reputation points

2021-02-24T05:48:16.017+00:00

Ok Sadiq. Thank you for the details.

Regards,
VJ
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Initial replication from on-premises to Azure failed with error 78024

1 answer

Your answer