ATTN: GroverH TIH Auto clean of backups not working for me, as you describe it should
Hello GroverH,
You know how enamored I am with all the hard work you do on your own time for the forum.
Pursuant to your directions I set My Disk Backup Options as you show, to keep only 2 current backups and delete the oldest one. it would be a great help if it would work and keep the drive from becoming full accidentally.
Today I did my weekly My Partitions backup expecting to see the first on in the set be removed bit it's still there.
What did I do wrong or did I misunderstand your directions? I see the 2 .jpgs that show my current configuration.
Thank you,
F Wolf
What changes did you make in your backup tasks between Feb 5 and 8th.
Did you start over on Feb 5 with a new backup task or did you make changes to an existing one?
Did you restore a backup sometime betgween the 5th and the 8th?
Because the last 2 backups are the same numbering scheme, it is possible the program will correct itself after the next backup.
Take no action until after the next backup. If the backups do not correct themselves and begin the deletion of the oldest and keep only 2, post back after the next backup and we can determine what needs to be done at that time.Examine each of the log files for Feb-5, 6, 7, and 8th. This might give you a clue as to the cause.
Hi GroverH,
Yes I did do a restore on Feb 5 the log shows it and that the machine needed a reboot as well. Seems odd that doing a restore would mess up the schedule, but apparently it does for some reason. Never had that trouble doing each partition separately I must say, but then there was NO schedule either!
I won't make any changes until next weekend and we'll see what happens then. Maye it will sort itself out or maybe not!
Thanks!
Just to follow-up:
As the backups are not stored on the system disk, following the restore, the storage folder contained tib backup files which the restored acronis history file (archives.xml) did not know about.
In order for backup to have continued with the correct number, the tib backup file (that was used for the restore) would need to have been deleted (or hidden away plus any newer backups) so that the storage folder contents matched exactly to what it was at "snapshot" time, as the actual backup file did not come into existence until after the completion of the backup. Therefore the existence of the newer backup after the restore was a surprise to the history file so it added the v2-1 to the file name of the next backup.