Numerous Problems Related to Scheduling
I'm using ATI 2014 on a Windows 7. I was using previous ATI 2013 without any problems - I really regret upgrading!
The first problem I had was that my incremental disk backup continually kept doing the increments and wouldn't do a full backup again after I made a modification. No matter what numbers I set. I emailed support on this one and I got a reply explaining how to remove the scheduling which I thought was going to help me. All it did though was render the whole backup as useless. I couldn't do anything with it any more. All the menus became disabled. The only operation I could do was a delete.
If I wanted to delete it I would have just deleted it in the first place. The support person claimed that was the intention although there's no mention of this being the outcome. If I had known this I wouldn't have bothered as I potentially exposed myself to being unable to recover old data if I had needed to do so. So I'm not at all happy about that for starters.
Secondly, I created a new backup but after a few weeks I realised it was taking up too much space and decided to stop the scheduling and create another one. However, the original backup still runs though even though the schedule clearly says it's off. The log just shows it running as if nothing changed!
Then to make matters worse, the new backup I wanted (to save space) won't start even though the schedule clearly says it scheduled! The new backup has a different name by the way although it's backing up the same disk.
This all seems related to the scheduling. All the services seem to be running ok. No errors to indicate anything is wrong at all.
The only thing that has changed in my system is the upgrade to 2014. As I said before 2013 ran fine.
Anyone else had this sort of problem?
@GroverH, thanks for the comments.
Sorry, I didn't mean to emphasise a particular line on my screen dump. I meant the whole day as the backup unexpectedly ran on the 14th. The "Backup E" is for a different disk by the way. It's my offsite backup of my backups.
I stopped the SPARKZ12 backup, via the "do not schedule" button, on the 13th. The summary screen showed, as it did in my screen dump, that it wasn't scheduled. However, on the 14th it still did the backup as shown on my screen dump.
When I originally stopped the backup on the 13th, I created another for the same disk but with a different backup name (System). This was incremental rather than differential, as my original one was. So the display on the 13th showed:
"SPARKZ12, schedule: Turn on"
"System, schedule: daily, at 03:00".
However, on the 14th. My differential backup (SPARKZ12) still ran as before and my new incremental one (System) didn't run. The log for my new one didn't have anything in it. It's as if it's getting confused by having multiple backups for the same disk even though the actual backup has a different name.
I deleted the new one (System) on the 14th, so unfortunately I can't show that now.
However good news: last night (the 15th), with only the backups as shown in my screen dump, it did function as expected - no differential backup for SPARKZ12.
I'll create my new one again today and hopefully tonight it will run and my old one (SPARKZ12) won't. I don't want to delete my old backup as I sometimes need access to old files from different days for my work. The intention is to leave it until my new backup has a few weeks of backups.
Sorry, if that all sounds a bit confusing!
It sound's like you are in a wait and see situation. In the meantime, spend some reading time with link 2 below. Note especially the illustrations 6-7-8. Read and view these 3 pictures several times.
Understand that the assigning of names to the task and the tib backup file is two different functions, done in two different locations and via two different screens.
If you don't perform illustration 6 & 7, you cannot get to step 8 and it is step 8 which is the one and only place you can control or assign custom or specific names to the *.tib backup file.
The best time to additionally assign a task name (also referred to as backup name) is after you have configured all the various options and schemes, etc, and just prior to clicking the Backup Now (or Backup Later) option (to save the task). Optionally accept or change the "backup name" (lower left corner). It is this name which will appear on your main screen as the backup name. You can either leave it unchanged or change the backup name to a name of your choosing. Now is your one and only chance to assign this name as editing of a task is discouraged.
Illustration 8 control the names given to the tib backup files and where they are stored. Each task has both a task or backup name plus a name assigned to the actual tib backup files. They may be the same or they may differ--user controlled. If you accept all the defaults, it is possible for you to have two tasks with differing task names but with exactly the same backup file name. This is something you can control via the names you assign to the task and the names you assign to the tib backup file.
Illustration 18 shows the best and last chance to change the name of the task (or backup name) to a task name of your choosing. Changing this name does not change the name assigned to the tib backup file.
-----------------------------
There is still a possibility your tasks are mis-leading. I realize you just started over but I would suggest you cease to use your existing tasks and again start over with a new task which has a new name plus a new name for the tib backup file. Having read the references and understand where and how the two different names are created, you will have a better understanding of how the names interact.
@GroverH, thanks for the information. That's quite a comprehensive collection of useful TI knowledge you have there.
Thankfully, normal service has been resumed now. My old backup has stopped and I can still restore from it. My new backup did run on schedule ok.