better tool to backup/sync a folder to

freelab xavier freelab.cc at gmail.com
Mon Apr 21 22:41:14 UTC 2014


thank you daira for your fast answer

2014-04-21 23:02 GMT+02:00 Daira Hopwood <daira at jacaranda.org>:

> On 21/04/14 18:08, freelab xavier wrote:
> > hello everyone
> >
> > we are running a testbed with tahoe with no big issue, in fact up to now
> everything is
> > working fine when we do the things right :)
> >
> > objective is to make a backup grid for our small company using several
> computers in
> > office, in houses and one in datacenter.
> >
> > we do have approx 1 to to backup. (10 * 100 go).
>
> (Note that in English we'd normally write 1 TB or Tbyte for this. "Octet"
> is also a
> rarely-used synonym for "byte" in English, but it is not used for the
> abbreviations.)
>

sorry i am french speaking
we use "b" for bit only
and we prefer use octet instead of byte

the difference between byte and bit still is not as clear for us :)


> [...]
> > drop_upload :
> > this solution would be the easiest but seems not to be usable as
> subdirectories are not
> > checked
>
> That is ticket <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1433>.
>
> > sync using owncloud client and owncloud external storage over sftp :
> > it has been reported as usable by several owncloud user
> >
> >
> > cli command backup : this make an incremental backup and actually we do
> not need it (our
> > server do already manage versioning)
> > problem i have observed  is if a failure happens (network cut) before
> all backup is
> > completed : tahoe cannot find any of the transfered files
>
> Note that those files actually have been uploaded, so if you repeat the
> backup,
> it will complete sooner and using less total bandwidth than it otherwise
> would
> have, because it is using the already-uploaded files. However no files
> will be
> accessible until a backup has completed.
>
>
this confirm our observations

yes it is true the time is less if a backup resume
but it is quite sad that no file are accessible before a complete backup
 (if the initial data is big this can take time before any backup is
available)

but at least not everything is lost

would it be possible to include any security in that.


imagine i start saving 100 GB on a bad internet connection with no access
to full bandwidth
this will take several hours or days

this is sad/risky that during all those days there is no file available in
tahoe




> > is there any other CLI command that would be usable for a folder sync ?
>
> 'tahoe cp -r', but that will unconditionally copy everything. I don't
> think it
> has any advantages for this over 'tahoe backup'.
>

how does it act if a file already exist on tahoe ?

does it upload all files including existing ?
or only modified/new files (timestamp) ?



>
> > duplicity : it is reported to be working fine
> > for us archives are not the best but can you confirm this is ok ?
>
> Yes, as far as I know that is a good solution, although I haven't used it
> myself.
>
> --
> Daira Hopwood ⚥
>
>

are rsync or rdiff usable with tahoe ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tahoe-lafs.org/pipermail/tahoe-dev/attachments/20140422/8485e103/attachment.html>


More information about the tahoe-dev mailing list