Actual path might be longer, but 350m is a short distance, multiple ISL link should be OK.
about downtime.
You usualy define 2 fabric, in each fabric you proceed with zoning (that is which host are allowed to see each other).
from host to disk relation you define at least two path (wvmware,unix or windows), actual SAN traffic can be round-robin or least traffic.
If a path is dead (due to link failure (rare), gbic failure (less rare) or switch update (twice a year)), packet will be resent on other fabric/other path.
tape drive are connected only on one port, backup software is responsible for retrying.
merging
Ideally you have config_A1/config_A2 on DC-A, and config_B1/config_B2 on DC-B.
when merging config_X1 there will be a downtime either in config_A1 or config_B1 or both, but you traffic should continue on both config_A2 and config_B2.