schiwagoa/rsync-time-backup
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source 
Minor tweaks
This commit is contained in:
Laurent Cozic
2017-09-26 15:09:55 +01:00
committed by GitHub
parent 4393a86bd0
commit 74f418d561
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -4
View File
@@ -40,7 +40,7 @@ On macOS, it has a few disadvantages compared to Time Machine - in particular it
* Backup from remote drive over SSH: * Backup from remote drive over SSH:
rsync_tmbackup.shuser@example.com:/home /mnt/backup_drive rsync_tmbackup.sh user@example.com:/home /mnt/backup_drive
* To mimic Time Machine's behaviour, a cron script can be setup to backup at regular interval. For example, the following cron job checks if the drive "/mnt/backup" is currently connected and, if it is, starts the backup. It does this check every 1 hour. * To mimic Time Machine's behaviour, a cron script can be setup to backup at regular interval. For example, the following cron job checks if the drive "/mnt/backup" is currently connected and, if it is, starts the backup. It does this check every 1 hour.
@@ -78,9 +78,7 @@ The script creates a backup in a regular directory so you can simply copy the fi
* Each backup is on its own folder named after the current timestamp. Files can be copied and restored directly, without any intermediate tool. * Each backup is on its own folder named after the current timestamp. Files can be copied and restored directly, without any intermediate tool.
* Backup to remote destinations over SSH. * Backup to/from remote destinations over SSH.
* Backup from remote destinations over SSH.
* Files that haven't changed from one backup to the next are hard-linked to the previous backup so take very little extra space. * Files that haven't changed from one backup to the next are hard-linked to the previous backup so take very little extra space.