- Posts: 26
- Liked: 1 time
- Joined: Jul 24, 2019 10:04 am
So I noticed that I could manually choose the datastores it should/can connect to, but in that list, it only shows the local VMFS datastores of the spare space on the ESXi boot drives of the vSAN cluster. the vSAN datastore is not visible. However it is/was visible when creating the replication job and was selected as the destination and replicas are being created and updated correctly (albeit slowly).
- Posts: 897
- Liked: 242 times
- Joined: Jun 28, 2016 12:12 pm
When you talk about selecting volumes, you mean step 5 here, correct? https://helpcenter.veeam.com/docs/backu ... ml?ver=110
That's just for DirectSAN and DirectNFS connections, it won't influence hotadd.
For your issue, just to confirm, the proxy itself has all its disks on the same vSAN, correct?
https://helpcenter.veeam.com/docs/backu ... ml?ver=110
If this is indeed the case, it bears raising a support case just so we can confirm why the proxy was not eligible for hotadd transport mode.
Be sure to include logs as per https://veeam.com/kb1832 and use the 1st option and select one of the jobs where you saw this behavior; it should be enough to start with (though depending on the situation, more information might be needed)
- Posts: 242
- Liked: 57 times
- Joined: Apr 28, 2009 8:33 am
- Location: Strasbourg, FRANCE
Users browsing this forum: No registered users and 13 guests