This document provides step-by-step testing instructions for the --tar-volume-size feature added to the backup command.
The --tar-volume-size parameter splits Pulp content backups into multiple volumes of a specified size, useful for systems with limited disk space or for splitting backups across multiple media.
This documents how to do live development on the smart_proxy_container_gateway
plugin against a foremanctl-deployed foreman-proxy container.
A systemd drop-in config volume-mounts your local git checkout of the plugin's
lib/ directory over the RPM-installed gem inside the container. Edits to local
files take effect on the next container restart — no image rebuild needed.
| [root@ip-10-0-168-10 backup]# cat /tmp/backup/foreman-proxy-restore.patch | |
| From: Claude Code | |
| Date: Thu, 25 Jun 2026 | |
| Subject: [PATCH] Fix restore for foreman-proxy installations | |
| Make foreman database restoration and deployment conditional based on | |
| installation flavor to support foreman-proxy systems that don't have | |
| the foreman database or full foreman services. | |
| Changes: |
| #!/bin/bash | |
| # | |
| # test-restore-final.sh - Same-box restore testing for foremanctl backup | |
| # | |
| # Usage: ./test-restore-final.sh /path/to/backup/foreman-backup-TIMESTAMP | |
| # | |
| # This script performs a DESTRUCTIVE restore on the same box: | |
| # - Drops and recreates all databases | |
| # - Restores database dumps | |
| # - Fixes database ownership and permissions |
Date: 2026-05-12
Branch: backup-offline-implementation
Repository: https://github.com/sjha4/foremanctl
Target Audience: foreman-maintain team for evaluation
This guide provides a complete step-by-step process to restore a Foreman/Katello deployment from a foremanctl backup. The backup includes all critical components needed for a full restoration.
Estimated Restore Time: 30-60 minutes (depending on volume data size) Complexity Level: MEDIUM Risk Level: Requires service downtime