HPE Simplivity Veeam Backup best practice

Hello  @Moustafa_Hindawi,

You can find the simplivity + veeam best practices here : Livre blanc technique : Veeam Backup & Replication sur HPE SimpliVity 380

Use NBD and you will avoid lot of issue :)

nbd is the way with simplivity. Check the link below if you want to increase performance as well.

v11: NBD multi-threading for VMware backup | Veeam Community Resource Hub

Hello @coolsport00 , @BertrandFR @YParis 

Thank you so much for your response and support!

No worries at all @Moustafa_Hindawi 

Hope it helped.

All replies are the best answer, however, I have to choose only one :(

Hi all, for anyone stumbling on this topic in the future. I contacted HPE support to view their latest stance on it and their feedback was as follows:

 

That issue was resolved in the VMware ESXi 8.0 Update 2b release. If Simplivity Hosts already use such ESXi 8.0U2b or above then you can set network transport mode as Virtual Appliance (HotAdd).

Workaround if Simplivity Hosts use previous ESXi versions:
-Use hot-add mode but with a appliance on every single host (including compute nodes) . For details, see Workaround 1: Force Veeam Backup & Replication to use the Hotadd Proxy on the same host as the VM   https://www.veeam.com/kb1681
-Configure a Veeam Proxy VM in the same ESXi host where the VMs to be protected are executed.
-Set the reg key: 
Key Location: HKLM\Software\Veeam\Veeam Backup and Replication\
Value Name: EnableSameHostHotaddMode
Value Type: DWORD (32-Bit) Value
Value Data: 
* value = 1  ' Tries hot-add if there is an ESXi with a VM-based proxy, 
if not available fails-over to a different proxy, and use the available transport mode. Which may cause stun
             * value = 2  ' (preferrable) Tries hot-add if there is an ESXi with a VM-based proxy, if not available fails-over to NBD.