Description of problem: In order to allow storage replication for disaster recovery purposes, need to have an option to store a backup storage connection for each storage domain in the DR data center. Currently, the existing functionality is the manage storage connection feature that allows replacing the storage domain's storage connection. We need this secondary connection to be stored as a backup one and in a case of a disaster, the storage domain's storage connection will be replaced immediately with a minimum manual intervention.
Do you think it really needed? In active-active, this would mean downtime during the reconnect. In active-passive, the tool can handle the mapping. Shouldn't we rely on multipathing or DNS name change?
In active-active we'll probably have to rely on storage relication. So at the moment, this is not needed.
* Storage replication with some kind of a floating address the storage exposes, hiding the 'real' addresses to both sites.
Closing until we know if this is needed