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

foreman-maintain online backup of Satellite generates warnings.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • None
    • 6.13.0
    • Satellite Maintain
    • False
    • Hide

      None

      Show
      None
    • False
    • CLOSED
    • 1,300
    • Platform
    • Important
    • No

      Description of problem:
      Online backup of Satellite fails with warnings.

      Running Backup
      ================================================================================
      Data consistency warning:

          • WARNING: The online backup is intended for making a copy of the data
          • for debugging purposes only. The backup routine can not ensure 100% consistency while the
          • backup is taking place as there is a chance there may be data mismatch between
          • the databases while the services are live. If you wish to utilize the online backup
          • for production use you need to ensure that there are no modifications occurring during
          • your backup run.

      Version-Release number of selected component (if applicable):
      Satellite 6.13

      Actual results:
      fails with warnings.

      And the document says:
      When performing an online backup, if there are procedures affecting the Pulp database, the Pulp part of the backup procedure repeats until it is no longer being altered. Because the backup of the Pulp database is the most time consuming part of backing up Satellite, if you make a change that alters the Pulp database during this time, the backup procedure keeps restarting.

      Expected results:

      It should work flawlessly.

      Additional info:

            jira-bugzilla-migration RH Bugzilla Integration
            jira-bugzilla-migration RH Bugzilla Integration
            RH Bugzilla Integration RH Bugzilla Integration
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: