Skip to main content

How to retry a failed incremental backup

Thread needs solution

My backup scheme for data partition has a full backup every 5 weeks and an incremental bu every week in between.

When an incremental fails (due to system shutdown), how do I retry (restart) that weeks incremental? It doesn't start automatically, although I have the retry option set, and if I press 'Backup Now', it starts a new full backup instead, which I do not want.

What should I be doing?

Richard

0 Users found this helpful

Clicking the "backup now" option tells the program to create the next backup--whatever type is due next based on your configuration settings and the number of backups which already have been created.

If you have your scheme set for full plus 4 incrementals, then the tib target storage folder should read as follows if the program is working correctly.

_FULL_B1_S1_V1

_INC_B1_S2_V1

_INC_B1_S3_V1

_INC_B1_S4_V1

_INC_B1_S5_v1

_FULL_B2_S1_V1
NOTE the full was due after the four incrmentals if scheme set to Full + 4 incrementals. If the scheme is set for Full plus 3 incrementals, then the S5 slice would not appear and the full B2 would follow the S4 slice.
You do not indicate whether you have automatic cleanup configured.  If you do not, I would recommend that stop using your existing task and begin againwith a new task configured for automatic cleanup as you see my example GH12 except set your own number of incrementals to follow the full.

Additinally, then set the automatic cleanup which is the "Store no more than 'n recent version chains."  ( A chain is all the files with the same B#. All the files in the B1 backup is chain1.  All the files in B2 is another chain, etc.) 

If you want the new backup to replace the old backup, then set the store number to 1.  Or, set the "store quota number to be whatever number of chains you wish to retain before the automatic deletion by the program begins.  Additionally, if you wish to keep the oldest full so it is exempt from deletion and retention quota, then checkmark the option "do not delete the oldest chain."

Note, if you check the "do not delete the oldest chain", it will be the first backup created (B1) and it will be a full and exempt from deletion. The next backup will also be a FULL (B2) which begins the Full + x incrementals.  If you do set the "do not delete the oldest chain", you may want to create one backup manually during the first month so as to keep on your set schedule because of the extra backup.

General: Examples of automatic cleanup.  Each task must carry the backup scheme name "custom"  as illustrated by the examples.
 These can be set up for Disk image, or Partiton, or Files-folders backups.  These example show how to set up automatic cleanup so the program will do the deletion after it reaches your "store # (retention quota) of how many chains to retain.

Editing an existing task is not recommended.  Rarely does an edited task perform to user expectations. It is usually  better to start with a new task using a new non-identical task name and point to a new storage sub-folder so each task has it own storage folder/sub-folder. Old task can be stopped or deleted from the task listings.

GH12. Create Custom Incremental Backup Scheme w/auto cleanup. ...Keep Full plus 6 Inc per chain. Store/Keep 4 chains. Use whatever number best fits your needs.

GH25. Understanding differences between Incremental and Differential backups for data recovery.

AGH-1. 64640: Do's & Don'ts--Hints to help prevent issues with your TIB.

GH63. 75086: A discussion on how to configure backup schemes.

Thank you for the information and links - it caused me to check more closely into the failure, and it seems that the problem is different to what I had thought - I am just as puzzled, but for a different reason!

If you look at the first two atachments, it is clear that the original backup was in fact trying to write a new full backup - Data2_full_b2_s1_v1 - inspite of the fact that only two incrementals exist, rather than the 4 called for by the scheme. Therefore the manual retries were in fact consistent in attempting to create full backups - but I do not understand why the original wasn't creating incremental s4 rather than a new full?

I have checked my Scheme definitions, using the information in the reply above, and it all seems to be correct - see attachments 3 & 4 - indeed, one of the other backups running just beforehand (see attchment 5) is identical, and worked perfectly, as attachment 2 shows.

Less significant, but also not what I expected, the status of Data2 backup after the failure - attachment 6 - shows the last backup as the previous week - correct - but the next as the following week, rather than indicating an outstanding backup for this week. I don't understand why the retry settings - attachment 7 - did not trigger an automatic retry when the system restarted?

Attachment Size
297402-122341.jpg 82.62 KB
297402-122344.jpg 111.57 KB
297402-122347.jpg 112.53 KB
297402-122350.jpg 84.67 KB
297402-122353.jpg 299.96 KB
297402-122356.jpg 156.37 KB
297402-122359.jpg 100.62 KB

Richard,
I would agree that a retry at the backup should have been triggered on startup following the missed backup. Have you looked at the log file?

The most usual explanation is the original task was changed by user edits and the program did not implent the changes correctly.
All my references lists advises against editing a task and the changes rarely ever produce the correct results. I don't know why changes are permitted if they cannot be implemented. However, the fact that the task is not working justifies starting over with a new task and ceasing to use the old one.
You many even want to consider running the TI cleanup utility and do a fresh re-install, but your other tasks "appear" to be working correctly.

Editing an existing task is not recommended. Rarely does an edited task perform to user expectations. It is usually better to start with a new task using a new non-identical task name and point to a new storage sub-folder so each task has it own storage folder/sub-folder. Old task can be stopped or deleted from the task listings.

GH12. Create Custom Incremental Backup Scheme w/auto cleanup. ...Keep Full plus 6 Inc per chain. Store/Keep 4 chains. Use whatever number best fits your needs.

GH25. Understanding differences between Incremental and Differential backups for data recovery.

AGH-1. 64640: Do's & Don'ts--Hints to help prevent issues with your TIB.

GH63-1. 75086: A discussion on how to configure backup schemes.

Rather than a cleanup/re-install, some users delete all the files in the database folder
c:\programdata\acronis\trueimagehome\database

The logs can be found at
c:\programdata\acronis\trueimagehome\logs

The scripts show in the task listing found here.
c:\programdata\acronis\trueimagehome\scripts