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

Improve the structure of the migration using backup/cloning section

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 6.16.0
    • Documentation, Upgrades
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • 0
    • Sat_docs_15_2024, Sat_docs_16_2024
    • None

      There are some challenges In understanding the flow of using the satellite clone method to migrate to RHEL9.

      In chapter 3.2 Migrating Satellite or Capsule to RHEL 9, we are asking users to take a backup and we have redirected them to Chapter 10.2. Performing a full backup of Satellite Server or Capsule Server. In this chapter all the backup methods are discussed, and we do not clarify whether users should take online or offline backup. Ideally for upgrades customers are expected to use OFFLINE backup but it is no where mentioned.
      In chapter 3.2 Migrating Satellite or Capsule to RHEL 9, we have point no:3, which suggests customers to restore the backup, again in the 4th point we have provided instructions to restore the database and pointed to the same guide.
      As per the feedback from CEE team, Satellite-Clone method saves time for customers to complete the RHEL version upgrade, so we wanted to push customers to use this satellite-clone method. So we wanted to call out specifically a 3rd method to upgrade the satellite using Satellite-Clone tool.
      We wanted to simplify the upgrade guide and avoid redirects from one guide to another as many customers do not like switching guides while performing any specific task, specially upgrade as it is a critical task.

              rhn-support-agadhave Akshay Gadhave
              rhn-support-agadhave Akshay Gadhave
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: