Line 111: |
Line 111: |
| | | |
| ==='''Practical setup tips'''=== | | ==='''Practical setup tips'''=== |
| + | |
| + | ====Typical settings==== |
| | | |
| Change these to suit your particular situation. | | Change these to suit your particular situation. |
Line 138: |
Line 140: |
| Full backup session (new backup sets) is allowed only on Friday | | Full backup session (new backup sets) is allowed only on Friday |
| | | |
| + | |
| + | ====Backup disk size limits workaround==== |
| + | |
| + | If having issues with the size of removable backup disks (eg 120Gb IDE on a workstation) versus the resultant backup data size (eg 120Gb of data compressing to approx 50Gb), then you can manually setup a cron job to delete the old backup file(s) before saving the new backup file(s). |
| + | |
| + | The specific issue experienced was being able to get one full backup onto a disk, and a weeks worth of daily incrementals, but the next weekly full backup failed, due to the need to save the new backup in the tmp folder on the removable disk, before deleting the old backup files. There was not enough space on the disk (size) being used. |
| + | |
| + | To workaround this, create a cron job and put it in /etc/cron.d with a script in /opt/scripts/XXX, which mounts the drive and deletes the old backup just before the new full backup commences. |
| + | This will delete the old backup before the new backup commences, which is different to how the backup is designed to work by default. It is necessary to forgo the security of retaining the old backup until the new one has completed, in order to use the available hardware (smaller disk). |
| + | |
| + | |
| + | Create the deletion script |
| + | pico -w /opt/scripts/deletebkp1 |
| + | |
| + | Enter the following (using your share name, user, pasword & domain) |
| + | umount /mnt/smb |
| + | /bin/mount -t smbfs //stationXX/bkp1 /mnt/smb -o username=XXXXXX,password=XXXXXXXXXXXXX |
| + | rm -f -R /mnt/smb/servername.yourdomain.com/ |
| + | rm -f -R /mnt/smb/tmp_dir/ |
| + | |
| + | Then save & exit |
| + | Ctrl o |
| + | Ctrl x |
| + | |
| + | |
| + | Create the cron job |
| + | pico -w /etc/cron.d/deletebkp1 |
| + | |
| + | Enter the following (setting the time & day to be just before your scheduled backup time), see below. |
| + | The following values suit a scheduled full backup for 2.00am on Saturday morning (ie Friday evening), where the old backup gets deleted at 1:50am |
| + | |
| + | 50 1 * * 6 root . /opt/scripts/deletebkp1 |
| + | |
| + | Then save & exit |
| + | Ctrl o |
| + | Ctrl x |
| + | |
| + | Restart crond so the new cron job takes effect |
| + | /etc/init.d/crond restart |
| + | |
| + | |
| + | Cron entries format is as follows: |
| + | +-----------------------Minute (0-59) |
| + | | +-------------------Hour of Day (0-23) |
| + | | | +---------------Day of Month (1-31) |
| + | | | | +-----------Month of Year (1-12) |
| + | | | | | +-------Day of Week (0=Sun,6=Sat) |
| | | |
| ==='''Removal/uninstall information'''=== | | ==='''Removal/uninstall information'''=== |