Skip to content
English
More support Sign in
Contact us
  • There are no suggestions because the search field is empty.

How to configure Impossible Cloud as a archival location in Rubrik CDM 

This step-by-step guide shows how to configure Impossible Cloud Storage (standard and immutable) as a cloud archival destination in a Rubrik Cloud Data Management (CDM) 9.1 deployment.

In modern Rubrik environments, configuration is performed via the Rubrik Security Cloud (RSC) web interface. These settings are then pushed to the connected Rubrik CDM cluster, which executes the archival jobs and handles communication with the Impossible Cloud Storage.

Step 1: Add a new cloud archival location in Rubrik Security Cloud

  1. After you logged into the Rubrik RSC web interface, navigate to Archival & Storage and open Data Center Archival Locations.
  2. Press Create Archival Location and the guided setup will be triggered.

Step 2: Configure Impossible Cloud as a S3-compatible object storage

Follow the guided configuration and the on-screen prompts to configure Impossible Cloud as a S3-compatible archival location:

  1. Select Object Store (S3 Compatible) and press Next.
  2. Select S3 compatible object storage as object store vendor an press Next.
  3. Define a name for your new archival location (e.g. Impossible Cloud Backup Location) and select your proper Rubrik CDM cluster.
  4. If you want make your backup immutable, enable the Immutable Archive option and specify a lock period. Additionally, you need to acknowledge that you have reviewed the compatibility matrix and the immutability documentation. Rubrik will always use the compliance mode of Impossible Cloud's object lock feature.
  5. Specify the regional storage endpoint that you intend to use under Host Name. You can find a full list of all available Impossible Cloud regions and endpoints here.
  6. Specify an unique Bucket Name. Rubrik will trigger the bucket creation via API but you need to ensure that the bucket name is not already taken. Otherwise, the bucket creation request will fail. 
  7. Specify the Number of Buckets. Typically, you will use one bucket per archival location.
  8. Create an Access and Secret key in the Impossible Cloud Storage Console and copy & paste it into the Rubrik interface. Remember to always securely store and manage your keys. Please find detailed information regarding the key creation in the Impossible Cloud documentation.
  9. When configuring Client-Side Encryption for S3-compatible archival locations in Rubrik, the required encryption method depends on whether the location is immutable or non-immutable: 
    1. Non-immutable: You need to generate and provide an RSA key. You can do it by following the  instructions provided by Rubrik (e.g. using openSSL).
    2. Immutable: You need to provide a password for encryption.

Important note: By default, Rubrik uses the deprecated V2 signature standard for its non-immutable S3-compatible storage connector. If you want to configure an Impossible Cloud bucket without object lock (immutability), you need to first contact Rubrik support to enable V4 since there is not yet a interface option to switch signature standards.

Step 3: Assign the new archival location to your SLA domain policy

After successfully adding your Impossible Cloud archival location, you must assign it to the appropriate SLA domain policy. To do this, navigate to the Archiving and Replication settings within your selected SLA domain. There, enable Archiving and choose the Impossible Cloud location from the list of available destinations.

You can then configure your offload policy, which defines how long backups are retained locally before being moved to Impossible Cloud. Alternatively, you may enable the Instant Archive option to send backups directly to the cloud immediately after they are created.