I am using CCRC 7.1.2 in our project.Is there any option to synchronize local copy with remote copy so that we can update only the modified files?
Refresh->Update from repository option is giving entire folder contents that we are updating but i need only the modified files
The "Refresh->Update from Repository" should be available at the file level
(see "Updating a resource in a ClearCase view", which should apply also to CCRC , not just the ClearCase Explorer with a classic ClearCase installation)
That means you can select a modified file and ask for the latest version of that file, you don't have to update the all folder or the all view.
Related
This is a follow on from op - Moving Vobs between Win and AIX
Due to the aix and win vob servers sharing resources (common CC reg & Common Admin PVOB on the Aix box) we need to amalgamate these vob servers onto the AIX server as a precursor to our ultimate move to new servers at CC8.
on the Win VOb Server we have locked the vob, run vob_siddump then a reformat dump of the vob.
Then using xcopy we copied the dumped vob.vbs from Windows to AIX vob server run the fix_prot on the new server.
But when we run the reformatvob -load it goes through it's steps Shows "Loader Done" then shows the following errors
Error from vob database /vobstore/vobs/vobname.vbs.
Error Trouble Opening the VOB Database /vobstore/vobs/vobname.vbs,
Error Trouble Loading versioned object base /vobstore/vobs/vobname.vbs.
Because of the shared registry is this due to the existing registry entry and we need to unregister and then rmtag before registering and tagging fresh or do we need to do anything further?
Clearcase logs on aix vob server show:
DB Log - Error process not running on registery specified hostname (old win vob server)
Vob Log - shows unix UID and GID messange and Warning unable to verify mount options in vob tag registry Clearcase Object not found
David, there are a few things you need to do here:
unregister the VOB and remove all the tags that refer to the old server
reregister and retag the vobs at the new location.
If you can't register the VOB, run fix_prot -r -root ... to reset the ownership and try again.
run vob_sidwalk to remap object ownership.
run it again with -recover_filesystem to reset container ownership. Alternatively run checkvob -pool -protections -fix -force {vob storage dir}.
The last step really needed to be started on the Windows side before this started. Essentially, you needed a sid dump file to turn into the map file that the sidwalk needs (unless you want to remap everything to the VOB owner...)
The complete procedure to follow is at Moving VOBs between Operating system types You may want to start fresh from there if you still have the VOB located in the old location.
I am reading the documentation of mkview as I am trying to create a snapshot view on my local disk and I am confused by the terminology surrounding "view storage directory", "snapshot view directory" and the -stgloc, -vws and -colocated_server options.
Here's my understanding:
"snapshot view directory" refers to the working directory on my local file system where I will be editing the files I checkout
"view storage directory" refers to some directory in the server where metadata about my view will be kept. I won't have anything to do with this directory.
Is this correct?
So to create a snapshot with server storage of the "view storage directory" and local storage of the "snapshot view directory", I would do:
ct mkview -sna -tag view_tag -vws /data/VIEWS/view_tag.vws -host foo -hpath /data/VIEWS/view_tag.vws -gpath /data/VIEWS/view_tag.vws ~/some/path/in/my/local/filesystem
(/data/VIEWS is an NFS file-system in my machine). Is that right? This seems to be consistent with what is described here.
However, I don't get what the -hpath and -gpath options are supposed to do (given that -vws has already provided the view storage directory and given that they seem to carry the same values). Also I don't understand the caveat in the mkview documentation that says (under -vws):
Use -stgloc rather than this option whenever possible
"snapshot view directory" refers to the working directory on my local file system where I will be editing the files I checkout
Yes, it can be anywhere on your disk, as opposed to dynamic view which are using a fixed mounting point (M:\ on Windows, /view on Unix)
"view storage directory" refers to some directory in the server where metadata about my view will be kept. I won't have anything to do with this directory.
Yes, and that is valid for both snapshot and dynamic view. You don't have anything to do... except both the ClearCase view server and your account must be capable to access it, which means it is often referenced though a global storage path.
The cleartool mkview man page (the official html page) describes vws as:
view storage directory in a location that is consistently connected to the local area network, on a host where ClearCase has been installed or on a NAS device that provides storage for such a host.
This location could be a server storage location (specified by –stgloc) or a location specified by the –vws option
If the view server is not your local workstation, then –host –hpath –gpath reference a host and path accessible both by your workstation and by the ClearCase server.
If the view server is your workstation, then -vws and hpath can be a local path, while gpath is a network shared path accessible by the view server.
I prefer keeping the view server on the local host (provided ClearCase was installed with that feature), as it avoids creating a single point of failure (a remote View server), and quickens the view operations (since the metadata are stored locally).
We have a ClearCase server installed on Solaris box and there are several vobs replicated in a multi-site environment. Now as this Clearcase server is becoming old we have setup an new Server on Windows and able to bring that new server into multi-site with all the required vobs. Now we would like to remove/decommission the vobs from old solaris box and want to free up the space occupied by those vobs.
Can any one suggest the best procedure to do this and also point us to the links for that procedure?
You can:
follow the technote "Moving a VOB using ClearCase MultiSite", which basically:
creates a replica on the source vob server:
import the replica on the destination vob server:
multitool mkreplica -export -workdir c:\\
[-maxsize 100m] -fship :
#
Import:
multitool mkreplica -import -workdir /var/tmp/doesntexist/ -tag
/your/new/vobtag/ -stgloc -auto -npreserve -public /var/adm/atria/
shipping/ms_ship/incoming/
simply rmtag and unregister the vob on the solaris box, in order to remove it completely from the central registry server.
See "How to remove a VOB or View from the ClearCase registry"
The alternative, to delete that vob, and to follow "Deleting a replica"
Then you can simply delete the vob and get back that disk space.
I already added additional folders from the same FTP via View > Remote Host. As I press sync the new folders doesn't appear in my local copy or in the project view. Now I like to have the local copy that I can edit (autosync on save is enabled).
How do I import those additional files?
Here's how I did it. From the Remote Host tab right-click the folder and select "Remove Path From Excluded". Then I drag the remote folder over to where it should be in the Project (local) pane and it copies all the files over.
I tried the sync from deployed, sync with local like the docs say but never did anything. Above method worked for me
I have already created my project views from the Rational Clearcase Client on XP machine.
Due to some reason I need to format my machine and I have installed Windows 7. Now my problem is, I already have the existing folders of the views created on XP. How do I re-import it so it will be shown in my Clearcase Navigator on Windows 7 machine?
In the OP jaychapani 's case (ClearCase Remote client):
The view storage for a "web view" is by definition on the CCRC server (so not on the client)
See "
How to reconstruct a CCRC view copy area after an unintentional deletion"
(the equivalent of a snapshot view directory is called, in CCRC, "view copy area")
A situation may occur where a developer unintentionally deletes a copy area and there is no backup.
The Web view still exists on the CM server and the view tag still exists in the ClearCase registry.
There is no way to perform such recovery completely from the CCRC graphical user interface (GUI).
Determine the View Tag (you can run cleartool lsview -l on the Web server: ask your ClearCase admin)
Create a new copy area (for example: D:\Webviews\<VIEWTAG>)
Create a .copyarea.dat file in the root of the above directory
Refer to technote 1119280 About the .copyarea.dat and .copyarea.db files for further details about this file.
a. Copy a .copyarea.dat file from another (known good) copy area into the root of the new copy area
b. Remove the "READONLY" and "HIDDEN" file attributes from that file.
Determine the UUID of the webview <VIEWTAG>.
You can get the UUID by running a cleartool lsview -l on the Web server (again, ask your ClearCase admin).
Modify the .copyarea.dat in the root of the new copy area.
If it was from a copy, modify the UUID and also the name of the <WEBVIEW> including its hexadecimal length field; modify also the name of the VOB root directory.
The timestamp in .copyarea.dat file does not need to be modified.
Remove the view tag from the .ccase_wvreg file.
Refer to technote1228258 About the CCRC .ccase_wvreg file for further details about this file.
Use CCRC GUI to perform "Add existing view".
Perform a Refresh->Repair->Discordance.
This repairs the content of the view.
Original answer, for a full ClearCase installation
If depends where the view storage of your (snapshot) view is stored.
If the view storage isn't stored on your local computer, you can simply re-create the root directory of your snapshot view and use "regen_view_dot_dat.pl" script found in <cc-home-dir>\etc\utils to regenerate the view.dat hidden file.
See "Clearcase - Find out when view was created" for more on that tool.
From that path, you can type clearexplorer . (note the space and the '.' dot), and you will see your view back in the ClearCase Explorer. Update it and you will find back its content.
If you had saved your snapshot view before formatting (including the hidden file view.dat), this is even easier: go the root path of that view and type clearexplorer .: your view will be back.