Re: Split a Replica Job Into Two
"'Brian Spraker' via unison-users" <[email protected]> Fri, 19 Apr 2024 05:17:06 -0700 (PDT)
| Newsgroups | gmane.network.unison.general |
|---|---|
| Message-ID | <[email protected]> |
That is correct. The initial scan / setup takes several hours to do. But once the archives are made, the scan completes in a matter of 30 seconds or less. Then whatever needs replicated takes an indeterminate amount of time. On Thursday, April 18, 2024 at 1:11:29 AM UTC-5 Tõivo Leedjärv wrote: > I believe Brian was referring to the initial scan after the archive files > are removed. The entire contents of the replica must be scanned then. This > is always going to take time because it is bound by the storage speed and > the entire 190 GB is read in. After the initial scan it will be mostly a > metadata scan and should complete in seconds. > > > On Wed, 17 Apr 2024 at 23:09, Eberhard W Lisse <[email protected]> wrote: > >> I have been using Unison for more than 20 years, mainly on Macs, but also >> a little on Windows and Ubuntu and currently have 65 GB home directory on 3 >> Desktops and 2 Laptops in an Intel and Silicon mix (all Mac). I use >> Homebrew and unison -version shows 2.53.4 (ocaml 4.14.1) >> >> Reconstruction of the archives takes around 30 seconds on the same WiFi. >> From the outside it takes perhaps a minute or less. I am convinced that >> tripling the size will not make this much worse. >> >> Making Backup of the Backup sounds silly to me. Rather upgrade on all >> sides and see what that does. >> >> el >> >> -- >> Sent from my iPhone >> On Apr 17, 2024 at 20:27 +0200, 'Brian Spraker' via unison-users < >> [email protected]>, wrote: >> >> That is a good idea.. and then potentially script something that makes a >> backup once a week. >> >> On Wednesday, April 17, 2024 at 12:49:38 PM UTC-5 [email protected] >> wrote: >> >>> "'Brian Spraker' via unison-users" <[email protected]> writes: >>> > The storage is up to about 190 GB now. Over the past few months, the >>> > archive files are getting corrupt. This requires that the archive file >>> on >>> > both systems be deleted - and the whole replica has to start over >>> again. >>> > The first time the archive files are set up, it takes several hours for >>> > Unison to scan and set up. >>> >>> One cheat you can do is that once you get a Unison run to complete >>> successfully, copy the archive files to a safe place. (Probably the >>> simplest is to copy ~/.unison whole.) If the archive files get >>> corrupted, you can replace them with a copy of the saved version. >>> Unison will still have to do extra checking when it is run next with the >>> restored archives, but likely a lot less work than it would take to >>> recreate them completely. >>> >>> Dale >>> >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> > To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].