Description of problem:
katello-service, katello-backup, and katello-restore functionality is going to be in foreman-maintain in 6.4. The original katello-* and satellite-* scripts will still live in 6.4, but we should deprecate them and remove them in 6.5 since they will be removed upstream.
Version-Release number of selected component (if applicable):
After a off-thread discussion, we have decided to remove the original katello-backup/restore scripts in 6.4 and deprecate them in 6.3.
Brad, can you update the flags for 6.3?
this would be 6.3.z only with a DEPRECATION WARNING in the output of katello-backup/restore but have zero effect on the actual functionality of the 2 tools.
Verified in Satellite 6.3.4 Snap 2
-bash-4.2# satellite-backup --help
DEPRECATION WARNING: satellite-backup and katello-backup will be removed in Satellite 6.4, where they will be replaced by foreman-maintain
Usage: satellite-backup /path/to/dir [options]
eg: $ satellite-backup /tmp/satellite-backup
--skip-pulp-content Create backup without Pulp content for debugging only
Backup changes since previous backup
--online-backup Keep services online during backup
--logical-db-backup Also dump full database schema during offline backup
--snapshot Use snapshots of the databases to create backup
Override default directory (/var/snap/) where the snapshots will be mounted
Override default block size (2G)
--features FEATURES Capsule features to include in the backup, please specify a list with commas. Valid features are tftp, dns, dhcp, openscap, and all.
--preserve-directory Do not create a time-stamped subdirectory
-y, --assumeyes Bypass interaction by answering yes
-bash-4.2# satellite-restore --help
DEPRECATION WARNING: satellite-restore and katello-restore will be removed in Satellite 6.4, where they will be replaced by foreman-maintain
Usage: satellite-restore /path/to/dir [options]
eg: $ satellite-restore /tmp/backup/satellite-backup-20171002150106
-i, --incremental Restore an incremental backup
-y, --assumeyes Answer yes for all questions
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.