Using vob_sidwalk to change or update VOB users and groups

The vob_sidwalk command provides a flexible means of reassigning ownership of objects in a VOB, updating the SIDS that represent the groups in a VOB’s group list, and correcting VOB storage directory protections.

When you move a VOB to a host in a domain that does not trust the domain in which the VOB’s original host exists, all SIDs stored in the VOB database become not valid, because they do not resolve to an account in the new domain. This problem occurs during domain migration (the host moves to a different domain and the VOB stays on the host). It also occurs when a VOB is moved from a host in one domain to a host in a different domain.

Common uses for vob_sidwalk include these:
  • Migrating a VOB from a Windows NT® domain to an Active Directory domain
  • Moving a VOB to a host in a domain that does not trust the original domain
  • Moving a VOB from a Windows® host to a host running Linux® or the UNIX® system, or vice versa
  • Moving a VOB server host to a domain that does not trust the original domain

This section provides several examples of procedures that use vob_sidwalk and vob_siddump. For additional examples of procedures that use vob_sidwalk, see Moving VOBs and relocating VOB data. The vob_sidwalk reference page provides complete information about all vob_sidwalk and vob_siddump options.

Regardless of the procedure you use, run vob_siddump (or vob_sidwalk) without the –execute option. Then examine the output to determine which objects in the VOB would have new owners. After you verify that the changes in ownership will be correct, run vob_sidwalk with the –execute option to actually remap the SIDs. The output SID file is written in comma-separated-value (CSV) form, so it can be viewed and changed with any text editor or any spreadsheet program that can read a file of this format.