6 Migrating or upgrading to HP-UX Directory Server from Netscape or Red Hat Directory Server

This chapter provides information about moving to HP-UX Directory Server 8.1 from Netscape Directory Server 6.11 or 6.21, or from Red Hat Directory Server 7.1 or 8.0.

In this chapter, moving to HP-UX Directory Server 8.1 from Netscape Directory Server 6.11 or 6.21, or from Red Hat Directory Server 7.1, is referred to as a migration; the two versions exist side-by-side during the migration while the data and configuration from the old server are copied over to the new 8.1 server. Migrations are discussed in “Migrating from Netscape Directory Server 6.x, or from Red Hat Directory Server 7.1” (page 47).

In contrast, moving to HP-UX Directory Server 8.1 from Red Hat Directory Server 8.0 is referred to as an upgrade; the new version completely replaces the old version. Upgrades are discussed in “Upgrading from Red Hat Directory Server 8.0” (page 53)

6.1Migrating from Netscape Directory Server 6.x, or from Red Hat Directory Server 7.1

This section explains the procedure for moving to HP-UX Directory Server 8.1 from Netscape Directory Server 6.11 or 6.21, or from Red Hat Directory Server 7.1.

NOTE: Before migrating to HP-UX Directory Server 8.1, you must either disable SSL in the legacy server or create a PIN file so that the legacy server can start up without interaction. To disable SSL, edit the legacy server's dse.ldif file and set the nsslapd-securityparameter to off. To create a PIN file, follow the instructions in the Administrator Guide for the legacy server.

NOTE: Most examples in this section assume the legacy server is Red Hat Directory Server 7.1, with the default server root directory path given as /var/opt/netscape/server7. For the Netscape Directory Server (6.11 or 6.21), you can substitute the following Netscape Directory Server default path in these examples: /var/opt/netscape/servers.

6.1.1 Tasks to perform before migrating

For the safety of the Directory Server data, perform the following tasks before beginning to migrate the Directory Server instances:

1.Shut down all Directory Server instances and the Administration Server, as described in “Starting and stopping servers” (page 44).

2.For servers that have a different configuration directory, make sure that the Directory Server Console write operations are moved from the configuration directory to the server itself, following the steps described in “Configuring the Directory Server Console” (page 47).

CAUTION:

Be sure that the legacy Directory Server instance is not running when you start the migration. The new HP-UX Directory Server instance will use the same port numbers, and the migration process may inadvertently perform updates on the legacy instance instead of the new instance.

6.1.1.1 Configuring the Directory Server Console

If you have a multi-master replication setup that replicates o=NetscapeRoot between the two master servers, server1 and server2, then by default, writes made through server2's Directory Server Console are written to server1, then replicated over. Modify the Directory

6.1 Migrating from Netscape Directory Server 6.x, or from Red Hat Directory Server 7.1

47

Page 47
Image 47
HP UX Direry Server manual Tasks to perform before migrating, Configuring the Directory Server Console

UX Direry Server specifications

HP UX Directory Server is a robust and scalable solution designed for managing directory information within enterprise networks. Developed by Hewlett-Packard (HP), this server offers an extensive set of features tailored to meet the needs of organizations that require an efficient way to store, manage, and retrieve identity and access data.

One of the key features of HP UX Directory Server is its ability to handle large directories with significant volumes of data. Built on a highly optimized architecture, it provides excellent performance and can support millions of entries without sacrificing speed or reliability. This capability makes it an ideal choice for large-scale deployments in enterprises that require high availability and responsiveness.

In addition to its scalability, HP UX Directory Server supports a wide range of protocols, including LDAP (Lightweight Directory Access Protocol), which ensures seamless integration with diverse applications and systems across various platforms. The server maintains standards compliance, which facilitates interoperability and simplifies administration tasks.

Security is a top priority for HP UX Directory Server, offering an array of features to protect sensitive information. It supports secure data transmission via TLS/SSL protocols, ensuring encrypted communication between clients and servers. Advanced access controls allow administrators to define fine-grained permissions, helping to safeguard directory data against unauthorized access.

Another salient feature of HP UX Directory Server is its replication capabilities. The server can replicate directory data across multiple instances, ensuring data consistency and availability in distributed environments. This feature is essential for businesses operating across different geographical locations or requiring failover solutions for disaster recovery.

HP UX Directory Server also comes equipped with tools for data management, including an intuitive administration console for configuring and monitoring the server. Additionally, it offers customizable schema capabilities, enabling organizations to tailor the directory structure to fit their specific needs.

Integration with existing identity management solutions is streamlined through connectors and APIs, allowing organizations to extend their directory services and enhance user experience.

In summary, HP UX Directory Server is a powerful directory management solution that combines scalability, security, and integration flexibility. Its support for industry standards, advanced replication, and comprehensive administrative tools makes it an essential asset for organizations seeking to manage identity and access efficiently. By leveraging this technology, businesses can improve their operational efficiency and ensure a secure and organized approach to directory management.