Chapter 2. Cloning Satellite Server

1. Back up the source server.
2. Clone the source server to the target server.
3. Power off the source server.
4. Update the network configuration on the target server to match the IP address of the target server with its new host name.
5. Test the new target server.

Procedure

1. Determine the size of the Pulp data:

   # du -sh /var/lib/pulp/

   Copy to Clipboard Toggle word wrap

2. If you have less than 500 GB of Pulp data, perform a backup with PostgreSQL databases active including the Pulp data. If you have more than 500 GB of Pulp data, skip the following steps and complete the steps in Section 2.3, “Pulp data considerations” before you continue.

   # satellite-maintain backup offline --assumeyes /var/backup

   Copy to Clipboard Toggle word wrap

3. Stop and disable Satellite services:

   # satellite-maintain service stop
   # satellite-maintain service disable

   Copy to Clipboard Toggle word wrap

1. The satellite-clone tool defaults to using /backup/ as the backup folder. If you copy to a different folder, update the backup_dir variable in the /etc/satellite-clone/satellite-clone-vars.yml file.
2. Place the backup files from the source Satellite in the /backup/ folder on the target server. You can either mount the shared storage or copy the backup files to the /backup/ folder on the target server.
3. Power off the source server.

4. Register your instance to the Red Hat Customer Portal and enable only the required repositories:

   # subscription-manager register
   # subscription-manager repos --disable=*
   # subscription-manager repos --enable=rhel-9-for-x86_64-appstream-rpms \
   --enable=rhel-9-for-x86_64-baseos-rpms \
   --enable=satellite-maintenance-6.18-for-rhel-9-x86_64-rpms

   Copy to Clipboard Toggle word wrap

5. Install the satellite-clone package:

   # dnf install satellite-clone

   Copy to Clipboard Toggle word wrap

   After you install the satellite-clone tool, you can adjust any configuration to suit your own deployment in the /etc/satellite-clone/satellite-clone-vars.yml file.

6. Run the satellite-clone tool:

   # satellite-clone

   Copy to Clipboard Toggle word wrap
7. Reconfigure DHCP, DNS, TFTP, and remote execution services. The cloning process disables these services on the target Satellite Server to avoid conflict with the source Satellite Server.
8. Reconfigure and enable DHCP, DNS, and TFTP in the Satellite web UI. For more information, see Integrating provisioning infrastructure services..
9. Log in to the Satellite web UI, with the username admin and the password changeme. Immediately update the admin password to secure credentials.
10. Ensure that the correct organization is selected.
11. In the Satellite web UI, navigate to Content > Subscriptions.
12. Click Manage Manifest.
13. Click Refresh and then click Close to return to the list of subscriptions.
14. Verify that the available subscriptions are correct.
15. Follow the instructions in the /usr/share/satellite-clone/logs/reassociate_capsules.txt file to restore the associations between Capsules and their lifecycle environments.
16. Update your network configuration, for example, DNS, to match the IP address of the target server with its new host name. The satellite-clone tool changes the host name to the source server’s host name. If you want to change the host name to something different, you can use the satellite-change-hostname tool. For more information, see Renaming Satellite Server in Administering Red Hat Satellite.
17. If the source server uses the virt-who daemon, install and configure it on the target server. Copy all the virt-who configuration files in the /etc/virt-who.d/ directory from the source server to the same directory on the target server. For more information, see Configuring virt-who for virtual machine subscriptions. After you perform an upgrade using the following chapters, you can safely decommission the source server.