iSCSI support for HP 3PAR storage

[ACC]

The direct-san backup is a verification that Veeam has access to the volumes on the SAN.

[tsimons_dti]

All-
We just stood up a new 3par to replace our old storage, we used 10gige iSCSI

I noticed that the 3par has FC ports on the back as well. If I get FC HBA's for my veeam/backup server, can I do a direct connect for SAN level backups?

~Todd

[emachabert]

technicaly, on the 3par side, there is no problem to have a direct attached FC host with access to the volumes that are already exported via iscsi, if you respect the compatibility matrix for the hba model and firmware version (check the HP spock website for this).

But, on the veeam side, I think you cannot do this. I think we already had a discussion about this kind of setup and at that moment you couldn't have a mixed access protocol setup. If the production volumes are exported via iscsi, veeam will also need to have an iscsi connection for the direct SAN access.

I'm not sure if this limitation is still here in v8 or v9, the guys in green will have the answer !!

[foggy]

We've done a quick test on one of the storages in our lab, LUNs were presented to hosts via iSCSI and we were able to do direct SAN to them via FC with no issues. The same LUN ID is used in both cases, regardless of the protocol.

[emachabert]

That is a good news, very good news

[tsimons_dti]

We've done a quick test on one of the storages in our lab, LUNs were presented to hosts via iSCSI and we were able to do direct SAN to them via FC with no issues. The same LUN ID is used in both cases, regardless of the protocol.

What version of veeam?

Thanks!

[foggy]

Tests were done on v9, however nothing has changed here comparing to v8, since this works on a SAN level: Veeam B&R takes the ID of the LUN containing the datastore where VM disks reside and looks for the disk with the same ID presented to the proxy server.