On 08/22/2013 10:40 AM, Chris Taylor wrote:
So if I follow this discussion correctly I should do the following steps.
1.Build my new server with OS and DS package
2.Edit the schema for my custom attributes
3.Setup a replication between my old server and the new server (as MMR)
4.Create a replication agreement between the two new servers (as MMR)
5.Remove the replication agreement between the old and new server
6.Run CLEANALLRUV to remove the old replication agreements
CLEANALLRUV doesn't remove replication agreements, it removes the
replication meta-data associated with the old servers.
Does this sound about right?
Yes.
Chris
*From:*389-users-bounces@lists.fedoraproject.org
[mailto:389-users-bounces@lists.fedoraproject.org] *On Behalf Of *Rich
Megginson
*Sent:* Wednesday, August 21, 2013 3:40 PM
*To:* Michael Lang
*Cc:* General discussion list for the 389 Directory server project.
*Subject:* Re: [389-users] Best way to upgrade DS servers
On 08/21/2013 01:36 PM, Michael Lang wrote:
Am 21.08.2013 21:31, schrieb Rich Megginson:
On 08/21/2013 01:03 PM, Michael Lang wrote:
Am 21.08.2013 19:25, schrieb Chris Taylor:
I am looking at replacing our two CentOS DS servers
which are 5.9 with some on the 6.4 channel. What is
the best way to transition all the data over? Should I
build them separately and import everything via ldif
files, or can I add them as consumers or in our setup
as another master in our MMR setup.
Chris,
what I've been expirencing until now, unless you replace
the DS with exactly the same machine (name, ...)
Why?
you should try an LDIF export first and use a VirtualMachine
to import your content to see any possible problems (schema
violations,...)
Why not install the new servers on the new machines as
replication masters and replicate the data to them?
you would also need to remove the replication later on (not only
in the GUI, the DS keeps a lot of logs and traces for every
replication you setup)
Yes, that's what CLEANALLRUV is for -
http://port389.org/wiki/Howto:CLEANRUV
beside, I would also consider the ACL's an other Database related
settings which will not be exported by a LDIF dump and will only be
"copied" if you can use the Backup functionality.
?
for the consumer setup you would still need to extend the schema first
if you customized it ...
Yes.
regards
mIke
To add a little complexity I have also added some RADIUS attributes to
the schema so I am assuming that, those will need to be added before I
setup any replication.
Any advice would be great.
Thanks,
Chris
--
389 users mailing list
389-users(a)lists.fedoraproject.org <mailto:389-users@lists.fedoraproject.org>
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users(a)lists.fedoraproject.org <mailto:389-users@lists.fedoraproject.org>
https://admin.fedoraproject.org/mailman/listinfo/389-users
--
389 users mailing list
389-users(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/389-users