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?
- 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.
- 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.
- As root on Satellite 5, run the exporter command-line tool.
- Copy the resulting data onto Satellite 6.
- As root on Satellite 6, run the importer command-line tools.
- 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.
- 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
- 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
/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.