Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionDirect Docs Feedback
2023-01-28 21:06:33 UTC
This guide could really benefit from a section about exclusions. There are many different kinds of data sources that ReAR can exclude, but the software itself doesn't provide much help in understanding how to do this. Administrators need to know how to exclude devices, partitions, RAID arrays, executables, files, and entire file systems from being included in the backup, overwritten on recovery, or both. It would be really helpful to know what ReAR excludes by default, but its own default config file, while highly organized, is extremely dense and lacking in quality examples. It doesn't seem possible to accurately verify that an exclusion was done correctly without taking the time to destroy and recover a test system. We would all save a lot of time if quality information was available to start with.
Reported by: lawrence.miller
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/ch-relax-and-recover_rear#annotations:35aeac68-cf1f-4c10-adff-cb095d826349
Dear Mr. Miller!
Thank you for your request for additional documentation. We appreciate your feedback and are committed to continuously improving our product documentation.
I have consulted with our subject matter expert, who will be responsible for preparing and testing the cases that need to be documented. After that, I will begin writing the documentation that will be applicable for RHEL 7, RHEL 8, and RHEL 9.
Based on our current workload, we estimate that it will take approximately 2 months to complete this request. However, we will do our best to complete it as soon as possible and will keep you updated on our progress.
Thank you for your patience and understanding.
Best regards,
Sarka Jana
Comment 17RHEL Program Management
2023-09-14 13:50:37 UTC
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 18RHEL Program Management
2023-09-14 13:52:09 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.
Due to differences in account names between systems, some fields were not replicated. Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.
To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer. You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:
"Bugzilla Bug" = 1234567
In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 19Red Hat Bugzilla
2024-01-26 04:25:14 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days