Restore clearcase lt server from existing files

Some time ago, the previous win2000advserver could not be upgraded normally, and we tried our best to solve the problem. It is expected that the gates will soon stop the Win2000 upgrade service, so we simply install win2k3 now, at least we will find the patches on the Internet. If we are lucky, we can still see that the dversion can be upgraded normally. Shortly after the setup of win2k3 was started, it was found that the installation could not be upgraded, and it was a little dizzy. The problem now is that this server has always been used as a clearcase lt server. If it cannot be upgraded and installed, how can we back up and restore existing clearcase files and data? After searching the Internet, we suddenly found that clearcase lt server for Windows didn't provide these features, but there were some notes about the backup and recovery methods of the UNIX clearcase server, using UNIX file backup and recovery methods. From this point, clearcase should be able to back up files. before reinstalling the system, you only need to keep the project folders and files generated by the original clearcase. Several copies of the file were backed up before the adventure, then go on.
First, install win2k3 ent server (SP1;
Then, install the rational clearcase lt License Server and clearcase lt Server & client, which is easy to use;
Open project explorer and the system prompts that the storage location cannot be found. You need to create a storage location. How can we recover from the original file? No relevant information is found online. After thinking about Several HR resources, I suddenly remembered that the cleartool provided by clearcase was very useful. I quickly found out the commands and looked at them all I was interested in. The mkstgloc command can be used to recreate the storage location with an existing folder. The command is as follows:
Mkstgloc-vob projectnamevobs E: \ clearcasestorage \ projectnamevobs
Note that the third parameter is the name of vob, and the fourth parameter is the folder where the vob is stored. There should be multiple vob, including one pvob. This command restores the storage location of the vob, and uses another mkstgloc to restore the storage location of the view, as shown below:
Mkstgloc-vob projectnameviews E: \ clearcasestorage \ projectnameviews
The third parameter must be consistent with the previous name, and the case must be correct. You can use ls to view the stgloc on the server. Next we need to restore vob and view. What command is used? Every command is not needed. Think about it. The system file directory is used in UNIX to restore it. Since stgloc can be restored successfully, each directory must have a file that records the folder attributes, I found one in the stgloc directory. stgloc files. Others are multiple vob or view folders. Open the vob and view folders, which are also several files and named admin
, A, B, C, and other folders. Read the cleartool command again and find that mkvob, mkview, and register are related to the creation of vob and view. After reading their help, confirm that the first two commands are new vob and view, which do not meet the requirements. Register can register existing folders in clearcase. Okay, that's it. Register vob first, one by one, as shown below:
Register-vob E: \ clearcasestorage \ REIT \ projectnamevobs \ vob1.vbs
...
Run the following command to register pvob:
Register-vob-ucmproject E: \ clearcasestorage \ REIT \ projectnamevobs \ pvob. vbs
Then View:
Register-view E: \ clearcasestorage \ REIT \ projectnameviews \ view1.vbs
...
Do not enter the path incorrectly. Later, we found that the registration sequence does not affect the results.
Open the project explorer, and the system prompts that the UCM project cannot be found. Use the administration console to check whether there is a pvob. Why does the system prompt NO? Take a closer look and find that all vob and view share the same thing: No tag. Without tags, vob and view cannot be accessed. Create a new one for them. OK. The correct prompt is displayed for project explorer. On the client, if you have already joined the project, you should be able to contact the server normally. If not, it should be okay from joining the project.
At this point, clearcase lt server is restored successfully.