Você está na página 1de 3

OnCommand Unified Manager Core (DataFabric

Manager)
The DataFabric Manager server provides infrastructure services such as
discovery, monitoring, role-based access control (RBAC), auditing, and logging for
products in the NetApp Storage and Data suites. The DataFabric Manager Server
software runs on a separate server and is managed through the Operations
Manager console, the Web-based user interface of the DataFabric Manager
server.
To use the DataFabric Manager server, you must enable the OnCommand Core
Package license (DataFabric Manager License/Operation manager license) by
using the license key.

NetApp Management Console


NetApp Management Console (NMC) enables storage, application, and server
administrators to perform management tasks such as data backup protection, space
management, resource provisioning, data migration, and performance tuning using
Performance Adviser, Protection Manager and Provisioning Manager.
NetApp Management Console (NMC) is a Java application that can be downloaded
from the Setup menu of the Operations Manager GUI.
NetApp Management Console runs on a Windows or Linux system separate from
the server on which the DataFabric Manager server is installed.

NetApp Management Console provides a rich graphical user interface (GUI) for
Performance Advisor, Protection Manager, and Provisioning Manager.
Performance Advisor is licensed as part of Operations Manager. No separate
license is required.
Provisioning Manager is a separate license that is added to the DataFabric
Manager server.
Protection Manager is a separate license that is added to the DataFabric Manager
server.

HA (High Availability) Metro cluster


Explaining HA
In a High Availability solution two storage system (nodes) controllers are directly
connected to each other or through FC switches. In a situation where one storage
system (controller) goes down other controller can take over its partner storage to
provide continued data service.
In a HA solution, storage controllers are connected with a HA interconnect. Each
node continuously monitors its partner and mirroring the data of its partners
NVRAM (Synchronous Snapmirror). In case of a node failure, the partner node
takeover to its storage and serves the data. This is called takeover process.
Once the failed node is repaired and functioning again, the takeover node giveback
the storage to the partner. This is called giveback process.
Benefits of HA Configuration:1- Fault Tolerance: When one node fails or becomes impaired, a takeover
occurs and the partner node continues to serve the data of the failed node.
2- Non-Disruptive Software Upgrades: When you halt one node and allow
takeover, the partner node continues to serve data for the halted node,
allowing you to upgrade the halted node.
3- Non-Disruptive Hardware Maintenance: When you halt one node and
allow takeover, the partner node continues to serve data for the halted node,
allowing you to replace or repair hardware on the halted node.

HA MetroCluster
MetroCluster configurations provide data mirroring and the additional ability to
initiate a failover if a building or entire site becomes lost or unavailable.
The MetroCluster configuration is of two types

1- Stretch MetroCluster configuration: protects against local issues, such


as loss of power in a building. A Stretched MetroCluster can have two
nodes within 500 meters of each other.
2- Fabric-attached MetroCluster configuration: protects against loss of
an entire site. A Fabric-attached MetroCluster which can be greater
than 500 meters and less than 160 kms.
The MetroCluster configuration uses SyncMirror to build a system that can
continue to serve data even after complete loss of one of the sites.

Configuring High Availability:

1- License controller failover on both systems:


system> license add xxxxxx
system2> license add xxxxxx
2- Reboot both systems:
system> reboot
system2> reboot
3- Enable the service on one of the two systems:
system> cf enable
4- Check the status on that system:
system> cf status
Other Commands:
system> cf takeover
system> cf giveback
system(takeover)> partner

Você também pode gostar