Satellite 6.3 introduces the "Satellite Clone" features which provides you with a simple way to copy or clone your Satellite or Capsule Server from one host to another.
This will make it simple for you to create a new environment for testing purposes or to upgrade the underlying operating system, for example from RHEL 6 to RHEL7.
The Satellite Clone feature uses a katello-backup which is copied from the original or source host to a new host.
- A source Satellite or Capsule 6.3 Server that you wish to clone
- A freshly installed RHEL 7 host or virtual machine that has access to the base RHEL7 packages and extras installed. This will be the target or clone server.
- A Satellite 6 subscription for the cloned server. If you would like to handle the registration of the system manually, set
- On the source server, perform a Satellite backup. The backup files are output to the specified backup directory.
# katello-backup --online-backup /backup/
- On the target server mount the shared storage that contains the katello-backup or copy the following files and folders into the
- On the target server, install the satellite-clone package
#yum install satellite-clone
- On the target server, customize the satellite-clone configuration file by editing
/etc/satellite-clone-vars.yml. To change an item from the default, remove the comment character (#) and edit its value.
required_root_free_spaceto 0 (Disabling this check since this may calculate the required space incorrectly in servers with mounted volumes)
register_to_portalto false (this will prevent satellite-clone tool from registering to portal again as the subscriptions are already attached in the previous steps)
backup_dirto the path containing the backup files.
- Change any other values to suit your requirements.
- Run the satellite-clone tool.
- Note that the satellite-clone tool changes the hostname of the cloned server to match the satellite production server by updating /etc/hosts to something like the following. This is intentional to clone your server with the config backup from the production server.
127.0.0.1 satellite.prod.com localhost.localdomain localhost
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
- The above mentioned hostname change of the cloned server will not affect the production server since DNS will still resolve your production server name to its production ip address.
- You will have an opportunity to change the hostname of the cloned server after cloning using katello-change-hostname <new_fqdn> --username <admin> --password <password> command.
- If you get error in any cloning step, please let us know for further steps. Performing any unrecommended steps in clone may affect your production server.
Note: On the target server, DHCP, DNS, TFTP and remote execution services are disabled. The cloning process disables these services on the target Satellite Server, to avoid conflict with the source Satellite Server.
[Optional] To re-enable DHCP, DNS, TFTP in the Satellite web UI. See Configuring DNS, DHCP, and TFTP on Satellite Server in the Installation Guide. Be aware of possible conflicts with your existing source Satellite infrastructure.
[Optional] If you want to re-enable remote execution, run the following command:
# satellite-installer --scenario satellite \
Log in to the Satellite web UI as user admin and password changeme. Change the admin user’s password.
Capsules' association with lifecycle environments - The cloning process breaks the association between Capsules and their lifecycle environments, to avoid interference with existing infrastructure. For testing purposes is recommended that you create new Capsule Servers to prevent interference with existing infrastructure.
Satellite Clone is complete.