Chapter 6. Migrating from Previous Versions
47
•
Section 6.3.1
Migrating a Standalone Server
•
Section 6.3.2
Migrating a 6.x Replicated Site
•
Section 6.3.3
Migrating a 6.x Multi-Master Deployment
•
Section 6.3.4
Managing Console Failover
.
6.3.1. Migrating a Standalone Server
Once you have backed up your critical configuration information, do the following to migrate a server:
1. Stop your legacy Directory Server.
If you do not stop the legacy Directory Server, the migration script does it for you.
2. On
the
machine
where
your
legacy
Directory
Server
is
installed,
install
a
new
7.x
Directory
Server.
This
installation
process
is
described
in
Chapter 3
Using Express and Typical Installation
or
Chapter 4
Silent Installation and Instance Creation
.
Use the same port numbers as your legacy production server if you want to ensure that any direc-
tory clients that have static configuration information (including Directory Server port numbers)
continue to work.
3. Run the migration script.
As root user, change directory to
serverRoot
/bin/slapd/admin/bin
. Then enter the fol-
lowing command:
migrateInstance7 -D
rootDN
-w
password
-p
port
-o
oldInstancePath
-n
newInstancePath
Where:
•
rootDN
is the Directory Server 7.x user DN with root permissions, such as Directory Man-
ager.
•
password
is the password for Directory Manager in Directory Server 7.x.
•
port
is the LDAP port number assigned to Directory Server 7.x.
•
oldInstancePath
is the path to the installation directory of the legacy Directory Server
(for example,
/opt/redhat-ds/server6/slapd-
serverID
).
•
newInstancePath
is the path to the installation directory of Directory Server 7.x (for
example,
/opt/redhat-ds/servers/slapd-
serverID
).
The following is an example of a command you would use to migrate an instance of Directory
Server 6.21 to Directory Server 7.1:
migrateInstance7 -D cn=Directory Manager -w secret -p 389 \
-o /opt/redhat-ds/server621/slapd-phonebook \
-n /opt/redhat-ds/servers/slapd-phonebook \
This command appears on one line in usage. The slashes
\
are used to wrap the line for printing,
and should be removed when using the command.
4. Follow the prompts. For example, if you’re prompted to provide a path and filename for your
backup directory, enter one or accept the default.
The migration process starts. At the end of migration, your legacy Directory Server is migrated. Ad-
ditionally, as a result of this migration, a new Directory Server 7.x instance is installed using the
configuration information obtained from your legacy Directory Server; the data from your old server
is migrated to the new server; and the new server is started.
A sample output in Example 6-1 shows a migration of Directory Server 6.21 to Directory Server 7.1.
The migration script detects three backends,
backend1
,
backend2
, and
userRoot
, which exist in
Summary of Contents for DIRECTORY SERVER 7.1
Page 1: ...Red Hat Directory Server 7 1 Red Hat Directory Server Installation Guide ...
Page 28: ...22 Chapter 2 Computer System Requirements ...
Page 36: ...30 Chapter 3 Using Express and Typical Installation ...
Page 48: ...42 Chapter 4 Silent Installation and Instance Creation DisableSchemaChecking No ...
Page 64: ...58 Chapter 6 Migrating from Previous Versions ...
Page 70: ...64 Chapter 7 Troubleshooting ...
Page 94: ...88 Glossary ...