Chapter 17. Back up and restore Red Hat Update Infrastructure

Procedure

1. The /var/lib/pulp directory may be large, depending on how many repositories have been deployed on the Red Hat Update Appliance. See Preparing your Environment for Installation for specific storage requirements, or use the du command from the command line interface to determine its size.

2. Stop the pulp-server services.

   # systemctl stop pulp_workers; systemctl stop pulp_resource_manager; systemctl stop pulp_celerybeat

3. Replace stop with status in the above commands to verify each service has stopped.

4. It is important that the following files retain their current attributes when backed up:

   • /etc/httpd/conf.d/05-pulp-https.conf
   • /etc/httpd/conf.d/pulp*
   • /etc/httpd/conf.d/ssl.conf
   • /etc/pki/katello-certs-tools/*
   • /etc/pki/pulp/*
   • /etc/pki/rhui/*
   • /etc/pulp/*
   • /etc/puppet/*
   • /etc/rhui/*
   • /etc/rhui/rhui-tools.conf
   • /etc/rhui-installer/*
   • /etc/qpid/qpidd.conf
   • /var/lib/mongodb/pulp_database*
   • /var/lib/pulp/*
   • /var/log/pulp/*
   • /var/log/httpd/*

   • /var/lib/puppet/*

     Use the following command to back up the files:

     # cp -a source_files_path destination_files_path

5. You may want to back up any generated client entitlement certificates and client configuration RPMs.

6. Restart the pulp-server services.

   # systemctl start pulp_workers; systemctl start pulp_resource_manager; systemctl start pulp_celerybeat

7. Replace start with status in the above commands to verify each service has started.

Procedure

1. Prepare a new Red Hat Update Appliance instance by following Section 4.2, “Register Red Hat Update Infrastructure” and Section 4.3, “Attach a subscription to the Red Hat Update Appliance”. When those steps are completed, proceed with the following restoration steps.

2. Stop the pulp-server services.

   # systemctl stop pulp_workers; systemctl stop pulp_resource_manager; systemctl stop pulp_celerybeat

3. Replace stop with status in the above commands to verify each service has stopped.

   Important

   It is crucial that the files included in the restore retain their current attributes.

4. Use the following command to restore the files to their original locations:

   # cp -a source_files_path destination_files_path

5. Restart the pulp-server services.

   # systemctl start pulp_workers; systemctl start pulp_resource_manager; systemctl start pulp_celerybeat

6. Replace start with status in the above commands to verify each service has started.

Procedure

1. The /var/lib/pulp directory may be large, depending on how many repositories have been deployed on the Red Hat Update Appliance. See Preparing your Environment for Installation for specific storage requirements, or use the du command from the command line interface to determine its size.

2. Stop the httpd service.

   # systemctl stop httpd

3. Replace stop with status in the above commands to verify each service has stopped.

4. It is important that the following files retain their current attributes when backed up:

   • /etc/httpd/conf.d/*.conf
   • /var/lib/pulp/*
   • /var/log/pulp/*
   • /var/log/httpd/*
   • /etc/pki/rhui/*
   • /etc/pulp/*

   • /var/lib/puppet/*

     Use the following command to back up the files:

     # cp -a source_files_path destination_files_path

5. In addition to the above files, you may want to back up any generated client entitlement certificates and client configuration RPMs.

6. Restart the service.

   # systemctl start httpd

7. Replace start with status in the above commands to verify each service has started.

Procedure

1. Prepare a new CDS instance by following all steps in Section 7.1, “Add a content delivery server”. When those steps are completed, proceed with the following restoration steps.

2. Stop the httpd service.

   # systemctl stop httpd

3. Replace stop with status in the above commands to verify each service has stopped.

   Important

   It is crucial that the files included in the restore retain their current attributes.

4. Use the following command to restore the files to their original locations:

   # cp -a source_files_path destination_files_path

5. Restart the httpd service.

   # systemctl start httpd

6. Replace start with status in the above commands to verify each service has started.

Procedure

1. It is important that the following files retain their current attributes when backed up:

   • /etc/haproxy/haproxy.cfg
   • /etc/pki/rhui/*
   • /var/lib/puppet/*

2. Use the following command to back up the files:

   # cp -a source_files_path destination_files_path

3. In addition to the above files, you may want to back up any generated client entitlement certificates and client configuration RPMs.

Procedure

1. Prepare a new HAProxy instance by following all steps in Chapter 8, Add an HAProxy load balancer. When those steps are completed, proceed with the following restoration steps.

   Important

   It is crucial that the files included in the restore retain their current attributes.

2. Use the following command to restore the files to their original locations:

   # cp -a source_files_path destination_files_path