Rubrik


Error

You must log in or register to view this page

Rubrik is an all-in-one data security, backup, and recovery platform that helps organizations protect and manage their data across on-premises, cloud, and hybrid environments.

Architecture

Rubrik consists of the following nodes (as shown in the diagram):

  • StorageSystemGroup node — Represents Rubrik clusters.
  • StorageSystem node — Represents Rubrik nodes.
  • DiskDrive node — Represents Disk on Rubrik nodes.

1758023245814-275.drawio.png

Important
Discovery creates a Management relationship between StorageSystem and Host if Host was scanned by using SNMP before the Rubrik API scan.

Platforms supported by the pattern

The pattern discovers Rubrik instances on Rubrik Security Cloud by using API scan.

Identification

To run a discovery of the product, the pattern must be triggered. This section describes conditions under which the pattern can be triggered.

Pattern triggers

The following table gives details about the pattern trigger:

PatternTrigger nodeAttributeConditionArgument
RubrikDiscoveredAPIProviderResultList

discovery_method

=

Rubrik.getClusterConnection

API provider discovery

Rubrik is discovered by executing REST API queries and processing the obtained data. To add a service account, see the official Rubrik API documentation.

The following figure shows how Rubrik API credentials are added in the BMC Helix Discovery UI: 

1758019052419-900.png

The following figure shows how a Rubrik API scan is set before its launch:

1758019117385-551.png

API queries

The Rubric pattern module executes API requests built by using GraphQL, with /api/graphql as the base endpoint. For details about how Rubric API requests are constructed in GraphQL, see GraphQL schema documentation.

The following is an example of the getClusterConnection request:

query { clusterConnection { nodes { id } } }

The following is an example of a structured GraphQL query designed to retrieve detailed information about cluster connections and their associated components:

query {
clusterConnection {
    nodes {
      id
      version
      name
      type
      systemStatus
      productType
      licensedProducts
      clusterDiskConnection {
        nodes {
          status
          diskType
          nodeId
          path
          usableBytes
          capacityBytes
          unallocatedBytes
          serial
          diskId
        }
      }
      replicationSources {
        sourceClusterUuid
        sourceClusterName
      }
      replicationTargets {
        targetClusterUuid
        targetClusterName
      }
      clusterNodeConnection {
          nodes {
          id
          hostname
          ipAddress
          cpuCores
          interfaceCidrs {
              cidr
              interfaceName
          }
          networkSpeed
          platformType
          ram
        }
      }
    }
  }
}

Trigger

The Rubrik pattern is triggered by DiscoveredAPIProviderResultList, where discovery_method =  "Rubrik.getClusterConnection".

Discovery view

The following image shows an example of the StorageSystemGroup node modeling:

1758023831171-602.png

The following image shows an example of the StorageSystem node modeling:

1758023973925-948.png

Subject matter expertise

Inputs from subject matter experts are welcome on any other potential approaches not discussed in this topic.

Testing

The pattern has been tested against the available customer data.

Open issues

There are no known open issues with this pattern.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Discovery content reference