Skip to main content

In this KB https://www.veeam.com/kb4027 The Huawei Plug-In for Veeam Backup & Replication reached End-of-Life on 2022-04-22 and is no longer available. VBR cannot call Huawei storage with it’s API to complete the backup job with storage’s snapshots.

 

https://helpcenter.veeam.com/docs/backup/vsphere/system_requirements.html?ver=110

In user guide of VBR v11, Veeam Backup & Replication does not offer integration with Huawei storage.

 

According to the above, Veeam VBR cannot support any backup integration with Huawei storage. If the environment only includes VMware ESXi 7 and Huawei storage, what is recommended backup mode can be selected in VBR v11?

How are you connected to the Huawei storage from your hosts?


How are you connected to the Huawei storage from your hosts?

Yes. All ESXi hosts are connected to Hauwei storage by FC Channel.


If you have physical proxies, then fastest option would be to also connect them via FC and then use Direct Storage Access (Direct SAN). It just wouldn’t be able to use storage snapshots.


Even though the Huawei storage integration is no longer available you can still backup VM data from that array through Direct SAN access, hotadd (virtual appliance mode) and NBD (network) mode.  
 


Even though the Huawei storage integration is no longer available you can still backup VM data from that array through Direct SAN access, hotadd (virtual appliance mode) and NBD (network) mode.  
 

I would recommend the same modes in that order.  Direct would be best if you can swing it.


If you have physical proxies, then fastest option would be to also connect them via FC and then use Direct Storage Access (Direct SAN). It just wouldn’t be able to use storage snapshots.

I also prefer this option. Thanks for your recommendation. @haslund 


Non Huawei-specific, but definitely recommend direct storage access before going back to using proxy’s, or network mode.  I haven’t performed any backups from storage snapshots, but I’ve had really great success with direct storage access.


FYI: even though it’s EOL, the Huawei plugin together with Veeam V11 still works.


FYI: even though it’s EOL, the Huawei plugin together with Veeam V11 still works.

@B. ten Velden Please not that the Huawei Plugin is not available on next version (Veeam v12).


Is there any progress on this matter?

Veeam 11 is getting close to EOS...


Is there any progress on this matter?

Veeam 11 is getting close to EOS...

there wont be any update on this, seeing that the plugin is EoL. And don’t expect to get a new plugin, seeing Huawei is Chinese and Veeam is American…
 

I would advise you to get in contact with either Huawei or get support by a Veeam partner to help you on changing your environment to make it work with v12.


Is there any progress on this matter?

Veeam 11 is getting close to EOS...

there wont be any update on this, seeing that the plugin is EoL. And don’t expect to get a new plugin, seeing Huawei is Chinese and Veeam is American…
 

I would advise you to get in contact with either Huawei or get support by a Veeam partner to help you

on changing your environment to make it work with v12.

 

hmm - I think Lenovo ist Chinese as well - and is promoted and integrated by Veeam...

 


I contacted Huawei regarding this issue, and they informed me that Veeam stopped supporting the plugin from their side, stating it was not Huawei's decision. Huawei mentioned they are open to addressing any requirements from Veeam in this matter.

However, I read the opposite on the Veeam R&D forum, as shown in the quote below:

 

Hello David,
thanks for the request. The statements made above are all that we can share from the R&D side here.

As the code is owned by Huawei and we do not have a contractual base anymore, we can not distribute the Huawei owned plug-in anymore. Please contact Huawei.
 

https://forums.veeam.com/veeam-backup-replication-f2/huawei-plugin-eol-t80446.html#p451689

 

We need to clarify this situation. If it is possible to reinstate support and both sides are open to it, we can facilitate their communication.

 

Thanks


You will need to work through the forum post and product management.  Not as much visibility here on the community.


Comment