To supplement Mark's response. I advise that you setup a "parallel" testing
infrastructure that's the same as what you will configure, so that you can understand
the processes of the replication/export-import, and how to configure the 389-ds instances
on RHEL8.
It's also worth reviewing the dse.ldif on the existing 1.2.x instances to see what
configurations have been set, plugins, etc. Not everything will need to be copied from the
1.2.x instance as there are many improvements in 1.4.x around how we configure the
instance, but it's worth doing to be sure.
If you need any further advice or help, please let us know!
On 8 Jan 2020, at 01:46, Jeffrey Westgate
<Jeffrey.Westgate(a)arkansas.gov> wrote:
Thank you Mark. We're looking at the docs you sent, and a few other things.
Appreciate the quick response.
From: Mark Reynolds <mreynolds(a)redhat.com>
Sent: Tuesday, January 7, 2020 8:27 AM
To: General discussion list for the 389 Directory server project.
<389-users(a)lists.fedoraproject.org>; Jeffrey Westgate
<Jeffrey.Westgate(a)arkansas.gov>
Subject: Re: [389-users] Need Migration assist, please
On 1/7/20 9:09 AM, Jeffrey Westgate wrote:
> we are running "389-Directory/1.2.11.15 B2017.101.1347" on a Scientific
Linux 6.9 VM. We have a 2 server cluster running, and have for several years, with very
little intervention required.
>
> we are wanting to move to RHEL8, and the latest (stable) 389DS
>
> We have questions (as the existing system was set up by a late employee of immense
knowledge of things computerized):
> - is the latest 389DS (stable version) compatible with RHEL8
> - how do we migrate the user database
>
> Been looking through the documents, but I'm not finding much to help.
In the installation guide there are two methods for migrating, replication and
export/import:
https://access.redhat.com/documentation/en-us/red_hat_directory_server/11...
Now there are no significant differences between 1.2.11 and 1.4.x that require any
special migration steps. You just need to prepare/configure the new RHEL 8 server to
match your old server prior to migration. Using the replication method you don't
really have any downtime, so this is the preferred path, but both techniques work fine.
HTH,
Mark
>
> --
> Jeff
> UNIX/Linux admin
>
>
>
> _______________________________________________
> 389-users mailing list --
> 389-users(a)lists.fedoraproject.org
>
> To unsubscribe send an email to
> 389-users-leave(a)lists.fedoraproject.org
>
> Fedora Code of Conduct:
>
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
>
> List Guidelines:
>
https://fedoraproject.org/wiki/Mailing_list_guidelines
>
> List Archives:
>
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproje...
--
389 Directory Server Development Team
_______________________________________________
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproje...
—
Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server
SUSE Labs