Environment Description: In order to better explain the problem, we imagine a virtual environment:
Server1:
Computer Name: from domain name: OLD operating system: Win2000 Server
Server2:
Computer Name: TO Domain Name: New Operating System: Win2000 Server
Task Description: Mobile libpub.vbs C: /clearcasestorage/vobs/libpub.vbs to Computer To VOBSTG
Move steps:
1. Confident, VOB to be moved has been formatted with Schema Version 54. This is because early Schema Versions does not support cross-domain mobile VOBs, you can use the ClearCase Administration Console or Cleartool Describe command to confirm a VOB's Schema Version. If the VOB to be moved is not formatted with Schema Version 54, then reformatted with the reformatvob command.
2. Log in to the VOB Server host from the VOB owner or a privileged user.
3. Lock the VOB you want to move. In order to ensure that you don't have a new VOB object when you do STEP # 4, you have to lock libpub.vbs.
4. Generate a SID file that lists the usernames and group names jointly integrated with libpub.vbs. Run the VOB_SIDDUMP command as shown below:
CCase-Home-Dir / etc / utils / vob_siddump / libpub
C: /clearcasestorage/vobs/libpub.vbs/libpub.csv
We recommend creating a SID file in the storage path of the VOB so that it can be used when the storage path moves, and we will use this file in STEP # 10.
5. Stop ClearCase services on host from host.
6. Copy the VOB storage path to the shared VOB storage location of the host TO.
C: / ClearcaseStorage / VOBS NET USE E: // TO / VOBSTG
C: / clearcasestorage / vobs ccopy libpub.vbs E: /LIBPUB.VBS
7. Install the VOB storage path protection on the host TO. As a libpub.vbs or special permissions Owners log in to the host to Run the fix_prot tool as the example below, Vobadm is the name of the new VOB owner, CCUsers is the name of the new owner of VOB, v: / vobstg / libpub .vbs is the local storage path that moves VOB on the host TO.
CCase-Home-Dir / etc / utiles / fix_prot -root -r -chown vobadm -chgrp ccUsers v: /vobstg/libpub.vbs
8. Using the new VOB objects and labels attached to the VOB storage path to replace the old. The command is as follows:
Cleartool register -vob-replace //to/vobstg/libpub.vbs
Cleartool mktag -vob-replace - tag / libpub //to/vobstg/libpub.vbs
9. Use the ClearCase Administration Console to lock VOB on the host TO. If you are worried that the user will try to visit when the new VOB is not ready, then lock it immediately.
10. Create a MAP file. Open your SID file created in Step # 4 (it is best to use Excle), replace the new domain column of the new-name column for each line with the new domain name and user name corresponding to the OLD-Name column; then delete the last three columns ( Values of type, new-sid, count. Here is the original SID file (example):
Old-name
Type
Old-SID
NEW-NAME
Type
New-SID
Count
OLD / AKP User NT: S-1-2-21-532 ... Ignore User
137
Here is a replacement SID file (example):
Old-name
Type
Old-SID
NEW-NAME
Type
New-SID
Count
OLD / AKP User NT: S-1-2-21-532 ... New / AKP
11. Test this generated MAP file. Run VOB_SIDWalk without -execute, write the lib-map.csv map file to a new SID file libpub-test.csv, but no change is made to VOB.
CCase-Home-Dir / etc / utils / vob_sidwalk -map
Too/vobstg/libpub.vbs/libpub-map.csv / libpub libpub-test.csv
12. If you consider the user may access Vob, lock VOB.
13. Update the identity of users and groups stored in VOB. When you are confident that the MAP file is correct, run the VOB_SIDwalk command, as shown below:
CCase-Home-Dir / etc / utils / vob_sidwalk -execute -map
Too/vobstg/libpub.vbs/libpub-map.csv / libpub libpub-exec.csv
14. Re-recover the ACLS file system. Finally, on the host TO, run with the VOB owner or special authority user, run the VOB_SIDwalk command with the -Recover_FileSystem selected parameters to accept the correct ACLS of the VOB storage path. The command format is as follows:
CCase-Home-Dir / etc / utils / vob_sidwalk-gene_filesystem / libpub
v: /vobstg/libpub.vbs/newlibpub.vbs
15. Confirm that the client under all new domain names can access the VOB just moved.
16. Confirm that all ClearCase users under the new domain name can access VOB. Users should be able to create, change, and delete their own objects.
