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.
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:
- Physical attributes, such as memory and CPU, equal to or greater than those available on the original host.
- A Solaris version compatible with the new SRC release.
- The Solaris patches appropriate to the Solaris version.
- The Python runtime environment appropriate to the SRC release from which you are migrating. This is the SMCpython package provided in the SRC software distribution for that release.
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
- Export and convert any existing LDAP objects into a file.
- Delete the existing objects from the LDAP directory.
- Delete all obsolete schema elements from the global directory schema.
- Modify existing schema elements as needed, and add the new schema elements to the global directory schema.
- Extend the access-control schema. For DirX only, extend the directory information tree (DIT) structure and DIT content rules.
- Modify existing data as needed.
- Import the modified LDAP objects into the directory.
Script Tasks With Directory Server Upgrade
- Export and convert any existing LDAP objects into a file.
- Delete the existing objects from the LDAP directory.
- 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.
- Remove the existing LDAP directory instance and the corresponding directory add-on package.
- Install the upgraded directory and the latest directory add-on package (which includes any schema changes).
- Import the LDIF file generated from the existing database.
- Modify existing data as needed.
- 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
- Preparing the Migration Host
- Cloning the Directory Server
- Installing the UMCmig Migration Package
- Migrating Directory Data on Solaris Platforms
- Running the Migration Script
- Completing the Migration
- Updating the Original Host
NOTE: If disk shadowing is employed, you must ensure that shadowing is stopped. See Managing Shadowed Directories When Migrating Directory Data for further details.
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:
DirX Deployment
In a DirX deployment, you must terminate the shadowing agreement by using the dirxadm tool as follows:
- Log in as user
dirx
and access the customize directory.su - dirx
cd customize
- Start dirxadm, perform a bind operation, and terminate the shadowing agreement.
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.
Updating DirX Secondary Directories
After moving the migrated directory into production, you must update the DirX secondary directories.
- Uninstall the current UMCdirxa package, and install the most recent one.
- Log in as user
dirx
and access the customize directory.su - dirx
cd customize
- Copy the dirxabbr-ext.UMC file.
cp <dirx_inst_path>/customize/dirxabbr-ext.UMC <dirx_inst_path>/client/conf/
where <dirx_inst_path> specifies the DirX installation directory.
- Create the access point of the secondary directory.
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
- Generate the SDX schema.
dirxadm
dirxadm>bind
dirxadm> sou schema.adm
dirxadm>exit
- Establish the shadowing agreements on secondary and primary hosts. Perform the following tasks on both secondary and primary host.
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:
- Terminate the shadowing agreements before the migration procedure is executed.
- Complete the following tasks to migrate the primary directory:
- Uninstall the primary directory server and all secondary directory servers.
- 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.
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:
- From a UNIX window, log in as
root
.- Load the SDX software disk 1.
- Start the Solaris software management tool.
swmtool
The Admintool: Software window appears.
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.
- For Sun ONE (iPlanet) only, perform that software's setup utility.
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:
- On the original host, log in as user
dirx
, and access the customize subdirectory.cd customize
- On the original host, archive the database.
dirxadm
dirxadm> source bind.tcl
dirxadm> save -file /tmp/dirxdb
- Transfer the archive by using FTP into the /tmp directory on the migration host.
- On the migration host, log in as user
dirx
, and access the customize subdirectory.cd customize
- On the migration host, copy the abbreviation file as described below.
cp dirxabbr-ext.UMC2.0 ../client/conf
/For SDX 3.0 and higher versions:
cp dirxabbr-ext.UMC ../client/conf/
- On the migration host, verify that the DirX server is running. See your DirX documentation for details.
- On the migration host, restore the archive.
dirxadmdirxadm> source bind.tcldirxadm> restore -file /tmp/dirxdbCloning Sun ONE Directory Server (iPlanet)
To set up Sun ONE Directory Server (iPlanet) on the migration host:
cd /opt/UMC/iDS/slapd-ssc
For SDX Release 4.0 and higher:
cd /opt/UMC/iDS/slapd-sdx
- On the original host, back up the database.
db2bak /tmp/iDSbak
- On the original host, archive the database.
tar cfv /tmp/iDSdb.tar /tmp/iDSbak/
- Transfer the archive by using FTP into the /tmp directory on the migration host.
- On the migration host, log in as
root
.- On the migration host, verify that Sun ONE Directory Server (iPlanet) is shut down.
- On the migration host, extract the archive.
tar xfv /tmp/iDSdb.tar
- On the migration host, access the database directory.
cd /opt/UMC/iDS/slapd-ssc
For SDX Release 4.0 and higher:
cd /opt/UMC/iDS/slapd-sdx
- On the migration host, restore the saved database.
bak2db /tmp/iDSbak
- On the migration host, start Sun ONE Directory Server (iPlanet).
/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.
- Host—IP address of the migration host. In general, this is localhost because you have cloned the production system.
- Administrator distinguished name (DN)
- Administrator password—The current administrator's password is specified as a value of the type CurrentPwd. If the password changes between the previously deployed and current releases, the value of NewPwd must be different from the CurrentPwd value. Otherwise, the values are identical.
- Deployed directory—The migration procedure varies depending on the directory server. Only the DirX directory server is supported for the migration from SSC 2.x releases. If you migrate from SDX 3.0.x to SDX 3.x, iPlanet Directory Server 4.1.x is also supported.
- Trap community and version—If you are migrating from SSC 3.0.x, you must provide values for these in the existing trap entries.
![]()
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:
If DirX is the deployed directory, log in as user
dirx
.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.
- Remove the Sun ONE add-on package.
pkgrm UMCiDSa
- Remove the Sun ONE Directory instance from its installation directory.
/opt/UMC/iDS/uninstall
- Install the latest Sun ONE Directory Server add-on package.
pkgadd /cdrom/cdrom0/SDX/solaris/UMCiDSa
- Install the recommended Sun ONE Directory Server release. See the SRC-PE Release Notes for the latest recommended version.
<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.
- Configure Sun ONE Directory Server for the SRC software.
/opt/UMC/conf/iDS/load
- Access the migration directory.
cd /opt/UMC/migration
- 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.
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:
- Turn off the original host and replace it with the migration host. This method requires that both hosts be initially set up in the same manner, including hostname and IP address.
- Transfer the migrated data from the migration host back to the original host. This method requires the following steps:
- Remove the directory add-on package (UMCdirxa, UMColdapa, or UMCiDSa) to establish a clean directory environment.
- Remove the directory package.
- Install the directory server and add-on package from the latest SRC release.
- For DirX deployment
cp <dirx_inst_path>/customize/dirxabbr-ext.UMC <dirx_inst_path>/client/co
nf/where <dirx_inst_path> specifies the DirX installation directory.
- Install the latest Sun ONE Directory Server add-on package.
pkgadd /cdrom/cdrom0/SDX/solaris/UMCiDSa
- Install the recommended Sun ONE Directory Server release. See the SRC-PE Release Notes for the latest recommended version.
<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.
- 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.