Thanks William!
Fernando Fuentes
Supervisor & Senior Systems Administrator
Email: ffuentes@xxxxxxxxxxx
American Alloy Steel, Inc.
Houston, Texas
Website: http://www.aasteel.com
Phone: 713-744-4222
Fax: 713-300-5688
On 10/3/19 5:19 PM, William Brown wrote:
On 4 Oct 2019, at 03:53, Fernando Fuentes <ffuentes@xxxxxxxxxxx> wrote:
I run 389ds 1.3.8 and there is an update to 1.3.9. Is it safe to update?
Yes! We have a great QE team and they test our updates to make sure they are safe.
If you have concerns, before you start the upgrade take a VM/LVM snapshot, and also be sure to run "db2bak".
We support replication between major releases normally (IE 1.2.x to 1.3.x OR 1.3.x to 1.4.x). This can be run for a while, but generally we don't advise more than a few months, as it's always better to keep your topology on the same versions.
Also if I have a Replication server with a Master and read only slave, what is the procedure or best practice to update?
Thanks!
It's really up to you. Having a plan, including backout strategy is always wise.
If this was my environment I would probably make my plan something like:
* backup (db2bak) read only replica (avoid use of the word slave these days :) )
* snapshot the read only replica (vm/lvm) if possible
* perform the upgrade on the replica
* run a sanity/acceptance test - do client applications still work, can you search for users, etc.
* wait a few days
Now do the same on the read-write server.
The backout plan is:
* If the acceptance test fails, revert the snapshot. You may need to perform a nsds5startreplicarefresh to reset the read-only replication information as this may cause a replication desync.
* If the snapshot roll back fails in some way, destroy the host and rebuild a new ro/rw replica with the content from db2bak/dse.ldif etc.
Hope that helps,
Regards,
--
Fernando Fuentes
Supervisor & Senior Systems Administrator
Email: ffuentes@xxxxxxxxxxx
American Alloy Steel, Inc.
Houston, Texas
Website: http://www.aasteel.com
Phone: 713-744-4222
Fax: 713-300-5688
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
—
Sincerely,
William Brown
Senior Software Engineer, 389 Directory Server
SUSE Labs
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
