Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-32036

satellite 6.15 backup is missing "pgsql_data.tar.gz" file in the backup directory.

XMLWordPrintable

    • False
    • sat-rocket
    • None
    • None
    • None
    • None

      Description of problem:

      Upon taking the backup of the satellite 6.15 server, the below  files are generated in the backup directory.

      ]# ls -l /var/backup_directory/satellite-backup-2025-03-24-21-19-33
      total 2099048
      rw-rr-. 1 root root   70801788 Mar 24 21:21 candlepin.dump
      rw-rr-. 1 root root  642748677 Mar 24 21:20 config_files.tar.gz
      rw-rr-. 1 root root  130469178 Mar 24 21:21 foreman.dump
      rw-rr-. 1 root root      65420 Mar 24 21:20 metadata.yml
      rw-rr-. 1 root root 1305332233 Mar 24 21:24 pulpcore.dump

      It seems to be incomplete and missing the "pgsql_data.tar.gz" file.

       

      Upon checking the backup directory of satellite 6.14 and satellite 6.16

      =====  On Satellite 6.14 =======

      ]# ls  -l  /var/satellite-backup]# ls -l
      total 15849464
      rw-rr-. 1 root root    31567300 Mar 25 20:28 config_files.tar.gz
      rw-rr-. 1 root root       54459 Mar 25 20:27 metadata.yml
      rw-rr-. 1 root root 16198164480 Mar 25 20:37 pgsql_data.tar

      ========== On Satellite 6.16 ==========

      ]# ls -l
      total 6687236
      rw-rr-. 1 root root  635368377 Mar 20 17:52 config_files.tar.gz
      rw-rr-. 1 root root      61482 Mar 20 17:51 metadata.yml
      rw-rr-. 1 root root  933838771 Mar 20 17:53 pgsql_data.tar.gz

      =====================================

       

      How reproducible:

      It is 100% reproducible

       

      Steps to reproduce:

      1. mkdir /var/satellite-backup **
          • satellite-maintain backup offline --skip-pulp-content   -y /var/satellite-backup{}
            Starting backup: 2025-03-21 20:30:31 +0100
            Running preparation steps required to run the next scenarios
            ================================================================================
            Make sure Foreman DB is up:
            / Checking connection to the Foreman DB [OK]
            --------------------------------------------------------------------------------
            Make sure Candlepin DB is up:
      • Checking connection to the Candlepin DB [OK]
        --------------------------------------------------------------------------------
        Make sure Pulpcore DB is up:
        \ Checking connection to the Pulpcore DB [OK]
        --------------------------------------------------------------------------------

      Running Backup
      ================================================================================
      Check if the incremental backup has the right type: [OK]
      --------------------------------------------------------------------------------
      Check for running tasks: [OK]
      --------------------------------------------------------------------------------
      Check for running pulpcore tasks: [OK]
      --------------------------------------------------------------------------------
      Confirm turning off services is allowed:
      WARNING: This script will stop your services.

      Do you want to proceed? (assuming yes)
      [OK]
      --------------------------------------------------------------------------------
      Prepare backup Directory: [OK]
      --------------------------------------------------------------------------------
      Generate metadata:

      • Saving metadata to metadata.yml [OK]
        --------------------------------------------------------------------------------
        Detect features available in the local proxy: [OK]
        --------------------------------------------------------------------------------
        Stop applicable services:

      Stopping the following service(s):
      redis, postgresql, pulpcore-api, pulpcore-content, pulpcore-worker@1.service, pulpcore-worker@2.service, pulpcore-worker@3.service, pulpcore-worker@4.service, pulpcore-worker@5.service, pulpcore-worker@6.service, pulpcore-worker@7.service, pulpcore-worker@8.service, tomcat, pulpcore-api.socket, pulpcore-content.socket, dynflow-sidekiq@orchestrator, foreman, httpd, puppetserver, foreman.socket, dynflow-sidekiq@worker-1, dynflow-sidekiq@worker-hosts-queue-1, foreman-proxy
      \ All services stopped [OK]
      --------------------------------------------------------------------------------
      Backup config files:
      \ Collecting config files to backup [OK]
      --------------------------------------------------------------------------------
      Backup Pulp data: [SKIPPED]
      --------------------------------------------------------------------------------
      Start applicable services:

      Starting the following service(s):
      postgresql

      All services started [OK]
      --------------------------------------------------------------------------------
      Backup Candlepin database:
      • Getting Candlepin DB dump [OK]
        --------------------------------------------------------------------------------
        Backup Foreman database:
        \ Getting Foreman DB dump [OK]
        --------------------------------------------------------------------------------
        Backup Pulpcore database:
        / Getting Pulpcore DB dump [OK]
        --------------------------------------------------------------------------------
        Start applicable services:

      Starting the following service(s):
      pulpcore-worker@1.service, pulpcore-worker@2.service, pulpcore-worker@3.service, pulpcore-worker@4.service, pulpcore-worker@5.service, pulpcore-worker@6.service, pulpcore-worker@7.service, pulpcore-worker@8.service, dynflow-sidekiq@worker-1, dynflow-sidekiq@worker-hosts-queue-1
      \ starting dynflow-sidekiq@worker-hosts-queue-1
      Job for dynflow-sidekiq@worker-1.service failed because the control process exited with error code.
      See "systemctl status dynflow-sidekiq@worker-1.service" and "journalctl -xe" for details.

      Job for dynflow-sidekiq@worker-hosts-queue-1.service failed because the control process exited with error code.
      See "systemctl status dynflow-sidekiq@worker-hosts-queue-1.service" and "journalctl -xe" for details.

      All services started [OK]
      --------------------------------------------------------------------------------
      Start applicable services:

      Starting the following service(s):
      redis, postgresql, pulpcore-api, pulpcore-content, pulpcore-worker@1.service, pulpcore-worker@2.service, pulpcore-worker@3.service, pulpcore-worker@4.service, pulpcore-worker@5.service, pulpcore-worker@6.service, pulpcore-worker@7.service, pulpcore-worker@8.service, tomcat, dynflow-sidekiq@orchestrator, foreman, httpd, puppetserver, dynflow-sidekiq@worker-1, dynflow-sidekiq@worker-hosts-queue-1, foreman-proxy
      / All services started [OK]
      --------------------------------------------------------------------------------
      Compress backup data to save space: [OK]
      --------------------------------------------------------------------------------

      Done with backup: 2025-03-21 21:05:10 +0100

            • BACKUP Complete, contents can be found in: /var/satellite-backup ****
              [root@admhplvap64 ~]#

      /var/satellite-backup content:
      ]# date; ls -lht /var/satellite-backup/
      total 27G
      rw-rr-. 1 root root 8.5G Mar 21 21:04 pulpcore.dump
      rw-rr-. 1 root root 618M Mar 21 20:50 foreman.dump
      rw-rr-. 1 root root 1.4G Mar 21 20:49 candlepin.dump
      rw-rr-. 1 root root 16G Mar 21 20:47 config_files.tar.gz
      rw-rr-. 1 root root 72K Mar 21 20:30 metadata.yml
       

       

       

              Unassigned Unassigned
              rhn-support-shmohamm Shaikh Mohammed Afrid
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: