Oncommand Unified Manager 5.x
This article describes the procedure to be followed to monitor existing Data Protection relationships without importing them fully into Protection Manager.
Following are the two reasons for the users not to import the relationship into Protection Manager:
- To buy-in to policy-based management, you have to create the managementconstructs within Protection Manager (Datasets, Protection Policies and ResourcePools). These powerful concepts allow users to abstract the complexity of theindividual relationships into higher-level service related containers, which allowmultiple objects to be managed much more easily. Some users do not want toadd this layer of abstraction in order to manage a handful of relationships, gothrough the change management or process of importing the relationships. Userswant to know the existing lag times and be alerted if the times exceed beyond anacceptable level.
- Once imported into Protection Manager, the Data Fabric Manager (DFM) server(and not the storage controller) is responsible for scheduling the relationships.When managing data protection relationships through Protection Manager, it isstrongly recommended that the DFM Server is made highly available and this isnot always the case in every environment.