High availability has to be provided by all components of a storage configuration: StorMan server, StorMan client and SMI-S providers.
StorMan server
The StorMan server is designed as a single server and can therefore be considered as a single point of failure for Storage Management.
High availability is provided in the following way:
The StorMan server is automatically restarted on the same server in case of failure.
A second redundant StorMan server can be set up to take over requests from the StorMan clients.
To support integration (e.g. into SE Manager on SE Servers) StorMan provides functions to start and stop the StorMan server and a check function to check the status of the StorMan server (e.g. via SE Manager or service CLI on M2000).
For SE Server the Management Cluster is supported as StorMan is installed and running on each Management Unit.
For BS2000 configurations with SHC-OSD multiple StorMan servers can be configured to support an automatic failover of StorMan servers.
In the WebUI from M2000 version V6.5SP1:
StorMan offers the possibility to synchronize its configuration with that of another StorMan in the MU cluster under Configuration -> StorMan -> Settings -> Synchronize Repository.
All configuration wizards, offer the possibility to select other MUs which should take over the configuration.
StorMan Client
The StorMan client can be installed on multiple MUs (same as the server).
In the other hand the client can switch to a redundant StorMan server in the LAN (e.g. in case of BS2000 configurations with SHC-OSD).
SMI-S Provider
Embedded SMI-S providers (e.g. ETERNUS DX/AF storage arrays) run directly on the storage array and are therefore available as long as the storage array.