The following list describes the prerequisites and assumptions you need to address to ensure a successful transition from Red Hat Satellite 5.6 or 5.7 to Satellite 6.
Ensure you start with a fully-functional, up-to-date Satellite 5.6 or 5.7 server.
Satellite 6 must be correctly installed and configured on a second machine. This installation must include a manifest that provides access to the same content as the Satellite 5.6 or 5.7 instance, and for the same number of clients.
The Satellite 6 instance must be synchronized with the desired Red Hat content before you start the transition process. The transition tools are purposely designed not to copy Red Hat content from Satellite 5 to Satellite 6.
The transition tools are designed to work in environments where network security prevents direct connection between the Satellite 5 and Satellite 6 instances. Consequently, the tools were designed to work in isolation, in two stages. The first stage is to export data from Satellite 5, and the second stage is to import data into Satellite 6. After the first stage is complete, you can use network tools (for example,
SCP) or physical media to transfer the exported data to the Satellite 6 server.
The export tools run on the Satellite 5 system. This allows direct access to the Satellite 5 database, repositories, and existing tools such as
spacewalk-report. It is also necessary because some customer sites have networking restrictions that limit access to the Satellite 5 instance.
The import tools run on the Satellite 6 system, for similar reasons.
Given the differences in data models and functionality between Satellite 5 and Satellite 6, importing Satellite 5 data cannot achieve a perfectly-configured Satellite 6 instance. The goal is to reduce the amount of configuration as much as possible.