Migrating individual hosts
When all users and groups have been migrated and no users
are required to log on to the Windows NT® domain, migrate Rational® ClearCase® hosts
to the Active Directory domain.
If you cannot migrate all your
Rational ClearCase hosts
at the same time, then migrate VOB servers first. (Registry and license
servers can migrate at any time, because they do not store SIDs in
their databases.)
Note: These procedures require you to use the vob_sidwalk utility.
Before performing any of these procedures, review the vob_sidwalk reference
page to better understand the capabilities of vob_sidwalk.
To
migrate an individual Rational ClearCase host:
- Stop Rational ClearCase on
the host.
- Use the procedures defined by Microsoft® to
migrate the host to the Active Directory domain.
- Reconfigure each Rational ClearCase host
so that its albd_server logs on as the (migrated) Rational ClearCase server
process user in the Active Directory domain. You can do
this by reinstalling Rational ClearCase on
the host and specifying the new account, or you can do it manually,
as described in Defining required domain accounts manually.
- If the host is a VOB server that will be also accessed
by clients running Linux® or the UNIX® system,
reset the credentials mapping domain in the Options page of
the ClearCase program
in Control Panel. The credentials mapping domain must be one in which
user and group account names match those of users on Linux or
the UNIX system that will access VOBs on this server.
- Restart Rational ClearCase on
the host.
- Reprotect any VOB and view storage on the host. To
do so, run the fix_prot utility on each VOB or
view storage directory as shown in this example:
ccase-home-dir\etc\utils\fix_prot –replace storage-dir-pname
In
this example, storage-dir-pname is the pathname
to the VOB or view storage directory.
- Update VOB databases with the new SIDs that represent the
cloned user and group accounts.
- Log on to the VOB server host as the VOB owner or privileged
user.
- Lock the VOB for all users except yourself (–nusers you).
Replace the old SIDs with the new ones.
Run vob_sidwalk. In this example, vob-tag is
the VOB tag of the VOB you are updating and SIDfile-path is
the name of a file in which vob_sidwalk logs the
changes it makes: ccase-home-dir\etc\utils\vob_sidwalk –s –execute vob-tag SIDfile-path
For
additional details about how vob_sidwalk remaps
SIDs, see Using vob_sidwalk to change or update VOB users and groups.
- Unlock the VOB.
Note: If you had been using proxy groups to enable users
from multiple domains to access a common set of
Rational ClearCase artifacts,
an Active Directory universal group should be used to eliminate the
need for proxy groups and domain mapping. Follow the procedure in
Converting proxy groups