Right now the only documented advice (that I know of, at least) on how to back up Pulp comes from the Katello/Foreman docs* and basically entails creating a big tarball nightly which is slow, inefficient, and unrealistic IMO.
To address this for my infrastructure, I've been working on a script that does a hot mongo backup and uses LVM snapshots that are later hoovered up by our enterprise backup system. My method results in very little downtime but I'm still working through a couple finicky things. I'd like to generalize the script for public consumption but due to where I work the release review process to publish "code" (har har) is pretty arduous. I'm at the outset of the process now but I don't have an ETA for being able to release. Because of the challenges I have ahead w/r/t releasing my script, I wanted to check in with the rest of the community and see if anyone else has the same intentions - perhaps even someone who codes at a 5th grade level and could blow my work out of the water ;) I'm going to keep plodding along with the release review process with the intention of getting my script accepted into the Pulp project "/playpen" area, but I'd love to see what other folks are doing, and if there are more elegant solutions that could be contributed which could replace what I'm working on, all the better. * https://fedorahosted.org/katello/wiki/GuideServerBackups - Kodiak
_______________________________________________ Pulp-list mailing list Pulp-list@redhat.com https://www.redhat.com/mailman/listinfo/pulp-list