17.2 Migrating Driver Configuration Data to a New Server

If you have added a new server (right-click the Identity Vault and select New > Server), you might need to migrate the server data from an existing driver set to the new server. You can do this in one of three ways:

After the server data is migrated, you must redeploy the driver set to the new server in order for the server to become active. For more information, see Deploying a Project to an Identity Vault.

17.2.1 Using the Server Migration Wizard to Migrate the Driver Set

Use the Server Migration Wizard to migrate server-specific data in an existing driver set to a new server. The Server Migration Wizard copies the following server-specific information for the driver set and associated drivers:

  • Global configuration values (GCVs)

  • Engine control values (ECVs)

  • Named passwords

  • Driver authentication information

  • Driver startup option

  • Driver parameters

  1. From the Outline view, right-click the server with the associated driver set you want to migrate, then select Migrate.

    Select Migrate to launch the Server Migration wizard

    The Server Migration overview page explains that you are migrating a driver set from its source server to a target server along with its server-specific data.

  2. Click Next.

  3. On the Select Target Server page, select the server targeted for driver set migration and select Next.

    The Target Server list shows only servers that are not presently associated with any driver set and have an Identity Manager version that is equal to or newer than the source server.

  4. In the Driver Startup Option Settings page, select the server that you want to be active.

    Selecting the driver startup options

    The default selection is Make the target server active. This option copies the current driver startup settings from the source server to the target server and disables all of the drivers on the source server.

    The Keep the source server active option copies the current driver startup settings from the source server to the target server and then disables the drivers on the target server.

    The Make both target and source servers active option copies the current driver startup settings from the source server to the target server and does not disable any drivers on either server. This option is not recommended, because having all service queues active on both servers causes the servers to run the same tasks, which can produce unpredictable behavior.

    Settings in the Driver Startup Option Settings page only affect the DirXML-DriverStartOption attribute on drivers and not the migration of other server data. You can also set the driver startup options on the driver’s Properties > Driver Configuration > Startup Options tab. Driver startup options are Auto Start, Manual, and Disabled.

  5. Select Migrate.

    The wizard copies the server-specific information for the driver set and associated drivers to the target server while displaying a progress bar. When the migration finishes, you see The server has been successfully migrated!

  6. Click Close to close the Server Migration Wizard.

  7. After the wizard closes, right-click the driver set object in the Outline view and select Live > Deploy.

  8. If necessary, fill in any needed information in the Identity Vault Credentials window to authenticate to the Identity Vault, then click OK.

    You see the Operation In Progress window, followed by the Deployment Summary page, which shows what is being deployed to the Identity Vault.

  9. Click Deploy.

  10. If you see errors on the Deployment Results page, click the error to see a summary of the cause and possible solutions. Click OK to close.

17.2.2 Migrating a Driver Set to a Server in a Different Tree

For this procedure, assume that you have created a new tree and server, but you want to use an existing driver set.

  1. Right-click the Identity Vault in the Modeler or Outline view and select Properties.

  2. In the Configuration section, edit the Host, Username, and Password entries to connect to the new tree, then click OK.

    Change the authentication information to the new tree
  3. Right-click the driver set in the Modeler or Outline view and select Properties.

  4. In the General section, edit the Deploy Context to reflect the container where you want to store the driver set. Type the name of the correct container or use the Browse icon to find the new container, then click OK.

    Edit the Deploy Context
  5. Right-click the server object in the Outline view and select Properties.

  6. Under the General > Properties section, edit the Name and Context entries to match the server in the new tree, then click OK.

  7. Redeploy the driver set to the new server by right-clicking the driver set object in the Modeler or Outline view and selecting Live > Deploy.

    You see the Operation In Progress window, followed by the Deployment Summary page, which shows what is being deployed to the new Identity Vault.

  8. Click Deploy.

  9. If you see errors on the Deployment Results page, click the error to see a summary of the cause and possible solutions. Otherwise, click OK to close.

    All server-specific data for the driver set is copied to the new server on the new tree.

17.2.3 Migrating Server Data for Each Driver

Although using the Server Migration Wizard is the preferred method, you can also migrate server data for a single driver in the driver set. You can either perform this action for each driver in the driver set, or use the Server Migration Wizard as described in Using the Server Migration Wizard to Migrate the Driver Set.

  1. Right-click a driver in the Outline view and select Copy > Server-Specific Settings.

    Migrating server data for a driver.
  2. In the Copy Server Data from Driver.Driver Set window, select the source server. This is the server whose data is copied to the selected targets.

  3. Under the Select the drivers/servers to copy to entry, select the target driver or drivers on the target server that you want to copy to. This example selects the Active Directory driver as the target driver on the Terabyte5.novell target server.

    IMPORTANT:Some server data is specific to a driver type, but other data, like the driver startup option, is not. Know what you want to accomplish before copying one driver’s server data to other driver types. Otherwise, drivers on the target server might behave erratically or fail.

  4. In the Select replica data you want to copy section, select the data you want to copy to the target server. The copied data includes:

    • Global configuration values (GCVs)

    • Named passwords

    • Driver authentication information

    • Driver startup option

    • Driver parameters

  5. After you select the data, click OK, then click OK in the Complete window.

    You must perform this action for each driver in the driver set, or use the Server Migration Wizard.