1、Quality Center Backup and Recovery Management GuidelineFile Name Quality Center Backup and Recovery GuidelineIntroductionCompany StarCiteAuthor SinckyDate 8/11/2009Status DraftDate Modifier Reason Chapter Description8/11/2009 Sincky First VersionSection I Quality Center Backup Strategy .31. Quality
2、Center Backup Introduction.32. Quality Center Repository Backup .33. Quality Center Database Backup .4Section II Quality Center Recovery Strategy.54. QC Database Recovery .54.1 former Database Server Recovery.54.2 New Database Server Recovery .54.3 Database Server Recovery Process .54.3.1 Recovery d
3、atabase .54.3.2 About TD login .55. QC Repository Recovery .65.1 Formal QC Server Recovery .65.2 Informal QC Server Recovery.6Section III Quality Center Upgrade Strategy.86. Quality Center Upgrade .86.1 Formal QC Server Upgrade.85.2 Informal QC Server Upgrade .8Section I Quality Center Backup Strate
4、gy1. Quality Center Backup IntroductionQuality Center Server IP: 10.200.30.117Quality Center Version: 9.2 EnterpriseQuality Center backup includes 2 sections: QC Repository backupQC Repository is a path to save the entire of resource and data about QC site administration and projects. One of QC site
5、 administration parameter “BASE_REPOSITORY_PATH” means the path of it. StarCite QC Repository path is:C:Program Files (x86)MercuryQuality Centerrepository There are 2 folders in this path: QC: it is Projects repository, we need to backup the necessary projects data SA: it is Site Administration repo
6、sitory, we need to backup the whole of it QC Database backupStarCite uses Microsoft SQL Server2005 as QC database server; it is also installed on 10.200.30.117. We need to backup all of the SQL Server database data for QC server.2. Quality Center Repository BackupQC Repository backup adopts a schedu
7、led batch script to backup automatically.1. The batch script is in C:Program Files (x86)MercuryQuality Centerrepository AddQCFiles.bat; it will zip the backup contents by 7zip tool and save as another disk2. The backup content includes 3 parts, they are repositorysa folder and repositoryqcSTARCITE_3
8、 folder and repositoryqcdbcon.txt file 3. This batch script has been added to Windows schedule task, by default it will be run at 12:00 AM every Saturday automatically4. The backup destination folder is D:BackupsQCRepositoryBak3. Quality Center Database BackupQC Database backup adopts SQL Server Mai
9、ntenance Plan to backup the necessary databases automatically on 10.200.30.117. Notes, Master database is ignored here.1. The Maintenance Plan is saved in localhostManagementMaintenance Plans folder in Microsoft SQL Server Management StudioQCDBFullBackupPlanQCDBLogBackupPlan2. QCDBFullBackupPlan wil
10、l full backup database: HP_DASHBOARD_920, qcsiteadmin_db, starcite_smallmeetingsolutions, training_testtesttest_db, QualityCenter_Demo_db, training_qc_rally_test_db3. QCDBFullBackupPlan will transaction log backup database: HP_DASHBOARD_920, qcsiteadmin_db, starcite_smallmeetingsolutions, training_t
11、esttesttest_db, QualityCenter_Demo_db, training_qc_rally_test_db4. The backup destination folder is D:BackupsQCDBBak by separated database name folder 5. Database strategy is:Full backup executes at 2:00 PM every Saturday, and deletes backup file 2 weeks ago automaticallyTransaction Log backup execu
12、tes it every 4 hours every day, and deletes backup file 2 weeks ago automaticallySection II Quality Center Recovery Strategy4. QC Database Recovery4.1 former Database Server RecoveryIf the former Database Server is broken:1. uninstall the former SQL Server software and all of QC databases2. reinstal
13、l SQL Server software in the former Database server machine; note the SQL Sever version is same as the former one3. restore all of QC databases according to the next stepsNothing if the former Database Server is available.4.2 New Database Server RecoveryIf want to change SQL Server to another machin
14、e:1. install SQL Server software on the new machine; note the SQL Sever version is same as the former one2. restore all of QC databases according to the next steps4.3 Database Server Recovery Process4.3.1 Recovery database1. get all of database backup files from D:BackupsQCDBBak to QC database serve
15、r, including qcsiteadmin_db and other project databases2. restore these databases from the latest full backup files by restore with nonrecovery mode with the same database name with databases original name3. restore the necessary log transaction files to these databases by restore with recovery mode
16、4. verify if there is a td user and td schema in every restored database4.3.2 About TD login1. if SQL Sever that QC will connect to is a new installation, create td login account in this SQL Sever2. set default schema to td for all of the restored database in td login properties setting3. set db_ddl
17、admin and public role membership to all of the restored database in td login properties setting4. if popup error when set role membership, execute SQL to modify SQL Sever parameter:EXEC sp_change_users_login update_one, td, td;5. QC Repository RecoveryAfter restored all of the necessary databases to
18、 SQL Sever, including qcsiteadmin_db and other project databases, we can restore QC repository. If QC server is broken, it is necessary to reinstall QC firstly. 5.1 Formal QC Server Recovery1. uninstall QC software in QC server2. invoke QC setup program and install it into the same folder with the o
19、riginal QC path3. if qcsiteadmin_db is restored or existing in QC Database server, choose upgrade existing qcsiteadmin_db schema when install QC software4. use sa login to connect SQL Server when setup QC software5. set the correct td password to qcsiteadmin_db schema when install QC software6. get
20、QC repository backup files from D:BackupsQCRepositoryBak after install QC software7. Unzip and replace all of the files in new QC Repository path with these backup files. In fact the new path is same as the original one8. startup QC service and login to QC Site Administration page, QC can list all o
21、f the available projects whose databases are correct to restored automatically9. check if QC projects information is available in QC Site Administration page10. check if QC projects data is correct after login the special project by project users5.2 Informal QC Server RecoveryIf the formal recovery
22、process encounters errors or does not work, we have to conduct the informal recovery approach from QC setup.1. restore all of the QC Project databases referred to 4.3.1 except database qcsiteadmin_db2. restore database qcsiteadmin_db referred to 4.3.1, but need to change the restored database name t
23、o another one, for example old_qcsiteadmin_db3. uninstall QC software and the entire QC files in QC server4. invoke QC setup program to install QC software into any path5. set SQL Sever connection as sa login when setup QC6. set the correct td password to qcsiteadmin_db schema when install QC, and Q
24、C will create a new qcsiteadmin_db database in this SQL Server7. stop QC service after QC installation is done, and we need to export Table data from old_qcsiteadmin_db and override into qcsiteadmin_db by the same Table Name by SQL Server export/import tool: mandatory tablestd.USERStd.ROLES td.USER_
25、ROLES td.PARAMStd.SEQUENCES optional tablestd.SESSION_LICENSEtd.SESSION_LICENSE_HISTORY td.SESSION _ HISTORY8. startup QC service and login QC Site Administration page by a QC administrator user, and check QC Site Administration is available9. Create all of the necessary Domains and Projects in QC S
26、ite Administration, and the empty databases are also created in SQL Server automatically. Note that their database names should be different with the databases name restored in step 110. stop QC service again11. get QC repository backup files from D:BackupsQCRepositoryBak12. Unzip the backup file, r
27、eplace the files under sa folder in the current QC Repository path with the backup sa files13. Unzip the backup file, replace the files except dbid.xml file in every project folder under qc folder of the current QC Repository path with the files under the same folder of the backup files, such as qcs
28、tarcite_3smallmeetingsolutions14. Open dbid.xml file in every project folder, and update the value of DB_NAME to the restored database name, for example starcite_smallmeetingsolutions. If other values need to update, just do it15. Open qcsiteadmin_db in SQL Server, and open td.PROJECTS Table; update
29、 DB_NAME field value to the restored database name, for example starcite_smallmeetingsolutions. If other fields need to update, just do it16. remember PROJECT_ID field values for every project name, close td.PROJECTS Table17. update the values of PROJECT_ID field of td.USER_PROJECTS in old_qcsiteadm
30、in_db database to the new values known from step 1618. export td.USER_PROJECTS Table data from old_qcsiteadmin_db and override into qcsiteadmin_db by the same Table Name by SQL Server export/import tool19. startup QC service again20. login QC Site Administration page by a QC administrator user, QC u
31、sers should be related to the relevant projects as normal21. activate these restored QC Projects and check them to associate the correct database in SQL Server22. login QC project by the project user as normal23. delete database old_qcsiteadmin_db and all of the created empty project databases in SQ
32、L Server24. deploy SQL Server database backup strategy by Section 3 Section III Quality Center Upgrade Strategy6. Quality Center UpgradeIf Quality Center would upgrade from version 9.2 to 10.0, we can follow Section 5 as well. Of course to keep all of the databases in SQL Server available is princip
33、al.6.1 Formal QC Server Upgrade1. uninstall QC 9.2 in QC server2. invoke QC 10 setup program and install it into the same folder with the original QC path3. if qcsiteadmin_db is restored or existing in QC Database server, choose upgrade existing qcsiteadmin_db schema when install QC software4. use s
34、a login to connect SQL Server when setup QC software5. set the correct td password to qcsiteadmin_db schema when install QC software6. get QC repository backup files from D:BackupsQCRepositoryBak after install QC software7. Unzip and replace the necessary files including sa and qc folder in new QC R
35、epository path with these backup files. Note that dbid.xml need not replace8. startup QC service and login to QC Site Administration page, QC can list all of the available projects whose databases are correct to restored automatically9. check if QC projects information is available in QC Site Admini
36、stration page10. upgrade every project by QC Upgrade Project tool in Site Administration page11. check if QC projects data is correct after login the special project by project users5.2 Informal QC Server UpgradeIf the formal recovery process encounters errors or does not work, we have to conduct th
37、e informal recovery approach from QC setup.1. restore all of the QC Project databases referred to 4.3.1 except database qcsiteadmin_db2. restore database qcsiteadmin_db referred to 4.3.1, but need to change the restored database name to another one, for example old_qcsiteadmin_db3. uninstall QC 9.2
38、software and the entire QC files in QC server4. invoke QC 10.0 setup program to install QC software into any path5. set SQL Sever connection as sa login when setup QC6. set the correct td password to qcsiteadmin_db schema when install QC, and QC will create a new qcsiteadmin_db database in this SQL
39、Server7. stop QC service after QC 10.0 installation is done, and we need to export Table data from old_qcsiteadmin_db and override into qcsiteadmin_db by the same Table Name by SQL Server export/import tool; before that we should confirm these Tables of the 2 databases have the common structure: man
40、datory tablestd.USERStd.ROLES td.USER_ROLES td.PARAMStd.SEQUENCES optional tablestd.SESSION_LICENSEtd.SESSION_LICENSE_HISTORY td.SESSION _ HISTORY8. startup QC service and login QC Site Administration page by a QC administrator user, and check QC Site Administration is available9. Create all of the
41、necessary Domains and Projects in QC Site Administration, and the empty databases are also created in SQL Server automatically. Note that their database names should be different with the databases name restored in step 110. stop QC service again11. get QC repository backup files from D:BackupsQCRep
42、ositoryBak12. Unzip the backup file, compare the backup files about sa folder with the current files, select the necessary files to replace the files under sa folder in the current QC Repository path13. Unzip the backup file, compare the backup files about qc folder with the current files, select th
43、e necessary files to replace them except dbid.xml file in every project folder under qc folder of the current QC Repository path with the files under the same folder of the backup files, such as qcstarcite_3smallmeetingsolutions14. Open dbid.xml file in every project folder, and update the value of DB_NAME to the restored database name, for example starcite_smallmeetin
