Error when setting up ASR for the first time

I'm setting up my first Azure ASR configuration and I'm getting the following error when I try to apply the policy that I cannot sort out.  Looking for some direction in solving this.


ERROR ID10003
ERROR MESSAGEProtection couldn't be configured for cloud/site EGMHypVsite.
PROVIDER ERRORProvider error code: 31389

Provider error message:
      Job 'Getting Virtual Disk Information' (EBC8738D-3E57-411E-B500-06A6C779B532) failed. Job State 10. Error Code: 32779. ErrorSummaryDescription: . ErrorDescription: .

Provider error possible causes:
      Check the error details.

Provider error recommended action:
      Resolve the issue and try again.
POSSIBLE CAUSESOne or more hosts couldn't be prepared. Check the Provider error for more information.
RECOMMENDATIONResolve the issue and retry the operation.
jterharkIT ConsultantAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

 
Binu B KCloud/Azure Infrastructure ConsultantCommented:
Can you give us a little bit more details? What type of Azure site Recovery are you confiuring? is it azure to azure or Hyper-v to azure or vmware to azure

I would follow the doc https://docs.microsoft.com/en-us/azure/site-recovery/
If you are doing that how far are you reached and where are you failing?

Regards
binu
0

Experts Exchange Solution brought to you by ConnectWise

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
 
jterharkIT ConsultantAuthor Commented:
I determined that the problem was left over files from a vm that had been deleted from the cluster manager.  Once the files were deleted, the problem went away.
0
 
Binu B KCloud/Azure Infrastructure ConsultantCommented:
This is resolved by the submitter
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.