Migrating Katello server 3.3 to a new hardware

Support
,
1

Problem:
I am trying to migrate the server from my UK DC to India DC.

I am using Katello 3.3 version with CentOS 7. My pulp data size is 980GB with many repos and content views. I tried to take online backup using katello-backup script, the problem is the backup script says that the backup is success but the pulp.tar file size 8GB only.

I notice, the pulp.tar size is increased up to 900GB but suddenly it reduce and the total katello backup is 27GB only (including Mongo and PostgreSQL db).

Is there any other way to migrate the katello service to a new hardware?

Expected outcome:

Foreman and Proxy versions:

Installed Packages

candlepin-0.9.54.10-1.el7.noarch
candlepin-selinux-0.9.54.10-1.el7.noarch
foreman-1.14.3-1.el7.noarch
foreman-compute-1.14.3-1.el7.noarch
foreman-debug-1.14.3-1.el7.noarch
foreman-installer-1.14.3-1.el7.noarch
foreman-installer-katello-3.3.1.4-1.el7.noarch
foreman-postgresql-1.14.3-1.el7.noarch
foreman-proxy-1.14.3-1.el7.noarch
foreman-release-1.14.3-1.el7.noarch
foreman-release-scl-3-1.el7.noarch
foreman-selinux-1.14.3-1.el7.noarch
katello-3.3.2-1.el7.noarch
katello-certs-tools-2.4.0-1.el7.noarch
katello-client-bootstrap-1.2.2-1.el7.noarch
katello-common-3.3.2-1.el7.noarch
katello-debug-3.3.2-1.el7.noarch
katello-default-ca-1.0-1.noarch
katello-installer-base-3.3.1.4-1.el7.noarch
katello-repos-3.3.1-1.el7.noarch
katello-selinux-3.0.2-1.el7.noarch
katello-server-ca-1.0-1.noarch
katello-service-3.3.2-1.el7.noarch
pulp-client-1.0-1.noarch
pulp-docker-plugins-2.1.0-1.el7.noarch
pulp-katello-1.0.2-1.el7.noarch
pulp-puppet-plugins-2.10.3-1.el7.noarch
pulp-puppet-tools-2.10.3-1.el7.noarch
pulp-rpm-plugins-2.10.3-1.el7.noarch
pulp-selinux-2.10.3-1.el7.noarch
pulp-server-2.10.3-1.el7.noarch
python-gofer-qpid-2.7.6-1.el7.noarch
python-kombu-3.0.33-6.pulp.el7.noarch
python-pulp-common-2.10.3-1.el7.noarch
python-pulp-docker-common-2.1.0-1.el7.noarch
python-pulp-oid_validation-2.10.3-1.el7.noarch
python-pulp-puppet-common-2.10.3-1.el7.noarch
python-pulp-repoauth-2.10.3-1.el7.noarch
python-pulp-rpm-common-2.10.3-1.el7.noarch
python-pulp-streamer-2.10.3-1.el7.noarch
python2-qpid-1.37.0-4.el7.noarch
python2-qpid-proton-0.24.0-2.el7.x86_64
python2-qpid-qmf-1.38.0-2.el7.x86_64
qpid-cpp-client-1.38.0-2.el7.x86_64
qpid-cpp-client-devel-1.38.0-2.el7.x86_64
qpid-cpp-server-1.38.0-2.el7.x86_64
qpid-cpp-server-linearstore-1.38.0-2.el7.x86_64
qpid-dispatch-router-1.2.0-2.el7.x86_64
qpid-proton-c-0.24.0-2.el7.x86_64
qpid-qmf-1.38.0-2.el7.x86_64
qpid-tools-1.38.0-2.el7.noarch
rajasekar-satellite-migration.novalocal-foreman-client-1.0-1.noarch
rajasekar-satellite-migration.novalocal-foreman-proxy-1.0-1.noarch
rajasekar-satellite-migration.novalocal-foreman-proxy-client-1.0-1.noarch
rajasekar-satellite-migration.novalocal-qpid-broker-1.0-1.noarch
rajasekar-satellite-migration.novalocal-qpid-client-cert-1.0-1.noarch
rajasekar-satellite-migration.novalocal-qpid-router-client-1.0-1.noarch
rajasekar-satellite-migration.novalocal-qpid-router-server-1.0-1.noarch
rubygem-smart_proxy_pulp-1.3.0-1.el7.noarch
tfm-rubygem-activerecord-session_store-0.1.2-2.el7.noarch
tfm-rubygem-addressable-2.3.6-3.el7.noarch
tfm-rubygem-algebrick-0.7.3-4.el7.noarch
tfm-rubygem-ancestry-2.2.1-1.el7.noarch
tfm-rubygem-anemone-0.7.2-14.el7.noarch
tfm-rubygem-angular-rails-templates-0.1.2-5.el7.noarch
tfm-rubygem-apipie-bindings-0.0.18-1.el7.noarch
tfm-rubygem-apipie-params-0.0.5-1.el7.noarch
tfm-rubygem-apipie-rails-0.3.7-1.el7.noarch
tfm-rubygem-audited-4.2.0-1.el7.noarch
tfm-rubygem-audited-activerecord-4.2.0-2.el7.noarch
tfm-rubygem-awesome_print-1.7.0-1.el7.noarch
tfm-rubygem-bastion-4.2.2-1.fm1_14.el7.noarch
tfm-rubygem-bundler_ext-0.4.1-1.el7.noarch
tfm-rubygem-clamp-1.0.0-5.el7.noarch
tfm-rubygem-colorize-0.7.7-4.el7.noarch
tfm-rubygem-concurrent-ruby-edge-0.2.0-4.fm1_12.el7.noarch
tfm-rubygem-css_parser-1.3.7-1.el7.noarch
tfm-rubygem-daemons-1.2.3-3.el7.noarch
tfm-rubygem-deacon-1.0.0-1.el7.noarch
tfm-rubygem-deep_cloneable-2.2.2-1.el7.noarch
tfm-rubygem-deface-1.0.2-3.el7.noarch
tfm-rubygem-docker-api-1.28.0-2.el7.noarch
tfm-rubygem-domain_name-0.5.20160310-1.el7.noarch
tfm-rubygem-dynflow-0.8.17-1.fm1_14.el7.noarch
tfm-rubygem-excon-0.51.0-1.el7.noarch
tfm-rubygem-facter-2.4.0-3.el7.x86_64
tfm-rubygem-fast_gettext-1.1.0-1.el7.noarch
tfm-rubygem-fog-1.38.0-1.el7.noarch
tfm-rubygem-fog-aws-0.13.0-1.el7.noarch
tfm-rubygem-fog-core-1.42.0-1.el7.noarch
tfm-rubygem-fog-google-0.1.0-2.el7.noarch
tfm-rubygem-fog-json-1.0.2-4.el7.noarch
tfm-rubygem-fog-openstack-0.1.12-1.el7.noarch
tfm-rubygem-fog-rackspace-0.1.1-1.el7.noarch
tfm-rubygem-fog-vsphere-1.7.0-1.el7.noarch
tfm-rubygem-fog-xenserver-0.2.3-1.el7.noarch
tfm-rubygem-fog-xml-0.1.2-4.el7.noarch
tfm-rubygem-foreman-tasks-0.8.6-1.fm1_14.el7.noarch
tfm-rubygem-foreman-tasks-core-0.1.1-1.fm1_14.el7.noarch
tfm-rubygem-foreman_docker-3.0.0-1.fm1_13.el7.noarch
tfm-rubygem-formatador-0.2.1-9.el7.noarch
tfm-rubygem-friendly_id-5.1.0-3.el7.noarch
tfm-rubygem-gettext_i18n_rails-1.2.1-3.el7.noarch
tfm-rubygem-hammer_cli-0.8.0-1.el7.noarch
tfm-rubygem-hammer_cli_foreman-0.8.0-1.el7.noarch
tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-5.el7.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.4-2.el7.noarch
tfm-rubygem-hammer_cli_foreman_tasks-0.0.10-2.fm1_12.el7.noarch
tfm-rubygem-hammer_cli_import-0.11.3-1.el7.noarch
tfm-rubygem-hammer_cli_katello-0.3.0-1.el7.noarch
tfm-rubygem-hashie-2.0.5-4.el7.noarch
tfm-rubygem-highline-1.6.21-5.el7.noarch
tfm-rubygem-http-cookie-1.0.2-1.el7.noarch
tfm-rubygem-ipaddress-0.8.0-9.el7.noarch
tfm-rubygem-jquery-ui-rails-4.1.2-5.el7.noarch
tfm-rubygem-katello-3.3.2-1.el7.noarch
tfm-rubygem-ldap_fluff-0.4.4-1.el7.noarch
tfm-rubygem-little-plugger-1.1.3-21.el7.noarch
tfm-rubygem-locale-2.0.9-11.el7.noarch
tfm-rubygem-logging-1.8.2-4.el7.noarch
tfm-rubygem-net-ldap-0.15.0-1.el7.noarch
tfm-rubygem-net-scp-1.1.0-6.el7.noarch
tfm-rubygem-net-ssh-3.0.2-2.el7.noarch
tfm-rubygem-netrc-0.7.7-7.el7.noarch
tfm-rubygem-oauth-0.4.7-8.el7.noarch
tfm-rubygem-parse-cron-0.1.4-2.fm1_11.el7.noarch
tfm-rubygem-passenger-4.0.18-9.11.el7.x86_64
tfm-rubygem-passenger-native-4.0.18-9.11.el7.x86_64
tfm-rubygem-passenger-native-libs-4.0.18-9.11.el7.x86_64
tfm-rubygem-pg-0.15.1-3.el7.x86_64
tfm-rubygem-powerbar-1.0.17-1.el7.noarch
tfm-rubygem-qpid_messaging-0.34.1-1.el7.x86_64
tfm-rubygem-rabl-0.12.0-2.el7.noarch
tfm-rubygem-rack-jsonp-1.3.1-5.el7.noarch
tfm-rubygem-rails-i18n-4.0.9-1.el7.noarch
tfm-rubygem-rails-observers-0.1.2-7.el7.noarch
tfm-rubygem-rbvmomi-1.9.4-1.el7.noarch
tfm-rubygem-responders-2.3.0-1.el7.noarch
tfm-rubygem-rest-client-1.8.0-1.el7.noarch
tfm-rubygem-roadie-3.1.1-1.el7.noarch
tfm-rubygem-roadie-rails-1.1.1-1.el7.noarch
tfm-rubygem-robotex-1.0.0-19.el7.noarch
tfm-rubygem-ruby2ruby-2.1.3-4.el7.noarch
tfm-rubygem-ruby_parser-3.6.3-4.el7.noarch
tfm-rubygem-runcible-1.9.1-1.el7.noarch
tfm-rubygem-safemode-1.2.4-2.el7.noarch
tfm-rubygem-scoped_search-3.3.0-1.el7.noarch
tfm-rubygem-secure_headers-3.4.1-1.el7.noarch
tfm-rubygem-sequel-4.20.0-5.el7.noarch
tfm-rubygem-sexp_processor-4.4.4-3.el7.noarch
tfm-rubygem-table_print-1.5.1-6.el7.noarch
tfm-rubygem-trollop-2.1.2-1.el7.noarch
tfm-rubygem-unf-0.1.3-5.el7.noarch
tfm-rubygem-unf_ext-0.0.6-6.el7.x86_64
tfm-rubygem-useragent-0.16.8-1.el7.noarch
tfm-rubygem-validates_lengths_from_database-0.5.0-3.el7.noarch
tfm-rubygem-webpack-rails-0.9.8-1.el7.noarch
tfm-rubygem-wicked-1.1.0-4.el7.noarch
tfm-rubygem-will_paginate-3.1.5-1.el7.noarch
tfm-rubygem-x-editable-rails-1.5.5-1.el7.noarch
tfm-runtime-3.2-5.el7.x86_64

Foreman and Proxy plugin versions:

Other relevant data:
[e.g. logs from Foreman and/or the Proxy, modified templates, commands issued, etc]
(for logs, surround with three back-ticks to get proper formatting, e.g.)

logs
2

If you just want to migrate keeping this version of Foreman / Katello I would suggest to dump database and files.

I recommend an update to a later version nevertheless, 1.14. is EOL for a long time now.

3

What options are you running the backup script with? Did you see any errors?

Considering we are releasing 3.10 soon, you would have to go through quite a bit of work to get upgraded to that point from 3.3, so consider starting fresh (I know easier said than done with almost 1TB of pulp data)

As far as your options to actually backup your server - if you can’t get the pulp data to backup, you can backup skipping pulp data and then rsync the pulp data over. We do this in satellite-clone, you may find this process helpful.

1 Like
4

I agree with your statement that it would be quite a bit of work to update from 3.3. We even face some problems from 3.7 to 3.8 etc. We ended up in a fresh install with 3.9 and migrated with Hammer CLI / Python scripts and some Hammer CSV. Was not funny at all tbh.

1 Like