Menu

#68 Concomitant daily+weekly+monthly backups

options/variables
open
nobody
5
2015-10-05
2015-05-01
Gingko
No

Hello.

I know that I am nearly four years late, but I tried 'AutoMySQLBackup' only today.

My first try ran properly, but I noticed a somewhat weird point.

It happens that I set 'AutoMySQLBackup' with its defaults options, which is doing a weekly backup each Friday and a monthly backup each first day of the month, in addition to its daily backup which always occurs.

Today is 2015-05-01 which is at once a Friday and the first day of the month.

The result is that 'AutoMySQLBackup' issued three backups at once, in the following order: monthly, weekly and daily.
All of these backups were whole runs, meaning that they needed three times the required processor resources, backup time, disk space and locked time for users of the still running MySQL application, although they were nearly identical (having been run just several minutes from each others).

Why is 'AutoMySQLBackup' not running the daily backup first, and next just creating hard links for the weekly backup and the monthly backup when necessary ?

Hard links are already used for the 'latest' copies (if optionally selected) for all three kinds of backups, this may result as at most six hard linked instances of the same files, thus saving time, resources and disk space during and after the backup, likely without any drawbacks.

Of course this may be somewhat more complicated for incremental backups, but I don't think this should be very difficult to solve.

Regards,

Gingko

Discussion

  • larsen255

    larsen255 - 2015-08-04

    +1

     
  • Stephan Bodmer

    Stephan Bodmer - 2015-10-05

    +1

     

Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.