Azure Site Recovery shows not all Datastores during Failback

Question

Hello,

we have setup Azure Site Recovery on the vSphere Environment of our Company.
Failover from on-premise to Azure worked like charm.
When we tried to failback we stumbled over an issue with the datastores. We had only the option to choose the Datastores of the Host where the Master Target Server was installed. The protected VMs a spreaded over two hosts. The ASR Configuration-, Process- and Master Target Server are running on a third host.
As a workaround we had to migrate the ASR Server to the Hosts where the protected VMs supposed to be one by one to complete the failback.
vMotion is not available and shouldn't be the issue.

vSphere Architecture in a nutshell:
3x Hosts with local Storage each.

Is this intended behaviour? I wasn't able to find anything speaking against our setup e.g. only working with shared storage etc.
Would it be necessary to have an Master Target Server on each host if no shared storage is available?

Answer 1

@André Kaltenbach Apologies for the delayed response!

Failback is a controlled event that is usually planned.

If you need additional Master Target failback servers then these are usually created during the planned failback activity, likewise you currently need a separate Master Target Server for Linux Failback .

As you have local datastores, you would need 3 Master Target Servers.

This relates to how VMWare works. You can’t share local datastores otherwise they would not be local!

You need to investigate VSAN or refer to the below.

Deploy additional master target servers
In the following scenarios, more than one master target server is required:
• You want to protect a Linux-based virtual machine.
• The master target server available on the configuration server doesn't have access to the datastore of the VM.
• The total number of disks on the master target server (the number of local disks on server plus the number of disks to be protected) is greater than 60 disks.

In short, the master target server would need access to the data store where the source machine is located. You can deploy additional master target servers to facilitate the failback activity.

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

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