librelist archives

« back to archive

Replicating repositories to other sites

Replicating repositories to other sites

From:
Petros Moisiadis
Date:
2014-03-07 @ 13:02
Since I have had problems with using NFS to store repositories to a
remote site, I am planning a solution of storing the repositories
locally and then replicating them to other, remote places.
What is the best way to replicate attic repositories to remote sites? I
am thinking to use rsync for that purpose. Is it a good choice? Are
there any better choices or any issues to consider if I go for rsync?

Re: [attic] Replicating repositories to other sites

From:
Jonas Borgström
Date:
2014-03-07 @ 14:11
On 2014-03-07 14:02, Petros Moisiadis wrote:
> Since I have had problems with using NFS to store repositories to a
> remote site, I am planning a solution of storing the repositories
> locally and then replicating them to other, remote places.
> What is the best way to replicate attic repositories to remote sites? I
> am thinking to use rsync for that purpose. Is it a good choice? Are
> there any better choices or any issues to consider if I go for rsync?

Yeah, rsync should work well. You just need to figure out a way to take
a read lock on the repository before invoking rsync to avoid issues with
concurrent access.

A good addition to this, albeit a bit resource hungry would be to run
"attic check --repository-only $REPO" before rsync. That way you would
avoid overwriting your good copy with a bad copy in case of silent data
corruption.

/ Jonas

Re: [attic] Replicating repositories to other sites

From:
Petros Moisiadis
Date:
2014-03-07 @ 17:18
On 03/07/14 16:11, Jonas Borgström wrote:
> On 2014-03-07 14:02, Petros Moisiadis wrote:
>> Since I have had problems with using NFS to store repositories to a
>> remote site, I am planning a solution of storing the repositories
>> locally and then replicating them to other, remote places.
>> What is the best way to replicate attic repositories to remote sites? I
>> am thinking to use rsync for that purpose. Is it a good choice? Are
>> there any better choices or any issues to consider if I go for rsync?
> Yeah, rsync should work well. You just need to figure out a way to take
> a read lock on the repository before invoking rsync to avoid issues with
> concurrent access.

Would it be a viable alternative, instead of dealing with locks, to use
LVM and always copy from a mounted (read-only) snapshot?

> A good addition to this, albeit a bit resource hungry would be to run
> "attic check --repository-only $REPO" before rsync. That way you would
> avoid overwriting your good copy with a bad copy in case of silent data
> corruption.
Yes, this seems a good addition.


> / Jonas
>
>