Hide Forgot
It was discovered that missing tables in the storage restore procedure were preventing all relevant data from being correctly restored. Improvements to the procedure in https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.3/html/Admin_and_Config/storage-restore.html now include all affected tables, and fixes the originally-reported issue.
[Admin_Config] Ready for review.
Description of problem: The restore procedure documentation is explaining only for "metrics_index" table[1]. However, the procedure is necessary for other tables[2] as well. [1] https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.2/html/Admin_and_Config/storage-restore.html [2] - rhq-data/data/rhq/metrics_index - rhq-data/data/rhq/one_hour_metrics - rhq-data/data/rhq/raw_metrics - rhq-data/data/rhq/schema_version - rhq-data/data/rhq/six_hour_metrics - rhq-data/data/rhq/twenty_four_hour_metrics Version-Release number of selected component (if applicable): JON 3.2
svn commit -m "tabl" Sending en-US/Admin_and_Config.xml Sending en-US/MetricsDB.xml Transmitting file data .. Committed revision 98007. In Step 3, I noted that in the original 3.2 docs, there was a rhq-data/data/data/ path that just didn't look correct. I've removed this, but if it is required, then I can add it back again. In Step 4, I left the user in the rhq directory because this is where they would be if they followed the procedure to date. I assumed that by now the customer would understand the directory pattern and could substitute paths as required in the procedure. http://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Operations_Network/3.3/html/Admin_and_Config/storage-restore.html will show the changes once published.
*** Bug 1136816 has been marked as a duplicate of this bug. ***