Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1515377 - [RFE] Allow the usage of "--skip-pulp-content" for the backup to be use by satellite-clone and provide manual steps to sync the pulp data
Summary: [RFE] Allow the usage of "--skip-pulp-content" for the backup to be use by sa...
Status: NEW
Alias: None
Product: Red Hat Satellite 6
Classification: Red Hat
Component: Satellite Clone
Version: 6.2.12
Hardware: All
OS: Linux
medium vote
Target Milestone: Unspecified
Assignee: John Mitsch
QA Contact: Lucie Vrtelova
Depends On:
TreeView+ depends on / blocked
Reported: 2017-11-20 17:30 UTC by Christian Marineau
Modified: 2019-04-15 03:41 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description Christian Marineau 2017-11-20 17:30:03 UTC
Description of problem:
The actual satellite-clone tool is expecting that the pulp file system (/var/lib/pulp/ /var/www/pub/) is provided by the katello-backup.

However, in some cases we can have hundreds gigabyte to terabytes under pulp filesystem.

- Requires the customer to have a very large filesystem available for the full backup on the source Satellite
- Requires a lot of time to backup/compress
- Requires a lot of time to transfer the backup
- Requires the target Satellite to have a temporary filesystem available for the backup
- Requires a lot of time to restore on the target Satellite

Version-Release number of selected component (if applicable):
6.2 / 6.3

Expected results:
- We should allow the usage of "--skip-pulp-content" when taking the original backup on the source Satellite.
- We should also provide detailed steps on how to manually transfer/copy the pulp directory once a Satellite server has been cloned. By example, with a rsync. Also, in some cases if the disk is virtual, it could be umounted and remount to the new Satellite server.

This will allow to have 1 single step of direct data transfer, instead of having multiple long step (backup, transfer, restore), and avoid to use a lot of temporary disk space.

Comment 1 John Mitsch 2017-11-28 15:18:27 UTC
+1 the functionality is all there now, it just needs better documentation

Comment 2 2018-01-16 16:46:16 UTC
upstream issue -

Note You need to log in before you can comment on or make changes to this bug.