Page Comparison

Introduction

Abiquo supports version 5.3 of Rubrik.

You can use Rubrik with:

• VMware vCloud Director

• VMware vCenter

...

Changes to the Rubrik integration

...

• The abiquo.rubrik.vcenter.id property is deprecated in Abiquo 5.4.4 and you should remove it

• The abiquo.backup.rubrik.sla property will now replace the default Rubrik SLA domains (Gold, Silver, Bronze).
  From Abiquo 5.4.4+ you must define ALL the default and custom domains that you wish to use in Rubrik. See #Rubrik configuration properties reference

Abiquo 6.0.0

• Optional abiquo.backup.policy.sync.delay property to set on the Abiquo Server in the abiquo.properties file.
  Specify

  , in milliseconds,

  how often to run the backup policy

  syncronization

  synchronization in milliseconds. The default value represents 24 hours. 

...

Requirements

• When you use Rubrik with vCloud Director

  • You must configure the endpoint in Rubrik properties

  • To create the Backup manager in Abiquo, you must enter Rubrik credentials and vCloud credentials separated by a hash (

    "

    #

    "

    ) or a custom separator configured in Rubrik properties

• For Rubrik, Abiquo backup policies must have the policy Code set to a valid Rubrik SLA Domain (default or custom)

• Users can add one backup policy only to a VM or they can request an immediate backup

...

The default Abiquo configuration includes the default Rubrik SLA Domains: Gold, Silver, and Bronze.

To use custom SLA domains, first create them in Rubrik.

...

To configure the Rubrik backup integration properties:

1. Log in to the Abiquo Remote Services server. 

2. Go to the /opt/abiquo/

...

1. config folder and create a

...

1.  rubrik.

...

1. properties file. 

   1. Make the tomcat user the owner of this file. 

   • This is the default location, but you can configure another location of the file in Abiquo properties

2. Edit this properties file and add properties as described in the following steps

3. If you are using Rubrik with vCloud Director, you must set the endpoint for vCloud, for example:

   Code Block
   abiquo.rubrik.vcloud.endpoint=https://myvclouddirector.example.com

4. For vCloud, configure each datacenter and its corresponding vCenter. Use the same index (integer) for a datacenter and its vCenter. The datacenter is the Name of an Abiquo public cloud region of the vCloud. To obtain the vCenter ID, obtain the Rubrik ID of a VM running on the vCenter from Rubrik. The format of the Rubrik ID is: VirtualMachine:::vCenterId-mobIdVM, so for example: VirtualMachine:::ee92b229-0dff-4632-b94e-eb9f581e1cff-vm-18662. In this case, the vCenter ID is ee92b229-0dff-4632-b94e-eb9f581e1cff. For example

   Code Block
   #abiquo.rubrik.infrastructure.datacenter.1=VCD Madrid Enterprise 1 #abiquo.rubrik.infrastructure.vcenter.1=ee92b229-0dff-4632-b94e-eb9f581e1cff

...

2. If you are using anything other than all three default Gold, Silver, and Bronze SLA domains, set the sla property to define ALL your domain names. The value of the sla property is a comma separated list. This list will replace the default domains.

   Code Block
   abiquo.backup.rubrik.sla=Gold,Platinum,Palladium

3. You can add any of the other properties from the Rubrik configuration properties reference below as required. Don't forget to remove the hash

...

1. #

...

1. comment symbol from the start of each property. 

...

...

Configure Abiquo Properties

To activate the Rubrik plugin and define the location of the configuration file:

1. Log in to the Abiquo Remote Services server

2. Edit the abiquo.properties file. 

3. Set the path to the plugin properties file using the following property.

   Code Block
   abiquo.backup.rubrik.config.path=/opt/abiquo/config/rubrik.properties

4. Optionally, configure other rubrik properties for nars and virtualfactory as required:

   1. Abiquo configuration

...

1. 1. properties for nars

   2. Abiquo configuration

...

1. 1. properties for virtual factory

2. Optionally,

...

1. log in to the Abiquo API Server, and configure how often to run the backup policy synchronization check

   Code Block
   # Delay between executions of the backup policy check (milliseconds). # The default represents 24 hours. #abiquo.backup.policy.sync.delay=86400000

...

Configure all backup jobs with policy codes

...

# Log level for feign client
#abiquo.rubrikclient.feign.logger.level=INFO

# Timeout for client to connect to the Rubrik API. To disable the timeout, set the value to 0 
#abiquo.rubrikclient.timeout.connectionInSeconds=300

# Timeout for client to read from Rubrik API. To disable the timeout, set the value to 0 
#abiquo.rubrikclient.timeout.readInSeconds=300 

# Maximum time to wait for task to finish in Rubrik API 
#abiquo.rubrik.task.max.minutes=30 

# Interval between checks if task is finished in Rubrik API
#abiquo.rubrik.task.period.minutes=1 

# Timeout for client to connect to vCloud API. To disable the timeout, set the value to 0 
#abiquo.rubrik.vcloudclient.timeout.connectionInSeconds=300 

# Timeout for client to read from the vCloud API. To disable the timeout, set the value to 0 
#abiquo.rubrik.vcloudclient.timeout.readInSeconds=300 

# For vCloud, character to split user into backup system and vCloud user
#abiquo.rubrik.credentials.splitter.user=# 

# For vCloud, character to split password into backup system and vCloud password
#abiquo.rubrik.credentials.splitter.pass=# 

# Number of backup results  
#abiquo.rubrik.clients.pagesize=50 

# In addition to the default Gold, Silver, and Bronze SLA Domains
# List of custom SLA Domains that you already configured in Rubrik
#abiquo.backup.rubrik.sla=

# For Abiquo 5.4.4+, with vCloud, configure each datacenter and its corresponding vCenter.
# Use the same index (integer) for a datacenter and its vCenter.
# The datacenter is the Name of an Abiquo public cloud region of the vCloud.
# To obtain the vCenter ID, obtain the Rubrik ID of a VM running on the vCenter from Rubrik.
# The format of the Rubrik ID is: VirtualMachine:::vCenterId-mobIdVM
# For example: VirtualMachine:::ee92b229-0dff-4632-b94e-eb9f581e1cff-vm-18662
# In this case, the vCenter ID is ee92b229-0dff-4632-b94e-eb9f581e1cff 
#abiquo.rubrik.infrastructure.datacenter.<index>=
#abiquo.rubrik.infrastructure.vcenter.<index>=