Home > Storage > PowerStore > Databases and Data Analytics > Dell PowerStore Metro Node with Oracle > Metro node configurations
There are two ways to configure the metro node appliance:
Both configurations have their own set of configuration parameters that allow an administrator to customize either configuration for specific needs.
Provides a simplified way to manage storage for critical applications within the local data center. Metro node provides block level access to data between two arrays and provides active/active synchronous replication for high levels of seamless and non-disruptive data mobility. It also allows for the ability to mirror data between multiple heterogeneous or homogeneous storage arrays by providing storage fault tolerance if one array fails. Metro node uses technology that allows a single copy of data to be shared, accessed, and relocated to the same or different geographic locations. The management of storage across the arrays in a metro node Local cluster provides improved storage utilization across all arrays in the cluster. A metro node Local consists of a single metro node cluster that connects to multiple supported storage arrays using the FC data transfer protocol. In the figure below, the storage is backed by two PowerStore 500T model arrays named PS-15 and PS-16.
Provides the same functionality and simplified way to manage storage as metro node Local, but it uses a campus or metro placed data center within synchronous distances. Metro node Metro can be installed with inter-cluster links that require 5 ms or less round trip latency. With metro node Metro, both systems are mirrored, and data is fully accessible at both sites, and yields a DTO (decision time objective) of 0.
Metro node Metro is also configured with a rule set and an optional witness component. The rule set contains several different rules that govern how a Metro configuration operates if one of the metro node cluster members becomes unavailable. An optional witness mitigates the situation where a rule set instructs metro node Metro to continue I/O on a specific cluster, but that cluster is the one with the outage. Without the witness, rule sets are biased towards the cluster specified in the rule and therefore are insufficient to provide seamless zero or near-zero Recovery Time Objective (RTO) failover in the event of site disasters and metro node cluster failures. The metro witness reviews periodic information sent by the metro cluster to determine and distinguish between failures and to resume I/O automatically.
This paper covers both a metro node Local and metro node Metro configuration.
For additional information about metro node Local and metro node Metro, including further diagrams, discussions about the witness component, and traditional bias rule sets, see References.