1MIGRATE-DS-ADMIN.PL(8) System Manager's Manual MIGRATE-DS-ADMIN.PL(8)
2
6 migrate-ds-admin.pl - Admin Server and Directory Server Migration
7 script
8
10 migrate-ds-admin.pl [--options] -- [args]
11
13 Admin Server and Directory Server migration script - migrates Admin
14 Server and all Directory Server instances from older releases to the
15 current release.
16 This script will copy instances (data and configuration) from the old
18 server root directory to their new FHS locations. This script does a
19 copy only - the data in the old instances will be left untouched. The
20 old instances must be shutdown first to ensure that the databases are
21 copied safely. During migration your migrated instances will be
22 started.
23
25 A summary of options is included below:
26 --help This message
28 --version
30 Print the version and exit
31 --debug
33 Turn on debugging
34 --oldsroot
36 The old server root directory to migrate from
37 --actualsroot This is the old location of the old server root.
39 --silent
41 Use silent setup - no user input
42 --file=name
44 Use the file 'name' in .inf format to supply the default answers
45 --keepcache
47 Do not delete the temporary .inf file generated by this program
48 --logfile
50 Log migration messages to this file - otherwise, a temp file
51 will be used
52 --instance
54 By default, all directory server instances will be migrated.
55 You can use this argument to specify one or more (e.g. -i
56 slapd-foo -i slapd-bar) if you do not want to migrate all of
57 them.
58 --cross
60 See below.
61 For all options, you can also use the short name e.g. -h, -d, etc. For
63 the -d argument, specifying it more than once will increase the debug
64 level e.g. -ddddd
65 args: You can supply default .inf data in this format:
67 section.param=value
69 e.g.
71 General.FullMachineName=foo.example.com
73 or
75 "slapd.Suffix=dc=example, dc=com"
77 Values passed in this manner will override values in an .inf file given
79 with the -f argument. The only required argument is the password of
80 the Configuration Directory Administrator, which can be specified on
81 the command line like this:
82 migrate-ds-admin.pl General.ConfigDirectoryAdminPwd=thepassword
84 All other paramters needed for migration will be read from the old
86 Admin Server configuration.
87 actualsroot: This is used when you must migrate from one machine to
89 another. The usual case is that you have mounted the old server root
90 on a different root directory, either via a network mount, or by copy‐
91 ing a tarball made using a relative directory on the source machine to
92 the destination machine and untarring it.
93 For example: machineA is a 32bit machine, and you want to migrate your
95 servers to a new 64bit machine. Lets assume your old server root on
96 machineA was /opt/myds, and your new machine also wants to use a server
97 root of /opt/myds. There are a couple of different ways to proceed.
98 Either make a tarball of opt/myds from machineA using a relative path
99 (i.e. NOT /opt/myds) or use NFS to mount machineA:/opt/myds on a dif‐
100 ferent mount point (e.g. machineB:/migration/opt/myds).
101 If you do this, you should give the old "real" server root (/opt/myds)
103 as the --actualsroot argument, and use /migration/opt/myds for the
104 --oldsroot argument. That is, the oldsroot is the physical location of
105 the files on disk. The actualsroot is the old value of the server root
106 on the source machine.
107 cross: Also known as crossplatform, or 'c', or 'x'. This is when the
109 source machine is a different architecture than the destination
110 machine. In this case, only certain data will be available for migra‐
111 tion. Changelog information will not be migrated, and replicas will
112 need to be reinitialized (if migrating masters or hubs). This type of
113 migration requires that all of your old databases have been dumped to
114 LDIF format, and the LDIF file must be in the default database direc‐
115 tory (usually /opt/fedora-ds/slapd-instance/db), and the LDIF file must
116 have the same name as the database instance directory, with a ".ldif".
117 For example, if you have
118 /opt/fedora-ds/slapd-instance/db/userRoot/
120 and
121 /opt/fedora-ds/slapd-instance/db/NetscapeRoot/
122 you must first use db2ldif to export these databases to LDIF e.g.
124 cd /opt/fedora-ds/slapd-instance
126 ./db2ldif -n userRoot -a /opt/fedora-ds/slapd-instance/db/userRoot.ldif and
127 ./db2ldif -n NetscapeRoot -a /opt/fedora-ds/slapd-instance/db/NetscapeRoot.ldif
128 Then you must somehow make your old server root directory available on
130 the destination machine, either by creating a tar archive on the source
131 and copying it to the destination, or by network mounting the source
132 directory on the destination machine.
133
135 migrate-ds-admin.pl was written by the 389 Project.
136
138 Report bugs to http://bugzilla.redhat.com.
139
141 Copyright © 2008 Red Hat, Inc.
142 This manual page was written by Michele Baldessari
143 <michele@pupazzo.org>, for the Debian project (but may be used by oth‐
144 ers).
145 This is free software. You may redistribute copies of it under the
146 terms of the Directory Server license found in the LICENSE file of this
147 software distribution. This license is essentially the GNU General
148 Public License version 2 with an exception for plug-in distribution.
149 May 18, 2008 MIGRATE-DS-ADMIN.PL(8)