[8549] in Info-AFS_Redistribution
Re: Marking a DB server to never be the sync site
daemon@ATHENA.MIT.EDU (Paul Blackburn)
Wed Mar 14 03:48:10 2001
Message-ID: <3AAF2DEF.50D7E0C6@hursley.ibm.com>
Date: Wed, 14 Mar 2001 08:38:07 +0000
From: Paul Blackburn <mpb@hursley.ibm.com>
MIME-Version: 1.0
To: info-afs@transarc.com
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Jeff Blaine wrote:
> I am 99% sure that the answer to this is "There is no way.", but I am
> going to ask anyway:
>
> Is there any way to mark a particular DB server as never allowed to be
> the sync site?
>
> We will have 5 DB servers soon (2 of those at remote sites) and would
> very much like the servers at the remote sites to never be allowed to
> become the sync site. Those 2 servers have lower IP addresses than
> our "core" 3 DB servers where 80% of all AFS work is done at HQ.
>
> Suggestions? Comments?
I haven't tried this but....
What would happen if the first three db servers have the same
/usr/afs/etc/CellServDB with only those three db servers.
Then, for the two remote db servers, you have all 5 db servers
listed in their /usr/afs/etc/CellServDB.
I believe that the first three db servers would only be able to
select a sync site candidate from the three. Meanwhile, the
two remote db servers would be able to keep in sync because
they can access the first three db servers.
Would this work?
Does the sync site push date to the other db servers or is it pulled?
Would the votes from the 2 remote db servers be ignored by the first 3?
Can someone explain how Ubik works?
--
cheers
paul http://acm.org/~mpb
