Red Hat Training

A Red Hat training course is available for Red Hat Satelitte

3.4. Frequently Asked Questions

Can I perform an in-place upgrade from Satellite 5 to Satellite 6?
Which versions of Satellite 5 are supported for the transition?
Which versions of Red Hat Enterprise Linux will Satellite 5 and Satellite 6 support as client systems?
What is the quick version of how to transition from Satellite 5 to Satellite 6?
Will the transition tools work with a disconnected server?
Will the transition tools transition all data from Satellite 5 to Satellite 6?
Can I run the transition tools and process multiple times?
Can I use the export tools on my production Satellite 5 system?
Can I perform an in-place upgrade from Satellite 5 to Satellite 6?
The underlying technologies between Satellite 5 and 6 are significantly different. For this reason, the in-place upgrade process (such as from version 4.x to 5.x or from 5.x to 5.y) does not apply for version 5 to 6. Satellite 6 needs to be installed on a new server as part of the side-by-side transition process. Consequently, this is referred to as a transition process and not an upgrade process.
Which versions of Satellite 5 are supported for the transition?
The transition path begins with Satellite 5.6 or 5.7. If you are running an earlier version of Satellite you first need to upgrade to at least version 5.6.
Future releases of Satellite will also be supported as platforms for moving from Satellite 5.

Note

If you plan a more passive transition process, the prior Satellite version does not matter. A passive transition process is more of an adoption process where legacy workloads remain on Satellite 5 and new workloads are freshly modeled on Satellite 6 as if it is treated as new infrastructure for your Red Hat Enterprise Linux Systems Management needs.
Which versions of Red Hat Enterprise Linux will Satellite 5 and Satellite 6 support as client systems?
The following support matrix currently applies:
  • Satellite 5.6 supports clients of Red Hat Enterprise Linux versions 4, 5, 6, and 7.
  • Satellite 6 supports clients of Red Hat Enterprise Linux versions 5.7 and later, 6.1 and later, and 7.0 and later.
  • Satellite 6 does not support clients of version Red Hat Enterprise Linux 4.
What is the quick version of how to transition from Satellite 5 to Satellite 6?
  1. Install Satellite 6, activate with a manifest and synchronize Red Hat content from CDN.
    • Review the documentation, learn and understand the basics of the Satellite 6 product, including new concepts, such as environments.
    • Back up the new Satellite 6 server, including databases, before using the transition tools.
  2. As root on Satellite 5, run the exporter command-line tool.
  3. Copy the resulting data onto Satellite 6.
  4. As root on Satellite 6, run the importer command-line tools.
  5. Validate and test the resulting Satellite 6 system for a subset of end to end functionality and important use-cases corresponding to the data-types transitioned from Satellite 5 to 6.

Note

Not all of the concepts can be translated between Satellite 5 and 6. Some manual steps are required to fully populate the newly installed Satellite 6 server.
Will the transition tools work with a disconnected server?
Yes, the transition tools are designed such that a disconnected environment is assumed, and neither Satellite 5 nor 6 can directly communicate with each other or the Internet in general.
Will the transition tools transition all data from Satellite 5 to Satellite 6?
No. In some situations, Satellite 5 and Satellite 6 take different approaches to the tasks of synchronizing and provisioning hosts, managing entitlements, and dealing with disconnected environments. Some configuration, system, and host data is also created and stored differently. Consequently, not all data can be successfully transitioned.
In Satellite 6, the following information cannot be transitioned:
  • Activation-keys that use "Red Hat default"
  • Anything history- or audit-related (events, oscap runs, and so on)
  • Anything monitoring-related
  • Configuration-channel ordering
  • Distribution-channel mapping
  • Kickstart data (other than snippets)
  • Organization entitlement-distribution (users need to create their own manifests)
  • Organization-trusts settings
  • Snapshots
  • Stored package-profiles
  • Custom system information, such as key/value pairs, system notes, and system properties in general. The latter is completed when a system registers to Satellite 6 and connects to the created profile.
  • User preferences
Can I run the transition tools and process multiple times?
Yes, the transition tools are idempotent. You can reuse the tools to create Satellite 6 data and preserve previous information. A small data file on the Satellite 6 server preserves the history of previous runs and tracks what has already been imported.
Can I use the export tools on my production Satellite 5 system?
Yes, assuming that you run the tools with sufficient disk space. Disk space will vary, from 20 MB to several Gigabytes, depending on the total amount of non-Red Hat content stored on the Satellite in /var/satellite/redhat/ and being selected for export by the export tool. When exporting custom or cloned channels, the tool searches for non-Red Hat content associated with the channels, to copy into the export archive. Other than some short-term CPU and memory consumption, the tool only performs read-only file system, and SQL queries on the database to gather data, write the resulting data to files on disk, and create a tar archive of the data.