Introduction to Rubrik
Rubrik simplifies backup and recovery for hybrid cloud environments. By combining data orchestration, catalog management, and deduplicated storage into a singular software platform, it removes the complexity of legacy backup systems. Enterprises can use Rubrik’s API-first software tool to automate automation and unlock cloud for long-term data retention or disaster recovery. Rubrik supports the top operating systems, databases, hypervisors, clouds, and SaaS apps and was made to be vendor-neutral.
Rubrik assists organizations in maintaining data integrity, provides data availability that withstands challenging circumstances, constantly tracks data risks and threats, and restores businesses with their data when infrastructure is attacked.
The following helps you to get started.
- To explore monitored metrics, see Supported Metrics and Default Monitoring Configuration.
- To verify prerequisites and configure, see Working with Rubrik.
Key Use cases
Discovery Use cases
- It discovers the Rubrik Cluster components.
- Publishes relationships between resources to have a topological view and ease of maintenance.
Monitoring Use cases
- Provides metrics related to job scheduling time and status.
- Generates alerts for each metric and notifies administrators about the issue with the resource.
- For detailed strcuture, see Resource Hierarchy.
Supported Target Versions
Rubrik cluster software version: 8.0.2-p2-22662
Resource Hierarchy
- Rubrik Cluster
- Rubrik Node
- Rubrik Disk
- Rubrik Node
Version History
| Application Version | Bug fixes / Enhancements |
|---|---|
| 2.2.0 | This implementation introduces third-party CI alert mapping and OpsQL-based enhancements. Configure alert mappings to target CI systems through the application configuration. After configuration, the system automatically forwards alerts to the corresponding third-party platforms and maps them to the specified CIs, ensuring consistent integration and efficient alert management.Previously, resource filters in the app configuration required manual entry of resource core and custom attributes. With this enhancement, the configuration is moved to OpsQL-based filtering, where users can see the keys auto-populated as needed. |
| 2.1.1 | Fixed Auth Token issue for getLatest snapshot scenario. |
| 2.1.0 | Added support for token-based authentication. |
| 2.0.6 | Added support for all critical and warning severity alerts and then added support for event type filtering. |
| 2.0.5 | Provided fix for Get Latest Metrics, Activity Logger and DebugHandler Changes. |
| 2.0.4 | Added support to perform discovery and monitoring using the other available nodes if the primary node is unable to make API calls. |
| 2.0.2 | Added support for NativeType Display order changes and resource grouping by type in UI |
| 2.0.3 | Bug Fix for metrics intermittent issue |
| 2.0.1 |
|