1

I am in process of upgrading ClearCase 7.0 from old machines (windows 2003) to ClearCase8.0 new machines(with windows 2012).

What would be the best way to do it so that in case we run into failures, we go back to 7.0 in old machines? Clients will still be at ClearCase 7.0.

To be clearer, a ClearCase architecture involves:

  • a vob server
  • a view server
  • a registry server
  • a icense server

http://techpubs.sgi.com/library/dynaweb_docs/0630/SGI_Admin/books/ClrC_AG/sgi_html/figures/ch18-4.gif

I need to know what needs to restored/preserved in order to facilitate a rollback in case of issues during the upgrade process.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
user2636464
  • 685
  • 7
  • 17

1 Answers1

1

One way which can allow an easy rollback is to make sure to make a separate registry server between CC7 and CC8, instead of upgrading the existing one.
And register the moved VOB in the new registry server, as part of the process described in "Moving Vob".

You can then ask the CC clients to points to the new registry server (for CC8), checking with the registry client list to check which to determine which Rational® ClearCase® hosts are clients of a specific registry server (and check if all your clients have switched or not).
A client can see which registry server he/she uses.

I would also recommend for the client to create new views once they refer to the new registry server, instead of trying to move the old ones.
That way, in case of rollback, they would still have their CC7 views.

Community
  • 1
  • 1
VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250