

# THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER # FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. # IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, # THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR # all copies or substantial portions of the Software. # The above copyright notice and this permission notice shall be included in # Software is furnished to do so, subject to the following conditions: # and/or sell copies of the Software, and to permit persons to whom the

# the rights to use, copy, modify, merge, publish, distribute, sublicense, # to deal in the Software without restriction, including without limitation # copy of this software and associated documentation files (the "Software"), # Permission is hereby granted, free of charge, to any person obtaining a The script is designed to be run daily using cron. Unmodified files are hardlinked between the backup instances. Rsync uses hard links to store similar files which saves huge amount of backup space as only modified files are written into the backup drive. Which allows the users to retrieve their missing content without any administrative operations. The backup structure can be mounted as a read only drive InĮach of the folder there is a subfolder for each of the target folders for backup with their backuped contents inside. Backups are stored in separate folders in the backup drive.

This saves a lot of space as recentĬhanges are held daily, but older changes are stored only weekly and then monthly. After a few weeks only the first weekly backup of each month is kept. Only weekly backups are held and other daily backups are removed. The script keeps three adjacent daily backups and after three days The script makes daily backups of target folders and keeps user rights and folder structure using rsync.

Rsync backup script to take daily, weekly and monthly backups automatically Incremental Rsync backup script to take daily, weekly and monthly backups automatically
