RBMR AIX pre-script

The RBMR configuration utility (rbmrcfg) can be triggered pre Rubrik backup to run automatically. Generating a fresh configuration makes sure the file is up to date and takes account of any changes to disks/OS patches/hardware etc.

The RBMR configuration utility (rbmrcfg) can be triggered automatically before a Rubrik backup runs. Running rbmrcfg before each backup ensures the RBMR configuration reflects the current system state, including any recent changes to disks, the operating system, or hardware.

There are two stages required for setup:

  1. Creating a script on the source system

  2. Enable the setting in the Rubrik Console


Stage 1: Create the pre-backup script on the source

To confirm the correct PATH on your system (if required), run the following as root:

echo $PATH

Create a script (.sh) file at the following location:

/etc/rubrik/scripts/rbmr.sh

With the contents below:

#!/usr/bin/ksh PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin rbmrcfg

Ensure the script is executable:

chmod 755 /etc/rubrik/scripts/rbmr.


Stage 2: Configure the pre-script in the Rubrik Console

In the Rubrik Console, on the Add Fileset page, enter the script location in the Enable Pre/Post Scripts field:

/etc/rubrik/scripts/rbmr.sh

Choose whether to enable Cancel backup if pre-script fails:

  • Unchecked:
    The Rubrik backup continues even if the pre-script fails. The resulting backup may not be suitable for Bare Metal Recovery (BMR), depending on which files were not generated or included (for example, boot or critical filesystem configuration files).

  • Checked:
    The Rubrik backup fails if the pre-script encounters an error, preventing the creation of a backup that is not BMR-ready.


Troubleshooting

If the pre-script fails during a Rubrik backup:

  1. Run the pre-script directly on the source as root:

    /etc/rubrik/scripts/rbmr.sh

    Run rbmrcfg manually:

    rbmrcfg

If both commands run successfully when executed manually but fail when run by Rubrik, please gather all relevant logs and open a support case.

------------------------------------------------------------------------------------------------------------------------------------------------------