Hi,
I have a simple Client Mac <> FullBackup on remote SSH <> Client On Mac setup which seems to work great.
I have 2 questions : - Whenever a new file is created or changed it can takes a few hours until the second client gets the file. Is this normal ? - How Can I make sure, that all the files are on the FullBackup ?
Many thank !
Well, it depends on how big the files are, but taking a few hours to sync might indicate that your repositories are not immediately notifying one-another of changes. It might be falling back to polling every half an hour for new changes.
You could fix that by setting up XMPP, or better, by installing git-annex 5.20140421 or newer on the SSH server; then the clients would immediately notify when there are changes.
You can find out if all files are present on the server by running
git annex find --not --in $serveron one of the clients. Any files it prints out have not been stored in the server.Thanks for this speedy answer !
I have version 5.20150219 installed on all the clients and on the server. The ssh server is a gcrypt repository. Could this be the reason of the clients not being notificated of the changes ??
Also, in theory, some file on one of the repositories could get corrupted, deleted, whatever. How can I make the repo check if everything is like intended on the other repos ? For example, I made a test renaming a file within the objects directory on the remote ssh server and ran git annex fchk, but it reported nothing...
Many thanks again !
Also, I noted a difference between encrypted (gcrypt) repos and unencrypted repos. The second ones have the other icon saying that it is live messaging. The encrypted one have a standard icon. Is it a technical limitation that encrypted repos can not live message ? And could it be the reason why the sync is not happening itself until i manually choose "sync" from the menu ?
You can use
git annex fsckto verify your repository contents. If you want to verify a local repository, the best thing to do is to rungit annex fsckthere. If you cannot do that, you can usegit annex fsck --from remoterepo --fastto verify a remote. If you leave off the --fast it will download all file contents to completely verify them.I suggest you read git-annex's documentation, there is plenty of it about using git-annex fsck to verify repositories.
The lack of "live messaging" for gcrypt repos is a bug. I'm fixing it now and the next version of git-annex will have remotedaemon properly supporting gcrypt repos.