RQM v4.0.2 What is the recommended way to back up and store historical data?
Li Chen (119●2●37●42)
| asked Aug 16 '13, 4:56 p.m.
retagged Aug 27 '13, 2:44 p.m. by Ralph Earle (257●3●9) We are using one project area for everything and therefore data (test cases, TCERs and etc.) grows very fast. A few issues are raised, 1. backup regularly so we can recover to certain point if needed. 2. cleanup so we can keep the project area smaller 3. keep artifacts for each release as is for the purpose of Audit 4. retrieve historical data. What are the recommended way in RQM to do these? How well a regular database backup works for these? What about dumping the whole project area to another project area to allow read-only access? |
One answer
Hi Li,
Some answers: 1) See https://jazz.net/wiki/bin/view/Main/JFSServerAdmin#Server_Backup_Maintenance and http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/index.jsp?re=1&topic=/com.ibm.jazz.repository.web.admin.doc/topics/t_jfs_backup.html&scope=null. 2) See http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/topic/com.ibm.rational.test.qm.doc/topics/c_deleting_artifacts.html. Although archiving test artifacts does not remove them from the repository (required for audit purposes), they are not included in most queries, etc. 3) See #2. 4) See the Trash View (see http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m3/topic/com.ibm.rational.test.qm.doc/topics/c_deleting_artifacts.html). Comments
Li Chen
commented Aug 21 '13, 3:53 p.m.
Thanks Paul, unfortunately we are using v4.0.2. I will have a look after we upgrade to V4.0.3 or 4.0.4 |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.