Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Running v7 and v8 on a single server
Topic Summary: Is this likely to work?
Created On: 28-Apr-2008 10:40
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 28-Apr-2008 10:40
User is offline View Users Profile Print this message


Alan Gooch

Posts: 107
Joined: 30-Aug-2005

We are in the process of moving our DOORS database from its own dedicated server onto CITRIX and upgrading from v7 to v8 at the same time.

We've done a trial run for which we copied the DOORS database onto a temporary PC and ran everything from there, including (obviously) copying the copy before migrating.

Having ascertained the time involved, I have been asked to look at whether it may be possible to do everything on the DOORS server to try and speed it up and cause less disruption to our users. I would expect the steps to be:-
install v8 server and client
stop v7 server
copy the DB
start the v8 server
migrate the copy to v8
archive v8 DB
stop v8 server
Upload v8 DB to CITRIX

This leaves us with no running DB on our old server, and everyone should be using the CITRIX version.

Whilst I appreciate the possible benefits of doing this as the DOORS server is a much faster machine than the temporary PC, I have grave doubts about the viability of doing it this way.
I have a nagging feeling that, as both v7 and v8 use registry based settings, trying to run the two versions of the database concurrently on the same machine is likely to be a problem, even if, as I expect, I have to identify a separate port setting for the v8 server.

Would it work if I stopped the v7 server BEFORE installing v8, and would it be a reversible action if we hit an unexpected problem?

Does anyone have any views on this?
Am I right to be nervous about it?

TIA
Report this to a Moderator Report this to a Moderator
 28-Apr-2008 12:45
User is offline View Users Profile Print this message


Scott Boisvert

Posts: 348
Joined: 14-Apr-2006

I have a test server where I'm running an 8.1 and 8.3 server concurrently and didn't have any problems with the installation. I believe I did the same thing when we upgraded from 7.1 to 8.1.

I say try it on a test server and document your process so when you do it on the live server there is no questions as to what needs to be done.

-------------------------
Scott Boisvert
Engineering Tools Administrator
L-3 Communications - Avionics Systems
scott.boisvert@l-3com.com
Report this to a Moderator Report this to a Moderator
 28-Apr-2008 20:41
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

There is no reason a v7.1 database and a v8.3 database cannot peacefully coexist on the same server. Yes, you need to have a different ports specified for the two databases, as well as of course 2 different database root folder locations, as well as 2 different install locations. Keep in mind, however, that installing v8.3 will uninstall v7.1 which means you'll need to re-install v7.1 after v8.3 install (that's true for both the server and the clients).

As for your sequence: [1] I hope you mean 'backup' and not 'archive' [2] stop the v8 service before archiving.

I don't see the point of doing the work on the old production server, if you figure to immediately move it to the Citrix box. Might as well backup the v7.1 database and upload it into the v8 Citrix spot. Down time is actually a little less since you skip the database-copy step. It doesn't matter if you backup-restore before you migrate (my notion) or after (your notion).

Keep in mind its not mandatory to move the database to Citrix, in order to use Citrix for the clients. If the Citrix box is 'near' the production DOORS server ('near' means 'fast access') you won't take much of a performance hit. I wonder about security if the clients are running on the production server (Citrix).

You've surely upgraded your licenses by now; v8.2-v8.3 use different licensing than v7.1-v8.1 do; but that new licensing is backward compatible.

- Louie
Report this to a Moderator Report this to a Moderator
 29-Apr-2008 11:12
User is offline View Users Profile Print this message


Alan Gooch

Posts: 107
Joined: 30-Aug-2005

Louie,

one of main problems is the inability to fully archive the project due to the size of the DB and a known v7.1 bug, hence the need to upgrade to v8 BEFORE moving to CITRIX.

I believe:-
to move to CITRIX I archive the project and restore it to the CITRIX server, therefore I do mean "archive" not "backup", in which case I do not need to stop the v8 service as it will not be useable or accessible to any of our users as none have a v8 client.

Obviously we need to "backup" the v7 database before starting this activity in case it all goes pear shaped. This will be done prior to starting this whole process.

> I wonder about security if the clients are running on the production server (Citrix).

This is something our CITRIX server owners have to sort out before we move as there are many other projects there already.

> You've surely upgraded your licenses by now; v8.2-v8.3 use different licensing than v7.1-v8.1 do; but that new licensing is backward compatible.

I think we're still using 8.1 on CITRIX, which is fine for us, but moves are afoot to get us to 8.2 (or. 8.3), which is another reason to sort this move out beforehand.
Report this to a Moderator Report this to a Moderator
 29-Apr-2008 14:53
User is offline View Users Profile Print this message


Louie Landale

Posts: 2070
Joined: 12-Sep-2002

Understand that archive-restore of a project will [] mess up out of project links [] lose or mess up your specific access records. Before archiving the project you need to erase all the access records, and after restoring it you need to manually reset them. Don't be fooled into thinking that if you have a group with the same name in both databases that any accesses that group has in the project in DB-A will be preserved when its restored in DB-B.

If you are upgrading the entire database then you definately do not want to 'archive', you want to 'backup'. If you plan to preserve the v7 database for just some projects and upgrade to v8 just one of your projects, you are still better off with a 'backup' as you can preserve your user database. After standing up the v8 database, purge all the other projects from the v8, and purge the project of interest from the v7 database.

Only archive-restore when you have to two valid database already.

- Louie
Report this to a Moderator Report this to a Moderator
 29-Apr-2008 15:10
User is offline View Users Profile Print this message


Alan Gooch

Posts: 107
Joined: 30-Aug-2005

A-ha. I understand now.

We have no inter-project links.
We have a Telelogic script which stores all the access information in a separate module, with a second script run after restoration on CITRIX which restores those access records.

We also do regular backup of the server disk (every other day).

Having said that, I appreciate what you are saying.
We are doing a trial run of this with a copy of our database prior to the real deal, so that we can check that the settings we believe we have we actually DO have.

My original question was with regards to having v7.1 and v8.1 on the same server. Your earlier response indicating that installing v8.3 uninstalls v7.1 makes we wary of performing this task on the DOORS server itself.
As we are moving to CITRIX and NOT using our DOORS server for v8, I think that, it would after all be prudent to copy the database to a second machine, upgrade that and copy the archive of THAT to CITRIX, which is more or less the premise I started from. For the extra time involved in copying the DOORS server to a second machine probably outweighs the complexity of having two version of DOORS running on the same machine and having to reinstall server and client for v7.1 after installing v8.1.

I may be being over cautious here, but I think I'm happier with the process.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.