Re: Replica ID management

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



n Mon, Mar 26, 2012 at 01:15:18PM -0400, mjames@xxxxxxxxxxxx wrote:
>    @Ryan, thanks! That’s an interesting solution. And I thought of another
>    question. Do the replica IDs need to be unique across all databases?

Whether or not there's a technological need, consider the advantage of having a single replica ID associated with a single database on a single host when you're reading your error logs.
 
>     
> 
>    From: 389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx
>    [mailto:389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Groten,
>    Ryan
>    Sent: Monday, March 26, 2012 1:08 PM
>    To: 389-users@xxxxxxxxxxxxxxxxxxxxxxx
>    Subject: Re:  Replica ID management
> 
>     
> 
>    I used the last set of digits from each servers ip address.  That ensures
>    uniqueness in my environment only because all my DS’s are in the same
>    subnet.
> 
>     
> 
>    From: [1]389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx
>    [2][mailto:389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of
>    [3]mjames@xxxxxxxxxxxx
>    Sent: Monday, March 26, 2012 10:53 AM
>    To: [4]389-users@xxxxxxxxxxxxxxxxxxxxxxx
>    Subject:  Replica ID management
> 
>     
> 
>    Happy Monday, group. This seems like it should be obvious. When I set up a
>    new replication using the console, I’m prompted to enter a unique replica
>    ID. How can I tell if the ID I choose is unique? Is there a best practice
>    for replica ID management?
> 
>     
> 
>    Thanks, Mike
> 
>     
> 
>    --------------------------------------------------------------------------
> 
>    This communication, including any attached documentation, is intended only
>    for the person or entity to which it is addressed, and may contain
>    confidential, personal and/or privileged information. Any unauthorized
>    disclosure, copying, or taking action on the contents is strictly
>    prohibited. If you have received this message in error, please contact us
>    immediately so we may correct our records. Please then delete or destroy
>    the original transmission and any subsequent reply.
> 
> References
> 
>    Visible links
>    1. mailto:389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx
>    2. mailto:[mailto:389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx]
>    3. mailto:mjames@xxxxxxxxxxxx
>    4. mailto:389-users@xxxxxxxxxxxxxxxxxxxxxxx

> --
> 389 users mailing list
> 389-users@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/389-users

--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users



[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux