Restore the services using Backupninja pipeline¶

This section describes how to restore the MAAS PostgreSQL database and the Salt Master node using the Backupninja Jenkins pipeline job.

To restore the services using the Jenkins pipeline job:

1. Verify that you have completed the steps described in Configure the Backupninja restore pipeline.

2. Log in to the Jenkins web UI.

3. Select from the following options:

   • For MCP versions prior to 2019.2.6, open the Backupninja restore salt-master/MaaS backup pipeline job.

   • For MCP versions starting from 2019.2.6, open the Backupninja restore pipeline pipeline job.

4. Specify the required parameters:

   Backupninja restore pipeline parameters¶

   Parameter	Description and values
   SALT_MASTER_URL	Add the IP address of your Salt Master node host and the salt-api port. For example, http://172.18.170.27:6969.
   CREDENTIALS_ID	Add credentials_id as credentials for the connection.
   RESTORE_SALTMASTER_AND_MAAS Added since 2019.2.6	Select to restore Salt Master and MAAS.
   RESTORE_KEYSTONE_CREDENTIAL_KEYS Added since 2019.2.12	Select to restore the Keystone credential keys.

5. Click Build.

   The Jenkins pipeline job workflow:

   1. Pillar verification. Verify that initial_data in pillars are defined correctly to prevent any issues related to a wrong configuration during the execution of the pipeline job.

   2. Perform the restore.

6. Verify that the restore completed and, in case of a remote backup storage, moved correctly:

   1. Verify the Salt Master node:

      1. Verify the Salt keys in /etc/salt/pki/.

      2. Verify the model in /srv/salt/reclass.

      3. Try to perform a test ping on the available Salt Minions using test.ping.

   2. Verify MAAS:

      1. Verify the MAAS UI.

      2. List the available machines in MAAS through the maasng.list_machines Salt module.