I am currently using QC 9.2 but will soon be upgrading to QC 10. I will install QC 10 on the new machine and want to move everything from the old machine to the new one.
What all will I need to do so the new machine will have all the info the old machine has.
Is it as simple as backing up the database then importing it into QC 10? or is it more involved?
If anyone has a step by step guide, that would be great.
Not Sure that it will help you, but here are the steps that we followed.
1 Verify System Configurations
IC Group Prepares Virtual Server Environment for Production System
2 Installation Prerequisites
SMTP Server Name
Database Server Name/Port Number (for Production)
License File Location (for Production)
JBOSS - Service User Name, Password, and Domain
3 Backup Quality Center Project Databases
4 Backup qcsiteadmin_db
5 Rename qcsiteadmin_db to qcsiteadmin_db10
6 Run Scripts for TD permissions and QC permissions on qcsiteadmin_db10
7 Install Quality Center 10.0
- Show advanced Database Server Configuration
- Point to qcsiteadmin_db10 to upgrade SCHEMA
8 Restore qcsiteadmin_db from backup
9 Stop Service (HP Quality Center)
10 Install Latest Patch (8.0) before running QC
11 Start Service (HP Quality Center)
12 Reset IIS
- Open Cmd Prompt on server
- type "iisreset" at command prompt
13 Start Quality Center
14 Log on to Site Admin
15 REMOVE Projects
16 Verify Site Admin configuration
17 Copy Existing repository information from old App server to new app server - Do this on a Project by Project basis
18 Edit Dbid.xml for QC 10
- Change "Path"
19 Train Quality Center Users
20 Migrate Quality Center Projects
20a - Back Up Projects
20b - De-Activate project to be migrated In the 9.2 Environment
20c - Verify that DBA has run Script against Project Database.
20c - Run Verification
20d - Run Repair
20e - Run Upgrade
20f - Activate Project In the 10.0 Environment
20g - Remove Project from the 9.2 Environment
Timing - For Each Project
21 Set Project Administrator(s) for each project
22 Log on to each project as administrator and Customize Module Access to remove "Business Components". This must be done for each project
23 Validate Migration of Projects
24 Upgrade QTP Scripts
We are running 9.2 and 10.0 in Parallel. We have a (.2 Server and a 10.0 server. They are both accessing the same SQL server therefore we have two QCSiteAdmin databases. One for 9.2 and one for 10.0.
My advice beyond what has been posted is to test. Build a test environment with a web and db server and test your upgrade. The one aspect I know HP has not documented is moving from SQL2000 to SQL2005. If that is the case for your upgrade please search the fourm as this upgrade path is well covered.
For us it's just an upgrade from 9.2 to 10.0. But the client software needs to be scripted in order to be rolled out. So it's virtually impossible to upgrade (re-install) the server and roll out the client to all users at the same time.
How do you handle the 2 different client installations? Is it possible to have a system with client 9.2 to connect to a server running 10.0 or vice versa?
[/ QUOTE ]
No, that does not work. When you connect to any QC server, there is a piece of code that verifies that your client installation matches the server's. If it doesn't, it automatically installs the client version matching the server's (and it needs the user to have administrative rights).
Even if you manage to bypass that mechanism, that won't work because the format of the data exchanged between the client and the server may change from one QC version from another.
[ QUOTE ]
So it's virtually impossible to upgrade (re-install) the server and roll out the client to all users at the same time.
[/ QUOTE ]
Don't you have any other software that needs such a synchronization between the server and client parts ? Usually, this is done by upgrading the server off work hours and including the client upgrade in the client network login procedure.