If VOB servers cannot migrate when clients do

If any VOB server cannot migrate when its clients do and you need to preserve the clients’ ability to access VOBs on that server, you must use vob_siddump to establish a mapping between new SIDs and old ones.

About this task

After the mapping has been established, you can use vob_sidwalk to update the VOB database with the new SIDs.
Note: Unless the VOB remains locked from the time you begin Step 3 until the time you complete Step 4, users can create new objects in the VOB between the steps. If they do, you must perform both steps again.

Procedure

  1. Log on to a client that has been migrated to the Active Directory domain.
  2. Lock the VOB for all users except yourself (–nusers your-username).
  3. Run vob_siddump to generate a map file.
    (You must use vob_siddump because you cannot run vob_sidwalk from a remote host.) In this example, vob-tag is the VOB tag of a VOB on a server that is still in the Windows NT® resource domain, and SIDfile-path is the pathname to the map file that vob_siddump generates. (If SIDfile-path cannot be created on a drive that is accessible to the VOB server host, you must copy it to the VOB server host before you perform Step 4.)

    vob_siddump –sidhistory vob-tag SIDfile-path

  4. Log on to the VOB server that hosts the VOB whose tag you used in Step 3.
    While the VOB still locked for all users except yourself, run vob_sidwalk to update the SID information stored in the VOB

    vob_sidwalk –execute –map mapfile-path vob-tag SIDfile-path

    In this example, mapfile-path is the map file you generated in Step 3 and SIDfile-path is the name of a file in which vob_sidwalk logs the changes it makes. For more information, see Using vob_sidwalk to change or update VOB users and groups.
  5. Unlock the VOB.