If I understand correctly, I think you want to have one or more yum repos managed somewhere outside of pulp that is your "backup". They contain every RPM and similar that pulp knows about. Naive question; what is it about this type of backup that is more convenient for you than just making a traditional backup of /var/lib/pulp/content/ ?
Questions aside, this is theoretically doable. You'll need to be setup for pulp's deferred content download feature, which includes deploying squid or an equivalent proxy. http://docs.pulpproject.org/user-guide/deferred-download.html You would first restore your database, and then create a repo in pulp for each of these backup repos. For each one: - set the download policy to "on_demand" - sync. This should discover that each content unit is already in the database, associate it to the repo, and populate the on_demand catalog with knowledge of its location in this giant feed - run the download_repo task with the "verify_all_units" option set to True. This will go through each file of each unit, discover it's missing, and then download it from the link that was cataloged above. --- http://docs.pulpproject.org/dev-guide/integration/rest-api/repo/sync.html#download-a-repository - delete your "backup" repos from pulp This is only possible for yum repos currently, until support for deferred download is added to other plugins. If you do go through with this as a plan, let us know how testing goes, and what tips you would have for the next person who tries it. Michael On Mon, Oct 10, 2016 at 12:03 PM, Nicolas FOURNIALS < [email protected]> wrote: > Hi, > > I was wondering if there was a way to get Pulp backups lighter, without > saving RPMs which are available elsewhere? > Actually, backup doc[1] is clear that everything in /var/lib/pulp should > be saved. But that would be very efficient if we could restore a Pulp > install by just having everything else in place (including manually > uploaded RPMs) and then launching a sync to re download every RPM coming > from a feed repo. > > My question may of course apply to other content types. > > > [1] https://docs.pulpproject.org/user-guide/server.html#backups > > _______________________________________________ > Pulp-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/pulp-list >
_______________________________________________ Pulp-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/pulp-list
