Moving DIT to a new master during migration
Hello,
I am in the process of migrating my schema v1 database to schema v2. In the course of this migration, I would like to make a new system the master server. The existing server hosts both the user directory and the configuration directory.
I was planning on simply exporting the existing server's DIT and importing it into the new server, however since this also includes configuration information, I am concerned that I might overwrite the configuration for the new server when I import the existing data into the new server's database.
What is the suggested process for moving a DS master from one server to another? I didn't find any reference to this on docs.sun.com.
Thanks,
Bill
[729 byte] By [
wgkorb] at [2007-11-26 9:39:17]
# 1
The suggested process would be to set up the new server as a master, and set up multi-master replication between the two, initializing the new server from the old servers database.
The old server will have multiple databases - possiblly a 'configuration' (o=NetscapeRoot) database, a o=internet database, and a user database. Multi-master replication only needs to be set up for the user and o=internet databases. You will need the o=internet data for commdirmig to do its work.
# 2
Thanks for the reply.
That makes sense for the most part. However, I would like my new server to assume the role of the configuration master, too. If I try to use this same trick, will I not lose configuration information from one of the two servers?
I'm assuming that when I set up the new server, it will get it's own configuration database, and I'll want to merge the configuration from the old server into the new server's database. In that case, perhaps I just need to generate an LDIF file of the o=NetscapeRoot suffix and import that into the new database?
BTW, I assume that I will also have to run the directory preparation tool on the new server before attempting to create the MMR replication agreement?
Thanks again,
Bill
# 3
> That makes sense for the most part. However, I would
> like my new server to assume the role of the
> configuration master, too. If I try to use this same
> trick, will I not lose configuration information from
> one of the two servers?
While doing this is possible, it is not recommended. What the best practice is for the configuration directory, is to have a configuration directory instance local to each and every messaging server, and to NOT replicate the configuration directory, and NOT have other data in the directory instance with the configuration.
However, having said that - if you really want to maintain a central configuration directory, and transfer it from one machine to the other ... yes, it's possible, but requires a lot more help and work that I can give here. Its best for you to use your local support resources to help you through this.
> I'm assuming that when I set up the new server, it
> will get it's own configuration database, and I'll
> want to merge the configuration from the old server
> into the new server's database.
You will get a new configuration directory instance only if you install it that way. You can install a new Messaging instance using an existing directory instance. Again, it's not recommended.
> In that case, perhaps
> I just need to generate an LDIF file of the
> o=NetscapeRoot suffix and import that into the new
> database?
Trying to do that is risky, because you will end up merging two config trees, that may well have conflicting data.
There used to be a 'merge configuration' option in the console the 5.x messaging servers used, that may well still be there.
> BTW, I assume that I will also have to run the
> directory preparation tool on the new server before
> attempting to create the MMR replication agreement?
Yes, you will. That is required to load the necessary objectclass and attribute definitions, as well as set up databases and indexes.
