Since 3Par PP is using native T10 ALUA specification, everything works out of the box.
In the Veeam Backup Server, you just need to connect the two 3Par arrays in the SAN management pane.
In a normal situation, each LUN has 8 path, 4 active I/O and 4 standby.
On both arrays, each replicated LUN has the same WWN and is exported with the same lun number.
Path Policy is set to RoundRobin on each host (VMware or Windows).
When backup starts, Veeam Backup finds the active array by looking which target is holding the active path. At least, it is what we understood when analyzing the behavior.
After a failover, active paths are switched to the secondary array. Veeam connects to the array looking at the target holding the active path, here again this is our understanding of the process and in our case it all went well.
We didn't try to do a switchover during backups. If using storage snapshot it would certainly fail since the storage snapshot only exists in one array. If using standard direct SAN without storage snapshot integration, it would be transparent and follow the path switchover.
Hopefully, there is now the option to fallback to normal mode if storage snapshot isn't working.
Users browsing this forum: No registered users and 1 guest