Dell Cyber Recovery Manager

Introduction

Dell EMC PowerProtect Cyber Recovery focuses on the protection and recovery pillars that are referenced in many well-known cybersecurity frameworks. This solution is a combination of professional services and technology that provides the following key elements:

Planning and design
Isolation and replication
Vault analytics
Recovery

The Cyber Recovery solution provides management tools and the technology that performs the actual data recovery. It automates the creation of the restore points that are used for recovery or security analytics. Dell Implementation Services provide Cyber Recovery vault design and implementation. Dell Advisory Services can design an effective recovery strategy. Organizations can dramatically reduce their surface of attack from inside and outside threats by removing the cyber attack recovery environment from the production network. The only required connection is a data path for periodically synchronizing the data, which is brought online only for data synchronization. This logical air gap provides another layer of defense by reducing the surface of attack. The Cyber Recovery software automates the recovery procedure for the NetWorker and PowerProtect Data Manager applications.

OpsRamp integrates with Cyber Recovery Manager through REST APIs.

Prerequisites

OpsRamp Classic Gateway 10.0 and above.
Ensure that “adapter integrations” add-on is enabled in client configuration. Once enabled you can see Dell Cyber Recovery Manager integration under Setup » Integrations » Adapter section

Install the integration

From All Clients, select a client.
Go to Setup > Integrations > Integrations.
From Available Integrations, select Adapter > Dell Cyber Recovery Manager. The Install Dell Cyber Recovery Manager Integration popup appears.
Note: Ensure that Adapter addon is enabled at client and partner levels.

Enter the following information:
a. Name: Name of the integration
b. Upload Logo: Optional logo for the integration.
c. GateWay Profiles: Select a gateway management profile to associate with the client.
Click Install. The Integration page displays the installed integration.

Configure the integration

In CONFIGURATION section, click + Add.
On Create Adapter Configuration, enter:
- Name: Configuration name.
- Protocol: Protocol. Example: HTTPS, HTTP, etc.
- IP Address: IP address of the target.
- Notification Alerts: Select TRUE or FALSE.
  Notes:
  - By default False is selected.
  - If you select TRUE, application will handle Critical/Recovery failure alert notifications for Connectivity, Authentication Exceptions.
- Events Polling: Select the appropriate option. If you select TRUE, events polling is done.
- Alert Configuration: Configure the alert filters, alert severity mappings, etc. based on your requirements.
Default configuration:
```
    {"alertFilters": {"alertSeverity": ["Critical","Warning"]},"alertSeverityMapping": {"Critical": "Critical","Warning": "Warning"}}
    
```
In the Credentials section, select Custom and enter the Username and Password.
In the Resource Types & Metrics section, select the metrics you want and configure for availability and alert conditions.
In the Discovery Schedule section, select Recurrence Pattern to add one of the following patterns:
- Minutes
- Hourly
- Daily
- Weekly
- Monthly
In the Monitoring Schedule section, configure how frequently the monitoring action should trigger.

Click Save.

The configuration is saved and displayed on the page.

After saving the integration, the Dell PowerProtect Cyber Recovery Manager resources are discovered and monitoring is enabled as specified by the configuration profile.

You can perform the actions manually, like Discovery, Monitoring or even Disable the configuration.

The discovered resources are displayed in the Infrastructure page under Server, with Native Resource Type as Dell CyberRecovery Manager.

Dell CyberRecovery Manager Jobs (Native Resource Type) is displayed under Components:

View resource metrics

To confirm Dell CyberRecovery Manager monitoring, review the following:

Metric graphs: A graph is plotted for each metric that is enabled in the configuration.
Alerts: Alerts are generated for metrics that are configured as defined for integration.

Hierarchy of Dell CyberRecovery Manager resources:

Dell CyberRecovery Manager
— Dell CyberRecovery Manager Jobs

Supported metrics

Metric Name	Metric Display Name	Units	Description
dell_cyber_recovery_manager_Status	Dell Cyber Recovery Manager Status		Gives the Dell Cyber Recovery Manager Status. Possible values: Running(1),Others(0).
dell_cyber_recovery_manager_vault_Status	Dell Cyber Recovery Manager Vault Status		Gives the Dell Cyber Recovery Manager Vault Status. Possible values: Locked(0),Unlocked(1).
dell_cyber_recovery_manager_job_Statu	Dell Cyber Recovery Manager Job Status		Gives the latest status of Dell Cyber Recovery Manager Jobs. Possible values: Canceled(0),Running(1),Warning(2),Critical(3),Success(4).
dell_cyber_recovery_manager_job_Progress	Dell Cyber Recovery Manager Job Progress	%	Gives the progress of Dell Cyber Recovery Manager Jobs
dell_cyber_recovery_manager_job_ElapsedTime	Dell Cyber Recovery Manager Job Elapsed Time	m	Gives the elapsed time of Dell Cyber Recovery Manager Jobs

Risks, Limitations & Assumptions

Application can handle Critical/Recovery failure alert notifications for the below two cases when user enables Notification Alerts in configuration:
- Connectivity Exception
- Authentication Exception
The metric can be used to monitor CyberRecovery Manager resources and can generate alerts based on the threshold values.
Application cannot control monitoring pause/resume actions based on the above alerts.
Component level threshold configuration is not possible.
Resource level metric threshold customization and frequency setting are not possible.
Usability issues in application configuration page while adding/editing.
Optional configuration parameters cannot be defined.
Application upgrade is manual process without version change.
The availability is shown unknown for few resources even if it is enabled on the respective resource metrics. This is because of the presence of multiple native type resources under the same resource type.