Repeating back-ups
Re: Repeating back-ups
I think I have a good idea for when and why this is happening. This has just happened to me.
- I have it running as a service
- I have incremental backup scheduled every day
- I have it set to do the missed backups, but (important!)
- I have it set to NOT create empty directories
- I see that last backup is at 10:20 p.m. on 6/15
- all the backups that follow are incremental
- It did one incremental backup next day (11 p.m. on 6/16) and then staring next morning is going once every hour.
- and (the key to the puzzle) the program shows in the "history" tab that the last backup that ran was from 10:20 p.m. on the 6/15. (That's the last non-empty backup!)
Verdict: apparently empty backups are not registering in the job history, and if the program sees no jobs in history for long enough (looks like twice the planned period, so 2 days in my case), it attempts a backup every one hour.
- I have it running as a service
- I have incremental backup scheduled every day
- I have it set to do the missed backups, but (important!)
- I have it set to NOT create empty directories
- I see that last backup is at 10:20 p.m. on 6/15
- all the backups that follow are incremental
- It did one incremental backup next day (11 p.m. on 6/16) and then staring next morning is going once every hour.
- and (the key to the puzzle) the program shows in the "history" tab that the last backup that ran was from 10:20 p.m. on the 6/15. (That's the last non-empty backup!)
Verdict: apparently empty backups are not registering in the job history, and if the program sees no jobs in history for long enough (looks like twice the planned period, so 2 days in my case), it attempts a backup every one hour.
Re: Repeating back-ups
Just check "Save empty backups" in the engine settings.
--
Luis Cobian
Cobian Backup's creator
Luis Cobian
Cobian Backup's creator