[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


Migrating Directory Data on Solaris Platforms

When you upgrade from an earlier SDX or SRC release, you must migrate your current directories for the upgraded SRC release.

We provide procedures to migrate directory data for Sun ONE Directory Server (iPlanet), or DirX from an earlier SRC or SDX software release this release. If you use Oracle Internet Directory, see the documentation for that product for information about updating directory data.

NOTE: The documentation does not describe how to change from one directory type to another when you upgrade to the current SRC release. Contact Juniper Networks Professional Services for assistance if you need to change directory types.


Before you start the migration procedures, you must provide a new host machine for the new software. We refer to this host as the migration host. After you complete the migration procedure, you can transfer the new installation to the original host or use the migration host as your new deployment host.

The migration host must include the following features:

Overview of the Migration Script

The migration script performs different tasks depending on whether you are upgrading your existing directory server to the latest release or keeping the current release.

Script Tasks Without Directory Server Upgrade

  1. Export and convert any existing LDAP objects into a file.
  2. Delete the existing objects from the LDAP directory.
  3. Delete all obsolete schema elements from the global directory schema.
  4. Modify existing schema elements as needed, and add the new schema elements to the global directory schema.
  5. Extend the access-control schema. For DirX only, extend the directory information tree (DIT) structure and DIT content rules.
  6. Modify existing data as needed.
  7. Import the modified LDAP objects into the directory.

Script Tasks With Directory Server Upgrade

  1. Export and convert any existing LDAP objects into a file.
  2. Delete the existing objects from the LDAP directory.
  3. Export the existing database into an LDAP Data Interchange Format (LDIF) file in case the databases are not compatible between the current and upgraded versions.
  4. Remove the existing LDAP directory instance and the corresponding directory add-on package.
  5. Install the upgraded directory and the latest directory add-on package (which includes any schema changes).
  6. Import the LDIF file generated from the existing database.
  7. Modify existing data as needed.
  8. Import the modified LDAP objects into the directory.

Overview of Steps to Migrate Directory Data

The migration procedure consists of the following steps:

Managing Shadowed Directories When Migrating Directory Data

The migration procedure executes only on the primary directory. If you are performing the migration in a shadowed environment setup, then you must ensure that shadowing is terminated before running the migration script.

Perform the following migration procedures:

  1. Running the Migration Script
  2. Completing the Migration
  3. Updating the Original Host

DirX Deployment

In a DirX deployment, you must terminate the shadowing agreement by using the dirxadm tool as follows:

  1. Log in as user dirx and access the customize directory.
  2. su - dirx 
    
    cd customize
    
    
    
  3. Start dirxadm, perform a bind operation, and terminate the shadowing agreement.
  4. dirxadm
    
    dirxadm> sou bind.tcl
    
    dirxadm> ob terminate -dsa <dsa_name> -operationalbindingid <ob-id> 
    -bindingtype SOB
    
    dirxadm> exit
    
    
    

where <dsa_name> is the digital signature algorithm (DSA) of the partner (secondary) directory and <ob-id> is the operational binding ID. Both of these values were established when you established the shadowing agreement.

  1. Perform the following migration procedures:
  1. Running the Migration Script
  2. Completing the Migration
  3. Updating the Original Host

Updating DirX Secondary Directories

After moving the migrated directory into production, you must update the DirX secondary directories.

  1. Uninstall the current UMCdirxa package, and install the most recent one.
  2. Log in as user dirx and access the customize directory.
  3. su - dirx 
    
    cd customize
    
    
    
  4. Copy the dirxabbr-ext.UMC file.
  5. cp <dirx_inst_path>/customize/dirxabbr-ext.UMC 
    <dirx_inst_path>/client/conf/
    
    
    

where <dirx_inst_path> specifies the DirX installation directory.

  1. Create the access point of the secondary directory.
  2. dirxadm
    
    dirxadm> bind
    
    dirxadm> ob modownacp {AE={ /CN=UMC-DSA2}, PSAP={TS=DSA,                           
    NA='TCP/IP!internet=127.0.0.1+port=21100' } }
    
    dirxadm>exit
    
    
    
  3. Generate the SDX schema.
  4. dirxadm
    
    dirxadm>bind
    
    dirxadm> sou schema.adm
    
    dirxadm>exit
    
    
    
  5. Establish the shadowing agreements on secondary and primary hosts. Perform the following tasks on both secondary and primary host.
  6. su - dirx 
    
    cd customize
    
    dirxadm
    
    dirxadm> sou bind.tcl
    
    dirxadm> ob establish -dsa <dsa_name> -operationalbindingid <ob-id> 
    -bindingtype SOB 
    
    dirxadm> exit
    

Sun ONE Deployment

To turn off shadowing and restart the directory server for a Sun ONE deployment:

  1. Terminate the shadowing agreements before the migration procedure is executed.
  2. Complete the following tasks to migrate the primary directory:
  1. Running the Migration Script
  2. Completing the Migration
  3. Updating the Original Host
  1. Uninstall the primary directory server and all secondary directory servers.
  2. When the primary directory is up and running, set up the supplier directories and the shadowing agreements according to the documentation for Sun ONE Directory Server.

Preparing the Migration Host

The directory server software and its add-on packages listed in the following table must be installed on both the original host and the migration host.


Directory Server
Software
Add-On Package

DirX

Available from Siemens

UMCdirxa

Sun ONE (iPlanet)

Available from Sun Microsystems

UMCiDSa

The software and add-on packages should already be present on the original host.

See the SRC-PE Integration Guide for information about installing the DirX or Sun ONE software.

To install the required SRC packages on either host:

  1. From a UNIX window, log in as root.
  2. Load the SDX software disk 1.
  3. Start the Solaris software management tool.
  4. swmtool
    
    
    

The Admintool: Software window appears.

  1. Select and add the desired package(s).

See the Solaris man page for pkgadd for more information about this utility.

See Chapter 28, Installing the SRC Software on a Solaris Platform for an example of adding a package.

  1. For Sun ONE (iPlanet) only, perform that software's setup utility.

    NOTE: If the deployed software is earlier than Release 2.0.2, use the UMColdap or DirX-SV package from the Release 4.x SDX software CD. However, the UMColdapa and UMCdirxa add-on packages must be from SSC Release 2.0.

    NOTE: Ensure that the directory contents do not change after you save the database on the original host. Additionally, keep the stored directory archives in case the migration fails and you need to restart the migration procedure from the beginning.


Cloning the Directory Server

You must transfer the contents of the original directory to a cloned directory on the migration host. The procedure depends on the type of directory in your current deployment.

Cloning the DirX Directory Server

To  set up the DirX directory server on the migration host:

  1. On the original host, log in as user dirx, and access the customize subdirectory.
  2. cd customize
    
    
    
  3. On the original host, archive the database.
  4. dirxadm 
    
    dirxadm> source bind.tcl
    
    dirxadm> save -file /tmp/dirxdb
    
    
    
  5. Transfer the archive by using FTP into the /tmp directory on the migration host.
  6. On the migration host, log in as user dirx, and access the customize subdirectory.
  7. cd customize
    
    
    
  8. On the migration host, copy the abbreviation file as described below.

For SSC 2.x versions:

cp dirxabbr-ext.UMC2.0 ../client/conf/

For SDX 3.0 and higher versions:

cp dirxabbr-ext.UMC ../client/conf/

  1. On the migration host, verify that the DirX server is running. See your DirX documentation for details.
  2. On the migration host, restore the archive.
  3. dirxadm
    
    dirxadm> source bind.tcl
    
    dirxadm> restore -file /tmp/dirxdb
    

Cloning Sun ONE Directory Server (iPlanet)

To set up Sun ONE Directory Server (iPlanet) on the migration host:

  1. On the original host, log in as root.
  2. On the original host, access the database directory.

For SSC Release 3.x:

cd /opt/UMC/iDS/slapd-ssc

For SDX Release 4.0 and higher:

cd /opt/UMC/iDS/slapd-sdx

  1. On the original host, back up the database.
  2. db2bak /tmp/iDSbak
    
    
    
  3. On the original host, archive the database.
  4. tar cfv /tmp/iDSdb.tar /tmp/iDSbak/
    
    
    
  5. Transfer the archive by using FTP into the /tmp directory on the migration host.
  6. On the migration host, log in as root.
  7. On the migration host, verify that Sun ONE Directory Server (iPlanet) is shut down.
  8. On the migration host, extract the archive.
  9. tar xfv /tmp/iDSdb.tar
    
    
    
  10. On the migration host, access the database directory.

For SSC Release 3.x:

cd /opt/UMC/iDS/slapd-ssc

For SDX Release 4.0 and higher:

cd /opt/UMC/iDS/slapd-sdx

  1. On the migration host, restore the saved database.
  2. bak2db /tmp/iDSbak
    
    
    
  3. On the migration host, start Sun ONE Directory Server (iPlanet).
  4. /opt/UMC/iDS/etc/start-slapd
    

Installing the UMCmig Migration Package

The UMCmig package is provided in the SRC software distribution and includes a single migration procedure that handles all migration possibilities. See the Solaris man page for pkgadd or smc for information about using one of these utilities to add a package. By default, the migration files are installed in the /opt/UMC/migration directory.

Customizing Migration

You must modify the file /etc/migration.conf to provide the following information. Figure 27 shows a sample modified file.


Figure 27: Sample Edited etc/migration.conf File

Running the Migration Script

The entire migration is valid for a single directory deployment.

If the migration is in a large-scale deployment with a shadowed directory setup, before you run the migration script follow the instructions in Managing Shadowed Directories When Migrating Directory Data. After you have completed those tasks, return to this section and continue with the following procedure.

The migration script logs the migration steps in the file /opt/UMC/migration/etc/migration.log. You can check this file for migration errors.

To run the migration script on the migration host:

  1. On the migration host, log in.

If DirX is the deployed directory, log in as user dirx.

  1. Access the migration directory.
  2. cd /opt/UMC/migration
    
    
    
  3. Start the migration script.
  4. sh migrate.sh
    

Completing the Migration

Depending on your directory server, you may have additional steps to complete the migration.

DirX

For DirX, the migration is completed when the migration script successfully terminates. You can now transfer the migrated database to the original host.

Sun ONE (iPlanet)

For Sun ONE (iPlanet), the migration script displays additional steps that you must manually perform.

  1. Remove the Sun ONE add-on package.
  2. pkgrm UMCiDSa
    
    
    
  3. Remove the Sun ONE Directory instance from its installation directory.
  4. /opt/UMC/iDS/uninstall
    
    
    
  5. Install the latest Sun ONE Directory Server add-on package.
  6. pkgadd /cdrom/cdrom0/SDX/solaris/UMCiDSa
    
    
    
  7. Install the recommended Sun ONE Directory Server release. See the SRC-PE Release Notes for the latest recommended version.
  8. <Sun-ONE-bin-path>/setup -s -f /opt/UMC/conf/iDS/sdx.inf
    
    
    

where <Sun-ONE-bin-path> is the location of the Sun ONE Directory Server binaries.

  1. Configure Sun ONE Directory Server for the SRC software.

    NOTE: Do NOT load the sample database.


  2. /opt/UMC/conf/iDS/load
    
    
    
  3. Access the migration directory.
  4. cd /opt/UMC/migration
    
    
    
  5. Complete the migration.

    NOTE: This step is required only if you are migrating from a 3.x release to a 4.x or higher release.


  6. sh finalizeMigration.sh
    
    
    

When you have successfully completed these steps, you can then transfer the migrated database to the original host.

Updating the Original Host

There are two ways to move the migrated data into production:

  1. Remove the directory add-on package (UMCdirxa, UMColdapa, or UMCiDSa) to establish a clean directory environment.
  2. Remove the directory package.
  3. Install the directory server and add-on package from the latest SRC release.
  4. For DirX deployment
  5. cp <dirx_inst_path>/customize/dirxabbr-ext.UMC 
    <dirx_inst_path>/client/conf/
    
    
    

where <dirx_inst_path> specifies the DirX installation directory.

  1. For a Sun ONE Directory Server deployment, install and configure the directory server.
  1. Install the latest Sun ONE Directory Server add-on package.
  2. pkgadd /cdrom/cdrom0/SDX/solaris/UMCiDSa
    
    
    
  3. Install the recommended Sun ONE Directory Server release. See the SRC-PE Release Notes for the latest recommended version.
  4. <Sun-ONE-bin-path>/setup -s -f /opt/UMC/conf/iDS/sdx.inf
    
    
    

where <Sun-ONE-bin-path> is the location of the Sun ONE Directory Server binaries.

  1. Configure Sun ONE Directory Server for the SRC software.

    NOTE: Do NOT load the sample database.


  2. /opt/UMC/conf/iDS/load
    
    
    
  1. Transfer the data from the migrated computer to the original host. Follow the procedure for your directory.

See Cloning the Directory Server.

NOTE: For a DirX deployment, you must skip the step where you copy the abbreviation file, dirxabbr-ext.UMC20.



[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]