How do i properly move Test Director to a new server when there are existing traces from CaliberRM?
When moving the Test Director Server, Test Director has an Admin
Copy tool where you copy the database and all of the ID numbers
change. If this option is used when moving TD to a new server, all
of the existing traces will be no longer be valid since the pointer
to the same ID may be a different object. Since each
test\set\step in Test Director has a unique ID number, when a trace
is created from CaliberRM to Test Director, this ID # is stored. If
this number changes, the trace is lost and cannot be recovered.
We recommend that customers copy the database outside of Test
Director in whichever database they are using (SQL, Access, Oracle,
etc.). This will preserve the ID numbers used in the Test Director
After the Test Director server move, we will need to ensure that
CaliberRM will be able to locate the new Test Director
Server. This can be done a couple of ways depending on what
is more appropriate for your environment.
If the previous Test director address will still be valid(just
upgrading hardware, but same configuraton), no changes will need to
If the old Test Director Server address is being decommissioned,
and there will be several apps affected by this move, it may be
beneficial to setup a network alias to map request for the old TD
address to the new TD address.
If CaliberRM is the only application interfacing with TD, or to
prevent additional alias" which can become quite complicated
to trace over time we can update the server address in the
CaliberRM database. To do this you will need to run the IVQL
utility available from Borland Technical Support. From a