Procedure 2.1. Creating and Mounting a Database Partition

1. Log in to the database server as root. For Embedded Databases, this is the same server as the Red Hat Satellite.
2. Create the postgres user.

   # useradd -d /var/lib/pgsql -M -r -s /bin/bash -U postgres
   

3. Add the mount point in /etc/fstab. For example:

   UUID="xxxxxxxx-xxxx-xxxx" /var/opt/rh/rh-postgresql95/lib/pgsql/data  ext4  defaults  0 0
   

   Important

   Red Hat does not support storing the database on a network filesystem.
4. Mount the partition to /var/opt/rh/rh-postgresql95/lib/pgsql/data and change ownership to postgres:postgres:

   # mkdir -p /var/opt/rh/rh-postgresql95/lib/pgsql/data
   # mount /var/opt/rh/rh-postgresql95/lib/pgsql/data
   # chown postgres:postgres /var/opt/rh/rh-postgresql95/lib/pgsql/data
   # chmod 700 /var/opt/rh/rh-postgresql95/lib/pgsql/data
   # restorecon -Rv /var/opt/rh/rh-postgresql95/lib/pgsql/data
   

Procedure 3.1. Download the Installation Media

1. Log on to the Customer Portal.
2. Click Downloads.
3. Click Red Hat Satellite.
4. Select 5.8 for RHEL 6 from the Versions drop-down list.
5. Select x86_64 or s390x from the Architecture list.
6. Download the Red Hat Satellite 5.8 Binary DVD.
7. Depending on your preferred installation source, either copy the DVD ISO image to the Satellite host, or burn it to DVD media.
   1. If you will be mounting the ISO image and running the installation program from there, copy the ISO image to the Satellite host.

      # scp satellite.iso root@hostname:/root
      

      Note

      If you will be installing a Managed DB instance, also copy the ISO image to that host.
   2. If you will be mounting a DVD and running the installation program from there, burn the DVD ISO image to DVD media.

Procedure 3.2. Mounting from a disc

1. Log into the machine as root.
2. Insert the Red Hat Satellite Server CD or DVD containing the installation files.
3. Red Hat Enterprise Linux might automount the disc. If so, it mounts the disc to the /media/cdrom/ directory. If Red Hat Enterprise Linux does not automount the disc, manually mount it to the /media/cdrom/ directory with the following command:

   # mkdir /media/cdrom
   # mount /dev/cdrom /media/cdrom
   

Procedure 3.3. Mounting from an ISO image

1. Log into the host as root.
2. Mount the ISO image to a location on your filesystem:

   # mkdir /media/cdrom
   # mount -o loop iso_filename /media/cdrom
   

Procedure 3.4. Generate New Satellite 5.8 Manifest

1. Log on to the Customer Portal and navigate to Subscriptions in the upper-left corner.
2. Navigate to Subscription Allocations.
3. Click New subscription allocation.
4. Enter a name in the Name field, select Satellite 5.8 from the Type drop-down list, and click Create.
5. Navigate to the Subscription tab and click Add subscriptions.
6. For each product to be attached to the manifest, specify the desired quantity in the Entitlements field, and click Submit. It may take several minutes for the subscriptions to be attached.
7. Click Export Manifest and save the manifest file locally.
8. Log out of the Customer Portal.
9. Access the terminal on the host to which the manifest file was downloaded.
   If the Satellite server is available via the network, copy the manifest file to the Satellite host. In this example, the file is copied to the /root directory.

   # scp manifest_file.zip root@satellite.example.com:/root
   

   If the Satellite server is disconnected, copy the manifest file to portable media, and on the Satellite server, copy the manifest file from the portable media.

Procedure 3.5. Activate the Satellite Repositories

1. List all available subscriptions, and identify the Red Hat Satellite 5 subscription.
   The list of available subscriptions may be long, but if you pipe the output into a pager utility, such as less or more, you can read the output one screenful at a time.

   # subscription-manager list --all --available | less
   

   Note the Pool ID as this is required to attach the subscription.
2. Attach the subscription to the host.

   # subscription-manager attach --pool=pool_id

   The output should be similar to the following:

   Successfully attached a subscription for: Red Hat Satellite
   

3. Disable all repositories.

   # subscription-manager repos --disable "*"
   

4. Enable the Red Hat Enterprise Linux 6 repository. The Red Hat Satellite 5.8 repository will be enabled automatically by the installation program.
   For ⁠AMD64 and Intel 64

   # subscription-manager repos --enable=rhel-6-server-rpms
   

   For IBM System z

   # subscription-manager repos --enable=rhel-6-for-system-z-rpms
   

Procedure 3.6. Running Installation Program

1. Run the installation program from the /media/cdrom/ directory:

   # ./install.pl
   

   The installation program first verifies the requirements in Chapter 2, Requirements are met before proceeding.

   * Starting the Red Hat Satellite installer.
   * Performing pre-install checks.
   * Pre-install checks complete.  Beginning installation.
   

2. The script performs host registration with Red Hat Subscription Manager (if not already done), installs and updates all required packages, and populates the database on the Managed Database Host.
   If the installation program prompts with the question, "Do you want the installer to resolve dependencies [y/N]?", reply y (Yes).

   * RHSM Registration.
   ** Registration: System is already registered with RHSM.  Not re-registering.
   * RHSM Subscriptions.
   ** Subscriptions: Subscription providing 'Red Hat Satellite' already attached.
   ** Subscriptions: Subscription providing 'Red Hat Enterprise Linux Server' already attached.
   ** Subscriptions: Disabling all RHSM repositories (rhel-6-server-rpms).
   ** Subscriptions: All repositories disabled.
   ** Subscriptions: Enabling RHEL repository.
   ** Subscriptions: RHEL repository enabled.
   * Checking for uninstalled prerequisites.
   ** Checking if yum is available ...
   There are some packages from Red Hat Enterprise Linux that are not part
   of the @base group that Satellite will require to be installed on this
   system. The installer will try resolve the dependencies automatically.
   However, you may want to install these prerequisites manually.
   Do you want the installer to resolve dependencies [y/N]? y
   * Installing Satellite packages.
   Warning: yum did not install the following packages:
   	libXt
   * Now running spacewalk-setup.
   * Setting up SELinux..
   ** Database: Setting up database connection for PostgreSQL backend.
   Database "rhnschema" does not exist
   ** Database: Installing the database:
   ** Database: This is a long process that is logged in:
   ** Database:   /var/log/rhn/install_db.log
   *** Progress: #
   ** Database: Installation complete.
   ** Database: Populating database.
   *** Progress: ###########################
   

Procedure 3.7. Download the Installation Media

1. Log on to the Customer Portal.
2. Click Downloads.
3. Click Red Hat Satellite.
4. Select 5.8 for RHEL 6 from the Versions drop-down list.
5. Select x86_64 or s390x from the Architecture list.
6. Download the Red Hat Satellite 5.8 Binary DVD.
7. Depending on your preferred installation source, either copy the DVD ISO image to the Satellite host, or burn it to DVD media.
   1. If you will be mounting the ISO image and running the installation program from there, copy the ISO image to both the Satellite host and the Managed DB host.

      # scp satellite.iso root@satellite_hostname:/root
      # scp satellite.iso root@manageddb_hostname:/root
      

   2. If you will be mounting a DVD and running the installation program from there, burn the DVD ISO image to DVD media.

Procedure 3.8. Mounting from a disc

1. Log into the machine as root.
2. Insert the Red Hat Satellite Server CD or DVD containing the installation files.
3. Red Hat Enterprise Linux might automount the disc. If so, it mounts the disc to the /media/cdrom/ directory. If Red Hat Enterprise Linux does not automount the disc, manually mount it to the /media/cdrom/ directory with the following command:

   # mkdir /media/cdrom
   # mount /dev/cdrom /media/cdrom
   

Procedure 3.9. Mounting from an ISO image

1. Log into the host as root.
2. Mount the ISO image to a location on your filesystem:

   # mkdir /media/cdrom
   # mount -o loop iso_filename /media/cdrom
   

Procedure 3.10. Generate New Satellite 5.8 Manifest

1. Log on to the Customer Portal and navigate to Subscriptions in the upper-left corner.
2. Navigate to Subscription Allocations.
3. Click New subscription allocation.
4. Enter a name in the Name field, select Satellite 5.8 from the Type drop-down list, and click Create.
5. Navigate to the Subscription tab and click Add subscriptions.
6. For each product to be attached to the manifest, specify the desired quantity in the Entitlements field, and click Submit. It may take several minutes for the subscriptions to be attached.
7. Click Export Manifest and save the manifest file locally.
8. Log out of the Customer Portal.
9. Access the shell prompt on the host to which the manifest file was downloaded.
   Copy the manifest file to the Satellite host. In this example, the file is copied to the /root directory.

   # scp manifest_file.zip root@satellite.example.com:/root
   

Procedure 3.11. Activate the Satellite Repositories

1. List all available subscriptions, and identify the Red Hat Satellite 5 subscription.
   The list of available subscriptions may be long, but if you pipe the output into a pager utility, such as less or more, you can read the output one screenful at a time.

   # subscription-manager list --all --available | less
   

   Note the Pool ID as this is required to attach the subscription.
2. Attach the subscription to the host.

   # subscription-manager attach --pool=pool_id

   The output should be similar to the following:

   		Successfully attached a subscription for: Red Hat Satellite
   

3. Disable all repositories.

   # subscription-manager repos --disable "*"
   

4. Enable the Red Hat Enterprise Linux 6 repository. The Red Hat Satellite 5.8 repository will be enabled automatically by the installation program.
   For ⁠AMD64 and Intel 64

   # subscription-manager repos --enable=rhel-6-server-rpms
   

   For IBM System z

   # subscription-manager repos --enable=rhel-6-for-system-z-rpms
   

Procedure 3.12. Installing the Managed Database

1. Log into the host to be used for the Managed Database as the root user.
2. Navigate to the directory containing the Satellite installation program.

   # cd /media/cdrom
   

3. Run the installation program with the --managed-db option.

   # ./install.pl --managed-db
   

4. The installation program asks for the following information.
   • Database name
   • Database user
   • Database password
   • A comma-separated list of local addresses to listen. Leave blank for all addresses.
   • A comma-separated list of remote addresses in address/netmask format. The Managed Database allows connections from these addresses.

   Database name: mydb
   Database user: mydbuser
   Database password:  mydbpassword
   Local addresses to listen on (comma-separated, RETURN for all): 127.0.0.1
   Remote addresses to allow connection from (address/netmask format, comma-separated): 192.168.1.10/32
   Initializing database:                                     [  OK  ]
   Starting postgresql service:                               [  OK  ]
   

Procedure 3.13. Running Installation Script

1. Run the installer script from the /media/cdrom/ directory:

   # ./install.pl --external-postgresql
   

   The installation program first verifies the requirements in Chapter 2, Requirements are met before proceeding.

   * Starting the Red Hat Satellite installer.
   * Performing pre-install checks.
   * Pre-install checks complete.  Beginning installation.
   

2. The script performs host registration with Red Hat Subscription Manager (if not already done), installs and updates all required packages, and populates the database on the Managed Database host.

   * RHSM Registration.
   ** Registration: System is already registered with RHSM.  Not re-registering.
   * RHSM Subscriptions.
   ** Subscriptions: Subscription providing 'Red Hat Satellite' already attached.
   ** Subscriptions: Subscription providing 'Red Hat Enterprise Linux Server' already attached.
   ** Subscriptions: Disabling all RHSM repositories (rhel-6-server-rpms).
   ** Subscriptions: All repositories disabled.
   ** Subscriptions: Enabling RHEL repository.
   ** Subscriptions: RHEL repository enabled.
   * Checking for uninstalled prerequisites.
   ** Checking if yum is available ...
   There are some packages from Red Hat Enterprise Linux that are not part
   of the @base group that Satellite will require to be installed on this
   system. The installer will try resolve the dependencies automatically.
   However, you may want to install these prerequisites manually.
   Do you want the installer to resolve dependencies [y/N]? y
   * Installing Satellite packages.
   Warning: yum did not install the following packages:
   	libXt
   * Now running spacewalk-setup.
   * Setting up SELinux..
   ** Database: Setting up database connection for PostgreSQL backend.
   Hostname (leave empty for local)? satellite-db.example.com
   Port [5432]?
   Database? mydb
   Username? mydbuser
   Password? ************
   ** Database: Populating database.
   *** Progress: ####################################
   

Procedure 3.14. Download the Installation Media

1. Log on to the Customer Portal.
2. Click Downloads.
3. Click Red Hat Satellite.
4. Select 5.8 for RHEL 6 from the Versions drop-down list.
5. Select x86_64 or s390x from the Architecture list.
6. Download the Red Hat Satellite 5.8 Binary DVD.
7. Depending on your preferred installation source, either copy the DVD ISO image to the Satellite host, or burn it to DVD media.
   1. If you will be mounting the ISO image and running the installation program from there, copy the ISO image to the Satellite host.

      # scp satellite.iso root@hostname:/root
      

      Note

      If you will be installing a Managed DB instance, also copy the ISO image to that host.
   2. If you will be mounting a DVD and running the installation program from there, burn the DVD ISO image to DVD media.

Procedure 3.15. Mounting from a disc

1. Log into the machine as root.
2. Insert the Red Hat Satellite Server CD or DVD containing the installation files.
3. Red Hat Enterprise Linux might automount the disc. If so, it mounts the disc to the /media/cdrom/ directory. If Red Hat Enterprise Linux does not automount the disc, manually mount it to the /media/cdrom/ directory with the following command:

   # mkdir /media/cdrom
   # mount /dev/cdrom /media/cdrom
   

Procedure 3.16. Mounting from an ISO image

1. Log into the host as root.
2. Mount the ISO image to a location on your filesystem:

   # mkdir /media/cdrom
   # mount -o loop iso_filename /media/cdrom
   

Procedure 3.17. Generate New Satellite 5.8 Manifest

1. Log on to the Customer Portal and navigate to Subscriptions in the upper-left corner.
2. Navigate to Subscription Allocations.
3. Click New subscription allocation.
4. Enter a name in the Name field, select Satellite 5.8 from the Type drop-down list, and click Create.
5. Navigate to the Subscription tab and click Add subscriptions.
6. For each product to be attached to the manifest, specify the desired quantity in the Entitlements field, and click Submit. It may take several minutes for the subscriptions to be attached.
7. Click Export Manifest and save the manifest file locally.
8. Log out of the Customer Portal.
9. Access the shell prompt on the host to which the manifest file was downloaded.
   Copy the manifest file to the Satellite host. In this example, the file is copied to the /root directory.

   # scp manifest_file.zip root@satellite.example.com:/root
   

Procedure 3.18. Activate the Satellite Repositories

1. List all available subscriptions, and identify the Red Hat Satellite 5 subscription.
   The list of available subscriptions may be long, but if you pipe the output into a pager utility, such as less or more, you can read the output one screenful at a time.

   # subscription-manager list --all --available | less
   

   Note the Pool ID as this is required to attach the subscription.
2. Attach the subscription to the host.

   # subscription-manager attach --pool=pool_id

   The output should be similar to the following:

   Successfully attached a subscription for: Red Hat Satellite
   

3. Disable all repositories.

   # subscription-manager repos --disable "*"
   

4. Enable the Red Hat Enterprise Linux 6 repository. The Red Hat Satellite 5.8 repository will be enabled automatically by the installation program.
   For ⁠AMD64 and Intel 64

   # subscription-manager repos --enable=rhel-6-server-rpms
   

   For IBM System z

   # subscription-manager repos --enable=rhel-6-for-system-z-rpms
   

Procedure 3.19. Running Installation Program

1. Run the installation program from the /media/cdrom/ directory. To install to an external PostgreSQL database:

   # ./install.pl --external-postgresql
   

   Or to install to an external Oracle database:

   # ./install.pl --external-oracle
   

   The installation program first verifies the requirements in Chapter 2, Requirements are met before proceeding.

   * Starting the Red Hat Satellite installer.
   * Performing pre-install checks.
   * Pre-install checks complete.  Beginning installation.
   

2. The script performs host registration with Red Hat Subscription Manager (if not already done), installs and updates all required packages, and populates the database on the Managed Database Host.

   * RHSM Registration.
   ** Registration: System is already registered with RHSM.  Not re-registering.
   * RHSM Subscriptions.
   ** Subscriptions: Subscription providing 'Red Hat Satellite' already attached.
   ** Subscriptions: Subscription providing 'Red Hat Enterprise Linux Server' already attached.
   ** Subscriptions: Disabling all RHSM repositories (rhel-6-server-rpms).
   ** Subscriptions: All repositories disabled.
   ** Subscriptions: Enabling RHEL repository.
   ** Subscriptions: RHEL repository enabled.
   * Checking for uninstalled prerequisites.
   ** Checking if yum is available ...
   There are some packages from Red Hat Enterprise Linux that are not part
   of the @base group that Satellite will require to be installed on this
   system. The installer will try resolve the dependencies automatically.
   However, you may want to install these prerequisites manually.
   Do you want the installer to resolve dependencies [y/N]? y
   * Installing Satellite packages.
   Warning: yum did not install the following packages:
   	libXt
   * Now running spacewalk-setup.
   * Setting up SELinux..
   ** Database: Setting up database connection for PostgreSQL backend.
   Database "rhnschema" does not exist
   ** Database: Installing the database:
   ** Database: This is a long process that is logged in:
   ** Database:   /var/log/rhn/install_db.log
   *** Progress: #
   ** Database: Installation complete.
   ** Database: Populating database.
   *** Progress: ###########################
   

1. Run the Active Directory Users and Computers program on your Windows machine with a user that has rights to add users into your domain. Create a user named virtwho-readonly-user.
2. Log in to vSphere Web Client using an account with administrator privileges.
3. Navigate to Home → Administration → Single Sign-On → Configuration.
   

   Figure 7.1. Navigate to Single Sign-On Configuration

4. Navigate to the Identity Sources tab, press the plus icon, and select the Active Directory identity source. This adds Active Directory identity source, including the virtwho-readonly-user user.
   

   Figure 7.2. Add the Identity Source

5. Navigate to Home → vCenter and select the vCenter to grant access to virtwho-readonly-user.
   

   Figure 7.3. Navigate to vCenter

6. Navigate to Manage → Permissions and press the plus icon to open the Add Permission dialog.
   

   Figure 7.4. Click the plus icon

7. Select the virtwho-readonly-user.
8. Select the Read-only role.
9. Click OK to save the permissions.
10. Log out and test the virtwho-readonly-user in vCenter. Make sure the inventory shows the resources that virtwho-readonly-user can access.

1. Log in to the Satellite server and install virt-who:

   # yum install virt-who
   

2. Edit the /etc/sysconfig/virt-who file and use the following options:

   # virt-who options
   VIRTWHO_BACKGROUND=1
   VIRTWHO_DEBUG=1
   
   # Enable virt-who with VMware
   VIRTWHO_ESX=1
   
   # Options for ESX mode
   VIRTWHO_ESX_ENV=not-used
   VIRTWHO_ESX_OWNER=[organization_id]
   VIRTWHO_ESX_SERVER=vcenter.example.com
   VIRTWHO_ESX_USERNAME=DOMAIN\\virtwho-readonly-user
   VIRTWHO_ESX_PASSWORD=*******
   
   # Report to Satellite
   VIRTWHO_SAM=0
   VIRTWHO_SATELLITE=1
   

   Replace [organization_id] with the ID of your target organization on your Satellite server.
3. Start and enable the virt-who service:

   # service virt-who start
   # chkconfig virt-who on
   

Procedure 8.1. Obtain the Channel Content ISOs

1. Log into the web interface.
2. Click Channels in the top navigation bar.
3. Click on the Red Hat Satellite channel. Ensure you select the Satellite channel that corresponds to your version of Satellite.
4. Click the Downloads tab and use the instructions on the page to obtain the Channel Content ISOs, available by version of Red Hat Enterprise Linux.
5. If the desired Channel Content ISOs do not appear, ensure your Red Hat Entitlement Certificate has been uploaded to Red Hat Network and correctly identifies the target channels.

Procedure 8.2. Mount and copy Channel Content ISOs

1. Log into the machine as root.
2. Create a directory in /mnt/ to store the file(s) with the command:

   # mkdir /mnt/import/
   

3. Mount the ISO file using the following command:

   # mount [iso_filename] /mnt/import -o loop
   

4. Create a target directory for the files:

   # mkdir /var/rhn-sat-import/
   

5. This sample command assumes the administrator wants to copy the contents of the ISO (mounted in /mnt/import/) into /var/rhn-sat-import/:

   # cp -ruv /mnt/import/* /var/rhn-sat-import/
   

6. Then unmount /mnt/import in preparation for the next ISO:

   # umount /mnt/import
   

7. Repeat these steps for the channel content ISO file of every channel that you need to import separately. Do not use combined full or incremental sources of channel content ISOs.

1. List the channels available for import.

   # satellite-sync --list-channels --mount-point=/var/rhn-sat-import
   

2. Initiate the import of a specific channel using a channel label presented in the previous list.

   # satellite-sync --channel=[channel-label] --mount-point=/var/rhn-sat-import
   

   Note

   Importing package data can take up to two hours per channel. Register systems to channels as soon as they appear in the Red Hat Satellite web interface. No packages are necessary for registration, although updates cannot be retrieved from the Satellite until the channel is completely populated.
3. Repeat this step for each channel or include them all within a single command by passing each channel label preceded with an additional -c flag, like so:

   # satellite-sync -c [channel-label-1] -c [channel-label-2] --mount-point /var/rhn-sat-import
   

Procedure 8.3. Moving Exporter Content

1. Log into the machine as root.
2. Create a target directory for the files, such as:

   # mkdir /var/rhn-sat-import/
   

3. Make the export data available on the local machine in the directory created in the previous step. Either copy the data directly, or mount the data from another machine using NFS. Copy the data into the new directory with the following command:

   # scp -r root@storage.example.com:/var/rhn-sat-export/* /var/rhn-sat-import
   

1. List the channels available for import with the command:

   # satellite-sync --list-channels --mount-point /var/rhn-sat-import
   

2. Initiate the import of a specific channel using a channel label presented in the previous list. Run the following command :

   # satellite-sync --channel=[channel-label] --mount-point=/var/rhn-sat-import
   

   Note

   Importing package data can take up to two hours per channel. Register systems to channels as soon as they appear in the Red Hat Satellite web interface. No packages are necessary for registration, although updates cannot be retrieved from the Satellite until the channel is completely populated.
   Repeat this step for each channel or include them all within a single command by passing each channel label preceded by an additional --channel flag:

   # satellite-sync --channel=channel-label-1 -c channel-label-2 --mount-point=/var/rhn-sat-import
   

3. The population of channels executes until completion. Verify all of the packages are moved out of the repository with the following command:

   # cd /var/rhn-sat-import/; ls -alR | grep rpm
   

   If all RPMs are installed and moved to their permanent locations, the count appears as zero. If so, remove the temporary /var/rhn-sat-import/ repository.

   # rm -rf /var/rhn-sat-import
   

Procedure 9.1. Configuring the Master Satellite Server

1. On the Web Interface:
   1. Log in as the Satellite Administrator.
   2. Click Admin → ISS Configuration → Master Setup.
   3. On the top right-hand corner, click Add New Slave.
   4. Fill in the following information:
      • Slave Fully Qualified Domain Name (FQDN)
      • Allow Slave to Sync? - Choosing this field will allow the Slave Satellite to access this Master Satellite. Otherwise, contact with this Slave will be denied.
      • Sync all orgs to Slave? - Checking this field will synchronize all organizations to the Slave Satellite.

      Note

      Choosing the Sync All Orgs to Slave? option on the Master Setup page will override any specifically selected organizations in the Local Organization table below.
   5. Click Create.
   6. (Optional) Click on any local organization to be exported to the Slave Satellite.
   7. Click Allow Orgs.

      Note

      In Satellite 5.5 and previous versions, the Master Satellite used the iss_slaves parameter in the /etc/rhn/rhn.conf file to identify which slaves could contact the Master Satellite. Satellite 5.6 and later uses the information in the Master Setup page to determine this information.
2. On the Command Line:
   1. Enable the inter-satellite synchronization (ISS) feature in the /etc/rhn/rhn.conf file:

      disable_iss=0
      

   2. Save the configuration file, and restart the httpd service:

      service httpd restart
      

Procedure 9.2. Configuring Slave Servers

1. In order to securely transfer content to the slave servers, the ORG-SSL certificate from the master server is needed. The certificate can be downloaded over HTTP from the /pub/ directory of any satellite. The file is called RHN-ORG-TRUSTED-SSL-CERT, but can be renamed and placed anywhere in the local filesystem of the slave, such as the /usr/share/rhn/ directory.
2. Log in to the Slave Satellite as the Satellite Administrator.
3. Click Admin → ISS Configuration → Slave Setup.
4. On the top right-hand corner, click Add New Master.
5. Fill in the following information:
   • Master Fully-Qualified Domain Name
   • Default Master?
   • Filename of this Master's CA Certificate - Use the full path of the CA Certificate downloaded in the initial step of this procedure.
6. Click Add New Master.

Procedure 9.3. Performing an Inter-Satellite Synchronization

• Begin the synchronization by running the satellite-sync command:

  satellite-sync -c your-channel

  Note

  Command line options that are manually provided with the satellite-sync command will override any custom settings in the /etc/rhn/rhn.conf file.

Procedure 9.4. Mapping the Master Satellite's Exported Organizations to the Slave Satellite's Organizations

1. Log in as the Satellite Administrator.
2. Click on Admin → ISS Configuration → Slave Setup.
3. Select a Master Satellite by clicking on it's name.
4. Use the drop-down box to map the exported master organization name to a matching local organization in the Slave Satellite.
5. Click Update Mapping.
6. On the command line, issue the satellite-sync on each of the custom channels to obtain the correct trust structure and channel permissions:

   satellite-sync -c your-channel
   

Procedure 9.5. Configuring the Master Satellite Server

1. Enable the inter-satellite synchronization (ISS) feature in the /etc/rhn/rhn.conf file:

   disable_iss=0
   

2. Save the configuration file, and restart the httpd service:

   service httpd restart
   

Procedure 9.6. Configuring Slave Servers

1. In order to securely transfer content to the slave servers, the ORG-SSL certificate from the master server is needed. The certificate can be downloaded over HTTP from the /pub/ directory of any satellite. The file is called RHN-ORG-TRUSTED-SSL-CERT, but can be renamed and placed anywhere in the local filesystem of the slave, such as the /usr/share/rhn/ directory.
2. Log in to the Slave Satellite as the Satellite Administrator.
3. Click Admin → ISS Configuration → Slave Setup.
4. On the top right-hand corner, click Add New Master.
5. Fill in the following information:
   • Master Fully-Qualified Domain Name
   • Default Master?
   • Filename of this Master's CA Certificate - Use the full path of the CA Certificate downloaded in the initial step of this procedure.
6. Click Add New Master.

Procedure 9.7. Mapping Master Satellite Organizations to Slave Satellite Organizations with spacewalk-sync-setup

1. Log in to a system. It does not matter if it is a Master Satellite, a Slave Satellite or a different system altogether, as long as the system can access the public XMLRPC API of the Master and Slave Satellites.
2. Issue the spacewalk-sync-setup on a command line interface:

   spacewalk-sync-setup --ms=[Master_FQDN] \
   --ml=[Master_Sat_Admin_login] \
   --mp=[Master_Sat_Admin_password] \
   --ss=[Slave FQDN]  --sl=[Slave_Sat_Admin_login] \
   --sp=[Slave_Sat_Admin_password> \
   --create-templates --apply
   

   Where:
   • --ms=MASTER, --master-server=MASTER is the FQDN of the Master to connect to
   • --ml=MASTER_LOGIN, --master-login=MASTER_LOGIN is the Satellite Administrator login for the Master Satellite
   • --mp=MASTER_PASSWORD, --master-password=MASTER_PASSWORD is the password for the Satellite Administrator login on the Master Satellite
   • --ss=SLAVE, --slave-server=SLAVE is the FQDN of the Slave Satellite to connect to.
   • --sl=SLAVE_LOGIN, --slave-login=SLAVE_LOGIN is the Satellite Administrator login for the Slave Satellite
   • --sp=SLAVE_PASSWORD, --slave-password=SLAVE_PASSWORD is the password for the Satellite Administrator login on the Slave Satellite
   • --ct, --create-templates is the option that creates both a master and a slave setup file for the master/slave pair we've pointed at
   • --apply tells the Satellite instances to make the changes specified by the setup files to the specified Satellite instances

   Note

   For more setup options:

   spacewalk-sync-setup --help
   

   The output from this command will be as follows:

   INFO: Connecting to [admin@master-fqdn]
   INFO: Connecting to [admin@slave-fqdn]
   INFO: Generating master-setup file $HOME/.spacewalk-sync-setup/master.txt
   INFO: Generating slave-setup file $HOME/.spacewalk-sync-setup/slave.txt
   INFO: Applying master-setup $HOME/.spacewalk-sync-setup/master.txt
   INFO: Applying slave-setup $HOME/.spacewalk-sync-setup/slave.txt
   

3. On the command line, issue the satellite-sync command on each of the custom channels to obtain the correct trust structure and channel permissions:

   satellite-sync -c your-channel
   

Procedure 10.1. Confirm Database Disk Space

1. Calculate the disk space occupied by the embedded database.
   1. For Satellite 5.6
      The embedded database is stored in directory /var/lib/pgsql. After the upgrade, the embedded database will be stored in directory /var/opt/rh/rh-postgresql95/lib/pgsql.

      # du --summarize -h /var/lib/pgsql
      

      Example output of the du command.

      81M	/var/lib/pgsql
      

   2. For Satellite 5.7
      The embedded database is stored in directory /opt/rh/postgresql92/root/var/lib/pgsql. After the upgrade, the embedded database will be stored in directory /var/opt/rh/rh-postgresql95/lib/pgsql.

      # du --summarize -h /opt/rh/postgresql92/root/var/lib/pgsql
      

      Example output of the du command.

      81M	/opt/rh/postgresql92/root/var/lib/pgsql
      

2. Confirm the available disk space in the embedded database's location for Satellite 5.8.

   # df -h /var
   

   Example output of the df command.

   Filesystem    Size  Used Avail Use% Mounted on
   /dev/mapper/vg_testhost01-lv_root
                 50G  3.4G   44G   8% /
   

3. Compare the disk space occupied by the embedded database and the available disk space. If the available disk space is less than the total disk space occupied by the embedded database, do not proceed until this has been corrected.

Procedure 10.2. Download a Satellite 5.8 Manifest

1. Log on to the Customer Portal and click Subscriptions.
2. Click Satellite Organizations.
3. Click Satellite.
4. Click the name of the Satellite instance to be upgraded.
5. Select Satellite 5.8 from the Version: drop-down list, and click Update.
6. Click Download manifest and save the manifest file.
7. Copy the manifest file to the Satellite 5 host which is being upgraded.

   # scp manifest_file.zip root@satellite.example.com:/root
   

Procedure 10.3. Download the Installation Media

1. Log on to the Customer Portal.
2. Click Downloads.
3. Click Red Hat Satellite.
4. Select 5.8 for RHEL 6 from the Versions drop-down list.
5. Select x86_64 or s390x from the Architecture list.
6. Download the Red Hat Satellite 5.8 Binary DVD.
7. Depending on your upgrade requirements, either burn the DVD ISO image to DVD media, or copy it to the host on which Red Hat Satellite will be installed.
   Run the following command on the host containing the DVD ISO image to copy it to the Satellite host. In this example, the ISO image is copied to the directory /root.

   # scp satellite.iso root@satellite.example.com:/root
   

   If you will be upgrading Red Hat Satellite from a DVD, burn the download ISO image to a writeable DVD.

Procedure 10.4. Mounting from a disc

1. Log into the machine as root.
2. Insert the Red Hat Satellite Server CD or DVD containing the installation files.
3. Red Hat Enterprise Linux might automount the disc. If so, it mounts the disc to the /media/cdrom/ directory. If Red Hat Enterprise Linux does not automount the disc, manually mount it to the /media/cdrom/ directory with the following command:

   # mkdir /media/cdrom
   # mount /dev/cdrom /media/cdrom
   

Procedure 10.5. Mounting from an ISO image

1. Log into the machine as root.
2. Download the ISO image from the Red Hat Network website.
3. Mount the ISO image to a location on your filesystem:

   # mkdir /media/cdrom
   # mount -o loop iso_filename /media/cdrom
   

Procedure 10.6. Download and Install Red Hat Satellite 5 Upgrade Package

1. Log on to the Customer Portal and click Downloads.
2. From the Product list, click Red Hat Satellite.
3. Select the Product Variant, Version and Architecture which match the current, installed instance of Satellite. For example, Red Hat Satellite, 5.6 for RHEL 6, and x86_64.
4. Click Packages and enter upgrade in the Search field.
5. Click Download Latest beside the rhn-upgrade package, and download it.
6. Copy the rhn-upgrade.rpm package to the Satellite server.
   If you have network access to the Satellite server from this computer, use the scp tool. In this example, the package is copied to the /root directory.

   # scp rhn-upgrade.rpm root@satellite.example.com:/root
   

   If you do not have network access to the Satellite server from this computer, copy the package to local media, transport the media to the Satellite server, and copy it from there.
7. On the Satellite server, navigate to the directory containing the rhn-upgrade.rpm package, and install it.

   # yum localinstall rhn-upgrade.rpm
   

Procedure 10.7. Updating User Passwords

1. Export a list of users with MD5-encrypted passwords:

   # spacewalk-report users-md5 > users-md5.csv
   

2. Change the password of each user using the following for loop:

   # for i in $(cat users-md5.csv | awk -F, 'NR>1 { print $4 }'); do
         echo "Changing password for user $i";
         satpasswd $i;
         echo;
   done
   

   Alternatively, instruct all users in the file users-md5.csv to log into Satellite's Web UI. Satellite will automatically change their passwords in the database to use SHA-256.

Procedure 10.8. Updating Client Certificates

1. Export a list of client systems using certificates using MD5-encryption:

   # spacewalk-report system-md5-certificates > system-md5-certificates.csv
   

2. Use the spacewalk-fips-tool to schedule an update of systems in an organization. You need to repeat this process for each organization in your Satellite environment. First use the following commands for organization with ID 1:

   # ORG_ID=1
   # for system in $(awk -F, "NR>1 { if (\$3 == $ORG_ID) print \$1 }" system-md5-certificates.csv); do systems="$systems $system"; done
   # spacewalk-fips-tool -i -u admin -d "2014-12-01 14:00:00" -o /tmp/scheduled-installations.csv $systems
   

   This schedules the installation of packages requires for the certificate update on December 1, 2014 at 2pm.
   Next, Either run rhn_check -v on each client or wait until osad picks up the event.
   Finally, use the spacewalk-fips-tool again to schedule an update of certificates:

   # ORG_ID=1
   # for system in $(awk -F, "NR>1 { if (\$3 == $ORG_ID) print \$1 }" system-md5-certificates.csv); do systems="$systems $system"; done
   # spacewalk-fips-tool -c -u admin -d "2014-12-01 14:00:00" -o /tmp/scheduled-installations.csv $systems
   

3. Repeat this process for each organization ID.

Procedure 12.2. Migrating to a Managed Database

1. Shut down the Red Hat Satellite instance:

   [root@satellite ~]# rhn-satellite stop
   

2. Remove the rhn-upgrade package if it exists on your server:

   [root@satellite ~]# yum remove rhn-upgrade
   

3. Use db-control to create a database backup

   [root@satellite ~]# mkdir ~/dbbackup
   [root@satellite ~]# db-control backup ~/dbbackup
   

4. Copy the database backup from the Satellite server to the Managed Database server.

   [root@satellite ~]# scp -r ~/dbbackup root@manageddb.example.com:~/.
   

5. Install the Managed Database using the Red Hat Satellite installation ISO.
6. After you have installed the Managed External Database, shut it down and back up the database configuration and access control files.

   [root@manageddb ~]# db-control stop
   [root@manageddb ~]# cp /var/opt/rh/rh-postgresql95/lib/pgsql/data/postgresql.conf ~/dbbackup
   [root@manageddb ~]# cp /var/opt/rh/rh-postgresql95/lib/pgsql/data/pg_hba.conf ~/dbbackup
   

   You need to backup these files because the migration process will erase them.
7. Use db-control to restore the database backup to the Managed Database server.

   [root@manageddb ~]# db-control restore ~/dbbackup
   

8. Restore the database configuration and access control files from backup to the Managed Database.

   [root@manageddb ~]# cp ~/dbbackup/postgresql.conf /var/opt/rh/rh-postgresql95/lib/pgsql/data/postgresql.conf
   [root@manageddb ~]# cp ~/dbbackup/pg_hba.conf /var/opt/rh/rh-postgresql95/lib/pgsql/data/pg_hba.conf
   

9. On the Satellite server, edit the /etc/rhn/rhn.conf file and change db_host to the domain name of the Managed Database and set the db_port to 5432. For example:

   db_host = manageddb.example.com
   db_port = 5432
   

10. Remove rh-postgresql95-postgresql from the /etc/rhn/service-list file on the Satellite server.

    [root@satellite ~]# sed -i 's/rh-postgresql95-postgresql //g' /etc/rhn/service-list
    

11. On the Managed Database, edit the /etc/rhn/rhn.conf file and change db_name, db_user, db_password to reflect the same values in /etc/rhn/rhn.conf on the Satellite server. For example:

    db_name = mydb
    db_user = mydbuser
    db_password = mydbpassword
    

12. Start the Managed Database instance using db-control.

    [root@manageddb ~]# db-control start
    

13. Remove the PostgreSQL and spacewalk-dobby packages from the Satellite server.

    [root@satellite ~]# yum remove rh-postgresql95 rh-postgresql95-postgresql rh-postgresql95-postgresql-contrib rh-postgresql95-postgresql-libs rh-postgresql95-postgresql-server rh-postgresql95-postgresql-pltcl spacewalk-dobby
    

14. Restart Red Hat Satellite.

    [root@satellite ~]# rhn-satellite start
    

Procedure 12.3. Migrating to an External PostgreSQL Database

1. Shut down all services on the Red Hat Satellite server, but start the Embedded Database with db-control:

   [root@satellite ~]# rhn-satellite stop
   [root@satellite ~]# db-control start
   

2. Remove the rhn-upgrade if it exists on your server:

   [root@satellite ~]# yum remove rhn-upgrade
   

3. Update your database to the latest schema version:

   [root@satellite ~]# yum update satellite-schema
   [root@satellite ~]# spacewalk-schema-upgrade
   

   This ensures that your database version matches the latest version on the External PostgreSQL Database.
4. Create a directory to hold your database snapshot.

   [root@satellite ~]# mkdir ~/dbbackup
   [root@satellite ~]# cd ~/dbbackup
   

5. Export the database using spacewalk-dump-schema:

   [root@satellite dbbackup]# spacewalk-dump-schema --to=postgresql > migrate-to-postgresql.sql
   

6. Stop the Embedded Database:

   [root@satellite dbbackup]# db-control stop
   

7. Use spacewalk-setup to populate the External PostgreSQL Database:

   [root@satellite dbbackup]# spacewalk-setup --db-only --external-postgresql
   

   The script asks for your database details so Satellite can connect and populate the database. Enter your External PostgreSQL Database details:

   ** Database: Setting up database connection for PostgreSQL backend.
   Hostname (leave empty for local)? postgresql.example.com
   Port [5432]?
   Database? myextdb
   Username? root
   Password?
   

   The script populates the database.
8. When the script completes database population, restore the database schema

   [root@satellite dbbackup]# spacewalk-sql -i < migrate-to-postgresql.sql
   

9. Remove the PostgreSQL and spacewalk-dobby packages from the Satellite server.

   [root@satellite ~]# yum remove rh-postgresql95 rh-postgresql95-postgresql rh-postgresql95-postgresql-contrib rh-postgresql95-postgresql-libs rh-postgresql95-postgresql-server rh-postgresql95-postgresql-pltcl spacewalk-dobby
   

10. Start Red Hat Satellite.

    [root@satellite ~]# rhn-satellite start
    

Procedure 12.4. Migrating to an External Oracle Database

1. Shut down all services on the Red Hat Satellite server, but start the Embedded Database with db-control:

   [root@satellite ~]# rhn-satellite stop
   [root@satellite ~]# db-control start
   

2. Remove the rhn-upgrade package if it exists on your server:

   [root@satellite ~]# yum remove rhn-upgrade
   

3. Update your database to the latest schema version:

   [root@satellite ~]# yum update satellite-schema
   [root@satellite ~]# spacewalk-schema-upgrade
   

   This ensures that your database version matches the latest version on the External Oracle Database.
4. Create a directory to hold your database snapshot.

   [root@satellite ~]# mkdir ~/dbbackup
   [root@satellite ~]# cd ~/dbbackup
   

5. Export the database using spacewalk-dump-schema:

   [root@satellite dbbackup]# spacewalk-dump-schema --to=oracle > migrate-to-oracle.sql
   

6. Stop the Embedded Database:

   [root@satellite dbbackup]# db-control stop
   

7. Exchange the PostgreSQL drivers and configuration scripts with the Oracle drivers and configuration scripts on the Satellite server:

   [root@satellite dbbackup]# yum remove -y spacewalk-postgresql
   [root@satellite dbbackup]# yum install -y spacewalk-oracle
   [root@satellite dbbackup]# yum remove -y spacewalk-java-postgresql spacewalk-backend-sql-postgresql
   

8. Use spacewalk-setup to populate the External Oracle Database:

   [root@satellite dbbackup]# spacewalk-setup --db-only --external-oracle
   

   The script asks for your database details so Satellite can connect and populate the database. Enter your External Oracle Database details:

   ** Database: Setting up database connection for Oracle backend.
   Database service name (SID)? oracledb
   Database hostname [localhost]? oracledb.example.com
   Database (listener) port [1521]?
   

   The script populates the database.

   Important

   Use the default Oracle Database port (1521) for the Red Hat Satellite database. Using an alternative port can cause SELinux errors.
9. When the script completes database population, restore the database schema

   [root@satellite dbbackup]# spacewalk-sql -i < migrate-to-oracle.sql
   

   Important

   You might need to change SELinux context of the migration script before loading it into Oracle Database:

   [root@satellite dbbackup]# semanage fcontext -a -t oracle_sqlplus_exec_t /root/dbbackup/migrate-to-oracle.sql
   [root@satellite dbbackup]# restorecon -v /root/dbbackup/migrate-to-oracle.sql
   

   Similarly, you might need to change SELinux context of dumped tables:

   [root@satellite dbbackup]# semanage fcontext -a -t oracle_tmp_t "/tmp/dumped-tables(/.*)?"
   [root@satellite dbbackup]# restorecon -R -v /tmp/dumped-tables/
   

10. Remove the PostgreSQL and spacewalk-dobby packages from the Satellite server.

    [root@satellite ~]# yum remove rh-postgresql95 rh-postgresql95-postgresql rh-postgresql95-postgresql-contrib rh-postgresql95-postgresql-libs rh-postgresql95-postgresql-server rh-postgresql95-postgresql-pltcl spacewalk-dobby
    

11. Start Red Hat Satellite.

    [root@satellite ~]# rhn-satellite start
    

Procedure 12.5. Migrating to an Embedded Database

1. Stop the main services on the Satellite server.

   [root@satellite ~]# rhn-satellite stop
   

2. Shut down the database on the Managed Database server.

   [root@manageddb ~]# db-control stop
   

3. Remove the rhn-upgrade package if it exists on your server:

   [root@satellite ~]# yum remove rhn-upgrade
   

4. Use db-control to create a database backup on the Managed Database Server and copy that backup to the Satellite server.

   [root@manageddb ~]# mkdir ~/dbbackup
   [root@manageddb ~]# db-control backup ~/dbbackup
   [root@manageddb ~]# scp -r ~/dbbackup root@satellite.example.com:~/.
   

   The Managed Database server is now free for other purposes. All further actions take place on the Satellite server.
5. Mount the Red Hat Satellite installation ISO on the Satellite server and set and export the YUM0 variable with the Red Hat Satellite mount point value.

   [root@satellite ~]# mkdir /media/cdrom
   [root@satellite ~]# mount -o loop Red_Hat_Satellite_58.iso /media/cdrom
   [root@satellite ~]# export YUM0=/media/cdrom
   

6. Enable the red-hat-satellite repository. If the red-hat-satellite repository definition is not present, install the satellite-repo package found in $YUM0/Satellite. After the red-hat-satellite repository is enabled, install the @satellite-database package group and disable the red-hat-satellite repository.

   [root@satellite ~]# yum install @satellite-database --enablerepo=red-hat-satellite
   

7. Use db-control to restore the database backup.

   [root@satellite ~]# db-control restore ~/dbbackup
   

8. Edit the /etc/rhn/rhn.conf file to remove the db_port and db_hostname values.

   [root@satellite ~]# sed -i 's/db_host\s*=.*/db_host = /' /etc/rhn/rhn.conf
   [root@satellite ~]# sed -i 's/db_port\s*=.*/db_port = /' /etc/rhn/rhn.conf
   

9. Add the rh-postgresql95-postgresql service to the /etc/rhn/service-list file to ensure that it is started and stopped in parallel with Red Hat Satellite.

   [root@satellite ~]# echo "SERVICES=\"rh-postgresql95-postgresql \$SERVICES\"" >> /etc/rhn/service-list
   

10. Start the Red Hat Satellite services.

    [root@satellite ~]# rhn-satellite start
    

Procedure 12.6. Migrating to an Embedded Database from an External PostgreSQL Database

1. Shut down all services on the Red Hat Satellite server:

   [root@satellite ~]# rhn-satellite stop
   

2. Make sure your External PostgreSQL Database is still running.
3. Remove the rhn-upgrade if it exists on your server:

   [root@satellite ~]# yum remove rhn-upgrade
   

4. Update the External PostgreSQL Database to the latest schema version:

   [root@satellite ~]# yum update satellite-schema
   [root@satellite ~]# spacewalk-schema-upgrade
   

   This ensures that your database version matches the latest version for the Embedded Database.
5. Create a directory to hold your database snapshot.

   [root@satellite ~]# mkdir ~/dbbackup
   [root@satellite ~]# cd ~/dbbackup
   

6. Export the database using spacewalk-dump-schema:

   [root@satellite dbbackup]# spacewalk-dump-schema --to=postgresql > migrate-to-postgresql.sql
   

7. Stop the External Database. It is no longer required.
8. Install the PostgreSQL installation and Satellite database tools packages on the Satellite server:

   [root@satellite dbbackup]# yum install -y spacewalk-setup-postgresql spacewalk-dobby
   

9. Use spacewalk-setup to populate the Embedded Database:

   [root@satellite dbbackup]# spacewalk-setup --db-only
   

   The script populates the database. Wait until this process completes.

   ** Database: Setting up database connection for PostgreSQL backend.
   ** Database: Installing the database:
   ** Database: This is a long process that is logged in:
   ** Database:   /var/log/rhn/install_db.log
   *** Progress: #
   ** Database: Installation complete.
   ** Database: Populating database.
   *** Progress: ####################################
   

10. When the script completes database population, restore the database schema:

    [root@satellite dbbackup]# spacewalk-sql -i < migrate-to-postgresql.sql
    

11. Start Red Hat Satellite.

    [root@satellite ~]# rhn-satellite start
    

Procedure 12.7. Migrating to an Embedded Database from Oracle Database

1. Shut down all services on the Red Hat Satellite server:

   [root@satellite ~]# rhn-satellite stop
   

2. Make sure your External Oracle Database is still running.
3. Remove the rhn-upgrade if it exists on your server:

   [root@satellite ~]# yum remove rhn-upgrade
   

4. Update the External Oracle Database to the latest schema version:

   [root@satellite ~]# yum update satellite-schema
   [root@satellite ~]# spacewalk-schema-upgrade
   

   This ensures that your database version matches the latest version for the Embedded Database.
5. Create a directory to hold your database snapshot.

   [root@satellite ~]# mkdir ~/dbbackup
   [root@satellite ~]# cd ~/dbbackup
   

6. Export the database using spacewalk-dump-schema:

   [root@satellite dbbackup]# spacewalk-dump-schema --to=postgresql > migrate-to-postgresql.sql
   

7. Stop the External Oracle Database. It is no longer required.
8. Exchange the Oracle drivers and configuration scripts with the PostgreSQL drivers and configuration scripts on the Satellite server:

   [root@satellite dbbackup]# yum remove -y spacewalk-oracle
   [root@satellite dbbackup]# yum install -y spacewalk-postgresql spacewalk-setup-postgresql spacewalk-dobby
   [root@satellite dbbackup]# yum remove -y spacewalk-java-oracle spacewalk-backend-sql-oracle
   

9. Use spacewalk-setup to populate the Embedded Database:

   [root@satellite dbbackup]# spacewalk-setup --db-only
   

   The script populates the database. Wait until this process completes.

   ** Database: Setting up database connection for PostgreSQL backend.
   ** Database: Installing the database:
   ** Database: This is a long process that is logged in:
   ** Database:   /var/log/rhn/install_db.log
   *** Progress: #
   ** Database: Installation complete.
   ** Database: Populating database.
   *** Progress: ####################################
   

10. When the script completes database population, restore the database schema

    [root@satellite dbbackup]# spacewalk-sql -i < migrate-to-postgresql.sql
    

11. Start Red Hat Satellite.

    [root@satellite ~]# rhn-satellite start
    

Procedure 12.8. Migrating to an External Database from Oracle Database

1. Shut down all services on the Red Hat Satellite server:

   [root@satellite ~]# rhn-satellite stop
   

2. Make sure your External Oracle Database is still running.
3. Remove the rhn-upgrade if it exists on your server:

   [root@satellite ~]# yum remove rhn-upgrade
   

4. Update the External Oracle Database to the latest schema version:

   [root@satellite ~]# yum update satellite-schema
   [root@satellite ~]# spacewalk-schema-upgrade
   

   This ensures that your database version matches the latest version for the External Database.
5. Create a directory to hold your database snapshot.

   [root@satellite ~]# mkdir ~/dbbackup
   [root@satellite ~]# cd ~/dbbackup
   

6. Export the database using spacewalk-dump-schema:

   [root@satellite dbbackup]# spacewalk-dump-schema --to=postgresql > migrate-to-postgresql.sql
   

7. Stop the External Oracle Database. It is no longer required.
8. Exchange the Oracle drivers and configuration scripts with the PostgreSQL drivers and configuration scripts on the Satellite server:

   [root@satellite dbbackup]# yum remove -y spacewalk-oracle
   [root@satellite dbbackup]# yum install -y spacewalk-postgresql
   [root@satellite dbbackup]# yum remove -y spacewalk-java-oracle spacewalk-backend-sql-oracle
   

9. Use spacewalk-setup to populate the External Database:

   [root@satellite dbbackup]# spacewalk-setup --db-only --external-postgresql
   

   The script asks for your database details so Satellite can connect and populate the database. Enter your External PostgreSQL Database details:

   ** Database: Setting up database connection for PostgreSQL backend.
   Hostname (leave empty for local)? postgresql.example.com
   Port [5432]?
   Database? myextdb
   Username? root
   Password?
   

10. When the script completes database population, restore the database schema

    [root@satellite dbbackup]# spacewalk-sql -i < migrate-to-postgresql.sql
    

11. Start Red Hat Satellite.

    [root@satellite ~]# rhn-satellite start