Home
Administering
Learn how to administer the product.
Administering HCL VersionVault
Learn about performing administrative tasks for an HCL VersionVault community including managing software licenses, user and group accounts, VersionVault server and client hosts, shared data, and the network that connects them.
Troubleshooting
These topics cover a variety of procedures that administrators might need to follow to find and fix problems.
Locating MVFS data containers
You can use standard operating system utilities and the mvfsstorage command to find where MVFS files are physically stored. Locating this storage may help resolve file access problems in dynamic views.
Finding the VOB location

Finding the VOB location

About this task

The describe command shows you the path to the VOB root over the network and also relative to the host on which the VOB storage resides:

Example

cleartool describe vob:\monet\src
versioned object base "\monet" created 01-Feb-93.17:35:03 by (vobadm.vobadm@sol) VOB storage host:pathname "sol:c:\vbstore\monet.vbs" VOB storage global pathname "\\sol_vbstore\monet.vbs" VOB ownership: owner vobadm group vobadm

You can also get this information from the All VOBs node of the HCL VersionVault Administration Console, which lists all VOB tags registered in the local host’s region on the local host’s registry server. The taskpad and detail views show the host and global path of the VOB storage directory along with other information about each VOB. From this listing you can navigate to the VOB storage node for the specific VOB in the HCL VersionVault Administration Console, where you can manage VOB storage.