old version chains not being deleted
i am (and have been trying for months) to try to get my backups to work properly (as I expect them to...)
I have 2 backups configured:
one is a system drive backup (approx 200gb at present), the other is a backup of another drive connected to my system (approx 450gb)
both have the same settings and backup to the same external hard drive (1tb).
the settings are to create a full backup, daily backup, incremental mode, create a new full version after every 6 incremental versions, delete chains older than 6 days.
right now my external hard drive contains the following files:
3 files for the non-system drive:
1 full backup of 470gb dated 7/26/16, an incremental backup of 32gb dated 7/27/16 and an incremental backup of 2mb dated 7/28/16.
then the backups of that drive just stop. no more backups.
13 files for my system drive backup:
1 full backup of 100gb dated 8/5/16, 6 incremental backups of between 1 to 3 gb each dated daily from 8/6/16 to 8/11/16.
then another full backup of 113gb dated 8/12/16, followed by 5 incremental backups of less than 1gb each dated daily from 8/13/16 to 8/16/16. strangely, on 8/16/16 there were 2 incremental backups of a very small size (one was 45mb and the other was 574mb).
then the backups of that drive also stops.
now there is no more activity on either backup. it hasn't deleted any old chains.
the destination drive has 179gb of free space.
Now i find out that i have to pay for tech support from the company that i bought the software from. Seriously, why would any company only give 30 days of support for technical issues for software that you pay for? I've had better customer support from many freeware companies.
any ideas what i'm doing wrong?
i've deleted my backup plans a couple of times already and started over because i thought i had screwed something up. i don't think its me though.
Agreed, need some more information to go on. If the backup just stopped, most likely, it's because either the source or destination have changed (upgrading to Windows 10 can have that effect as it modifies the original partitoin scheme), or, perhaps the drive letter has changed. I would simply go back into the task and re-select teh source and destination and run the backup again and see what happens. If it runs, great. However, the backup version chain count will reset, so you'll hae to wait for 6 more incrementals, but at least it will be running again.
Second guess, with the limited information.. You have Windows Fast boot enabled and the backups are not able to run because the system is sleeping or hibernating during the scheduled time. Upon "waking up" because of fastboot, it does not trigger with Acronis. The way to resolve this is 1) disable fastboot - disable hibernaion if you can or 2) always reboot/restart the machine instead of shutting down (since a shutdown with fastboot just puts the system into hibernation and doesnt' trigger the full startup code in event viewer that Acronis needs to run a missed backup when the machine returns from a full boot).