Configure the Backupninja backup pipeline¶

The Backupninja backup pipeline supports backup of the following components:

• MAAS, including the PostgreSQL database that contains the data for MAAS and machines that are registered and managed by MAAS
• Salt Master, including the PKI keys, certificates, the Salt Minion on cfg01, and the metadata model
• Dogtag server files and database

To use the Backupninja backup pipeline, you must override the current Backupninja configuration and disable the default backup schedule. This section describes how to configure the Backupninja backup pipeline.

To configure the Backupninja backup pipeline:

1. Log in to the Salt Master node.

2. Verify that Backupninja scheduling is set to manual:

   salt-call pillar.get backupninja:client
   

   Example of system response:

   parameters:
     backupninja:
       client:
         scheduling:
           when:
             - manual
   

3. If the pillars do not include the parameter above or it has a different value:

   1. Manually override the value by adding the following block to infra/backup/client_common.yml.

      parameters:
        backupninja:
          client:
            scheduling:
              when:
                - manual
      

   2. Apply the backupninja state:

      salt -C 'I@backupninja:client' state.sls backupninja
      

4. Verify that the class with the Backupninja backup Jenkins job is present in the pillar:

   salt -C 'I@jenkins:client and not I@salt:master' pillar.get jenkins:client:job:backupninja_backup
   

5. If the pillars do not include the Backupninja backup pipeline:

   1. Add the following class to cicd/control/leader.yml:

      - system.jenkins.client.job.deploy.backupninja_backup
      

   2. Rerun the jenkins state on the cid01 node:

      salt -C 'I@jenkins:client and not I@salt:master' state.sls jenkins.client