> For the complete documentation index, see [llms.txt](https://docs.storware.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.storware.eu/deployment/backup-destinations/filesystem/rubrik.md).

# Rubrik Managed Volumes

## Overview

With Storware supporting a wide range of sources, one can easily expand Rubrik capabilities by integrating both solutions. Storware supports file-based backup destinations with a mechanism to run custom pre/post storage access integration scripts. Rubrik, on the other hand, is able to expose Managed Volumes, which can easily be used as a snapshot-driven file system backup destination. Storware initiates backups for all supported virtualization platforms or storage providers. The file system backup destination has enabled pre/post storage access integration scripts which are executed in each storage-related activity (before and after changes are made). For each VM/storage instance, integration assumes a separate managed volume.

The pre-script locates the managed volume in Rubrik (creates it if necessary), exposes it over NFS, mounts it on the node, and invokes “begin snapshot” Rubrik API call. Then the changes are made to the volume (new data is being stored, expired data is removed according to the retention).

Finally, a post-script is invoked to unmount the volume and invoke “end snapshot” Rubrik API call. This script is also invoked in any failure of the pre-script or task activity.

Example for OpenStack using Ceph RBD storage environment:

![](https://content.gitbook.com/content/wUsKWUrceYHp8e9TJ00e/blobs/vUpenKmg6CWW7J23Fgwl/deployment_backup-destination_enterprise-backup-destination_rubrik_1.png)

## Supported features

| Supported version          | CDM 8.0, 8.1  |
| -------------------------- | ------------- |
| Syntetic backup            | Not supported |
| Random Access              | n/a           |
| Deduplication              | Not supported |
| Encryption                 | Not supported |
| Pre/post command execution | Supported     |

## Requirements

1. A working Rubrik cluster (IP floating address or FQDN)
2. Network communication between Rubrik and Storware on ports:
   * TCP 443
   * NFS v3 (TCP and UDP): 111, 2049
3. Username and password for Rubrik software, with the following permissions:
   * Create, delete, modify Managed Volumes
   * Create snapshots for Managed Volumes
   * Resize Managed Volumes
   * Change mode: Read-Only to Read-Write, and from Read-Write to Read-Only on Managed Volumes

## Setup

In the Rubrik software cluster, you need to create:

1. SLA Domains -> Local Domains: SLA with your retention settings for backup from Storware in Managed Volumes.
2. Very important: We don’t need to create any Managed Volumes on Rubrik manually – this will be created automatically by Storware, and the size of the managed volume needed for backup is dynamically growing by Storware, so at each step, we are not losing any extra space on Rubrik.

On the Storware node, you need to make the following changes:

1. Go to `/opt/vprotect/node/scripts/rubrik/scripts`
2. Edit the config file and fill variables with your own information, for example:

   ```
   R_API=https://your_rubrik floating_ip_address/api
   R_TOKEN=your_token
   #R_USER=login_for_rubrik_when_token_was_not_provided
   #R_PASS=pass_for_rubrik_when_token_was_not_provided
   #R_NFS_SUBNET=subnet_for_the_share_when_vlans_are_in_use
   R_CLIENT_ID=rubrik_client_id
   R_SLA_NAME=name_of_your_sla_domain_in_rubrik
   ```
3. Save this config file
4. Next, edit `/etc/sudoers.d/01_vprotect-node` file and ensure the following entries are present before the `Defaults!VPROTECTNODE !requiretty` line (add them if missing):

   ```
   %vprotect ALL=(root) NOPASSWD: /opt/vprotect/node/scripts/rubrik/scripts/privileged.sh
   %vprotect ALL=(root) NOPASSWD: /usr/bin/rmdir
   ```

Now we need to configure your Storware server by using a web interface. Please enter the web address: **<https://your\\_Storware\\_IP/or/FQDN\\_address>**, and log in as Global Administrator in Storware.

1. Go to **Backup Destinations** -> **File System** and click **Create**
2. Select **Rubrik Managed Volumes**
3. In the **General** tab:
   1. **Name** – provide a name for the backup destination
   2. **Default backup destination** – enable if this destination should be used by default
   3. **Description** – (optional) provide a description
   4. **Visibility for all projects / Projects** – specify project visibility or assign specific projects
4. In the **Choose Node Configurations** tab:
   1. Select the **Node Configurations** that will use this backup destination
5. In the **Rubrik Managed Volumes Settings** tab:
   1. **Backup destination path** – specify the temporary mount path where Storware Backup & Recovery mounts the Rubrik Managed Volume to store backup data (e.g. /vprotect\_data/backup)
6. In the **Pre/post access** tab:
   1. Enable **Execute pre-store command** and add the command arguments: \
      • Command arg: /opt/vprotect/node/scripts/rubrik/scripts/pre.sh \
      • Command arg: /opt/vprotect/node/scripts/rubrik/scripts/config
   2. Enable **Execute post-store command** and add the command arguments: \
      • Command arg: /opt/vprotect/node/scripts/rubrik/scripts/post.sh \
      • Command arg: /opt/vprotect/node/scripts/rubrik/scripts/config
7. Save configuration

## Limitations

Based on the number of nodes, the Rubrik cluster has the following limitations:

* Three-node configuration - protection up to 256 virtual machine instances
* Two-node configuration - protection up to 128 virtual machine instances

A single Rubrik node can protect up to 64 virtual machine instances.