Physical VOB definition

ClearCase repositories can be broken up into numerous stand-alone VOBs are kept together in larger ones. Table 10-8 lists some of the considerations for breaking up VOBS.

Table 10-8. Trade-off between large and small VOBs
More VOBsFewer VOBs

  • Simpler access control

  • Easier to split across servers on growth

  • Less data on VOB restore

  • Finer-grain licensing for MultiSite

  • Simpler access for developers

  • Easier administration

A few common practices:

  • Components that are closely related are kept in the same VOB.

  • Components that need high security are kept separate (both data VOB and project VOB).

  • Components containing checked-in binaries are kept separate from source.

Typically project VOBs are separated from the data VOBs. It is acceptable ...

Get Software Configuration Management: A Clear Case for IBM Rational ClearCase and ClearQuest UCM now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Start your free trial