Consolidated Troubleshooting Article for Red Hat Satellite 6.x backup-related Issues
Updated
Backup Issues
- Offline backup on Red Hat Satellite 6 fails with: Hammer configuration failed: Incorrect credential for admin user
- Incremental backup fails with an error message ''Provide a valid previous backup directory'' on Red Hat Satellite 6
- The Satellite snapshot/backup generates broken archives of pgsql_data.tar.gz which cannot be restored successfully
- [Satellite 6.x] 'WARNING: Snapshot rootvg-pgsql--snap changed state to: Invalid and should be removed.' warning during Satellite backup
- Red Hat Satellite backup fails with an error 'Postgres user needs write access to the backup directory'
- [Satellite6] Satellite services are not restarted after the backup
- satellite-maintain snapshot backup do not restore the Red Hat Satellite services if it fails.
- [Satellite 6] Satellite services unavailable after a failed offline backup
- Why Satellite services remain stopped after a failed offline backup?
- Red Hat Satellite 6.12+ backup does not include the files under /etc/ansible on the Satellite server
Restore Issues
- Restoring Red Hat Satellite 6.16 or 6.17 fails complaining about db duplicates on CREATE UNIQUE INDEX
- Restroring from full offline Satellite backup fails with
pg_restore: error: could not uncompress data: (null)error on Red Hat Satellite 6.16 server - Restoring backup of Red Hat Satellite server on a target Satellite server fails with an error could not connect to database template1.
- [Satellite] Restoring satellite backup from RHEL7/Sat6.11 to RHEL8/Sat6.11 failed in configuring qpid, puppetserver and foreman smartproxy services
- satellite-maintain restore fails with '/usr/share/foreman-installer/modules/foreman_proxy/manifests/plugin/remote_execution/ssh.pp' is available
How To
- How to backup and restore a Red Hat Satellite 6 system?
- How to take a backup of the Red Hat Satellite 6 server without packages?
Q & A
SBR
Product(s)
Article Type