RE: [OpenAFS] Does vos release/volume replication always initiates data transfer from RW site?

2018-08-06 Thread Ximeng Guan
9 AM To: Ximeng Guan ; openafs-info@openafs.org Subject: Re: [OpenAFS] Does vos release/volume replication always initiates data transfer from RW site? In OpenAFS, all of the "smarts" are in the vos process. This process has no knowledge of the network topology which is why OpenAFS has diffic

Re: [OpenAFS] Does vos release/volume replication always initiates data transfer from RW site?

2018-08-06 Thread Jeffrey Altman
On 8/6/2018 12:12 PM, Ximeng Guan wrote: > Indeed if we have two RO replicas at Site B and RW at site A, subsequent > release will be twice as consuming, unless "vos release" can be made to be > even smarter, such that data is "relayed" among RO sites instead of being > broadcasted from the RW

RE: [OpenAFS] Does vos release/volume replication always initiates data transfer from RW site?

2018-08-06 Thread Ximeng Guan
nal Message- From: openafs-info-ad...@openafs.org [mailto:openafs-info-ad...@openafs.org] On Behalf Of Todd Lewis Sent: Monday, August 6, 2018 5:45 AM To: openafs-info@openafs.org Subject: Re: [OpenAFS] Does vos release/volume replication always initiates data transfer from RW site? Giv

Re: [OpenAFS] Does vos release/volume replication always initiates data transfer from RW site?

2018-08-06 Thread Todd Lewis
Given the two-site scenario below, and successful manual replication as outlined by Jeffrey further below, you then have two RO volumes at site B as desired. If "vos release" is enough of a problem to warrant this manual intervention, then won't subsequent releases from the RW site A now be twice

Re: [OpenAFS] Does vos release/volume replication always initiates data transfer from RW site?

2018-08-06 Thread Jeffrey Altman
On 8/5/2018 11:58 PM, Ximeng Guan wrote: > Hello, > > We have one cell covering two sites. The WAN bandwidth between the two > sites is relatively low, so we use volume replication to speed up the > access. > > Those replicated volumes are often large in size. So replication to the > remote site