fswatch-rsync | local folder with a remote folder via another server | Continuous Backup library

by aalto-ics-kepaco Shell Version: v0.2.0 License: No License

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | fswatch-rsync Summary

fswatch-rsync is a Shell library typically used in Backup Recovery, Continuous Backup applications. fswatch-rsync has no bugs, it has no vulnerabilities and it has low support. You can download it from GitHub.

This is a script to automatically synchronize a local project folder to a folder on a cluster server via a middle server. It watches the local folder for changes and recreates the local state on the target machine as soon as a change is detected. Warning: This script enforces the local state of the folder to the remote location, meaning if additional files are created on the remote location they will be deleted, so don’t store results or any other work in subfolders on the remote location. If you need to work inside the target folder you can of course create hidden folders or files since hidden files will be ignored as mentionend above.

Support

Quality

Security

License

Reuse

Support

fswatch-rsync has a low active ecosystem.

It has 55 star(s) with 22 fork(s). There are 17 watchers for this library.

It had no major release in the last 12 months.

There are 3 open issues and 0 have been closed. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of fswatch-rsync is v0.2.0

Quality

fswatch-rsync has 0 bugs and 0 code smells.

Security

fswatch-rsync has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

fswatch-rsync code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

fswatch-rsync does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

fswatch-rsync releases are available to install and integrate.

Installation instructions are available. Examples and code snippets are not available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of fswatch-rsync

Get all kandi verified functions for this library.

fswatch-rsync Key Features

No Key Features are available at this moment for fswatch-rsync.

fswatch-rsync Examples and Code Snippets

No Code Snippets are available at this moment for fswatch-rsync.

Community Discussions

Trending Discussions on Continuous Backup

How to disable azure cosmos db continious backup

Consistency of Continuous backup of Azure Cosmos DB

Mongo atlas recommends cloud provider snaphots for backup - Is it effective?

QUESTION

How to disable azure cosmos db continious backup

Asked 2022-Feb-22 at 10:59

I enabled the Azure cosmos DB continuous backup for one of my Cosmos DBs.
How can I disable it? It just says you have successfully enrolled in continuous backup.

...

ANSWER

Answered 2022-Feb-22 at 10:59

I am not sure if you have seen this message in the portal when you created the account/also mentioned in the doc

"You will not be able to switch between the backup policies after the account has been created"

since you need to select either "Periodic" or "Continuous" at the creation of Cosmos Account, it becomes mandatory.

Update:

You will not see the above in portal anymore, you can Switch from "Periodic" to "Continous" on an existing account and that cannot be reverted. You can read more here.

Source https://stackoverflow.com/questions/69347197

QUESTION

Consistency of Continuous backup of Azure Cosmos DB

Asked 2021-Nov-25 at 17:15

What would be the consistency of the continuous backup of the write region if the database is using bounded staleness consistency? Will it be equivalent to strong consistent data assuming no failovers happened?

Thanks Guru

...

ANSWER

Answered 2021-Nov-25 at 17:15

Backups made from any secondary region will have data consistency defined by the guarantees provided by the consistency level chosen. In the case of strong consistency, all secondary region backups will have completely consistent data.

Bounded staleness will have data that may have stale or inconsistent data inside the defined staleness window (minimum 300 seconds or 100k writes). Outside of that staleness window the data will be consistent.

Data for the weaker consistency levels will have no guarantees for consistency from backups in secondary regions.

Source https://stackoverflow.com/questions/70099953

QUESTION

Mongo atlas recommends cloud provider snaphots for backup - Is it effective?

Asked 2020-May-19 at 10:12

MongoDB has deprecated the continuous back up of data. It has recommended using CPS (Cloud provider snapshots). As far as I understood, snapshots isn't really going to be effective compared to continuous backup coz, if system breaks, then we can only be able to restore the data till the previous snapshot which isn't gonna make the database up-to-date or close to it atleast.

Am I missing something here in my understanding?

...

ANSWER

Answered 2020-May-19 at 10:12

Cloud provider snapshots can be combined with point in time restore to give the recovery point objective you require. With oplog based restores you can get granularity of one second.

Source https://stackoverflow.com/questions/61886736

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install fswatch-rsync

Download and install fswatch: https://github.com/alandipert/fswatch. Make fswatch available in your PATH variable. This can be achieved by appending PATH=/path/to/where/you/installed/fswatch:$PATH to ~/.bash_profile (OSX) or ~/.bash_rc (most Linux). OR you can add your path to fswatch to the script itself instead by changing the FSWATCH_PATH variable. Set up ssh-key authentification: If you don’t have an ssh key-pair, generate one using ssh-keygen. Then copy the key to the middle server using ssh-copy-id -i ~/.ssh/id_rsa.pub ssh_user@middleserver. Follow the same procedure for the authentification from middle to target server (create a keypair on the middle server and copy it to the target server). See the Note below if you’re on a Mac and don’t have ssh-copy-id installed. Make the script executable: chmod u+x ./fswatch-rsync.sh. Note: On a Mac you can either install ssh-copy-id via MacPorts/Brew/etc, compile it from source or you can just append the content of your public key (default ~/.ssh/id_rsa.pub) to the ~/.ssh/authorized_keys file on the server. Make sure the access rights are set properly though (e.g. chmod 700 for ~/.ssh and 600 for ~/.ssh/authorized_keys, see <http://unix.stackexchange.com/questions/36540/why-am-i-still-getting-a-password-prompt-with-ssh-with-public-key-authentication>).
Download and install fswatch: https://github.com/alandipert/fswatch.
Make fswatch available in your PATH variable. This can be achieved by appending PATH=/path/to/where/you/installed/fswatch:$PATH to ~/.bash_profile (OSX) or ~/.bash_rc (most Linux). OR you can add your path to fswatch to the script itself instead by changing the FSWATCH_PATH variable.
Set up ssh-key authentification: If you don’t have an ssh key-pair, generate one using ssh-keygen. Then copy the key to the middle server using ssh-copy-id -i ~/.ssh/id_rsa.pub ssh_user@middleserver. Follow the same procedure for the authentification from middle to target server (create a keypair on the middle server and copy it to the target server). See the Note below if you’re on a Mac and don’t have ssh-copy-id installed.
Make the script executable: chmod u+x ./fswatch-rsync.sh

Support

Please let me know if there’s any problems with this script or the setup, I’m happy about any feedback. And of course also feel free to fork this and contribute here on GitHub. The package is free to use without any license (public domain).

Find more information at: