cannot stop backup, more
I just created a new backup task for Acronis 2017. This computer already has two backup tasks configured and running for well over a year. This new backup, however, doesn't actually backup and stays on "calculating" forever. Clicking on Stop Backup show "stopping ...", but otherwise does nothing. Restarting Acronis or rebooting resumes this problem backup. I cannot kill it.
I've followed this post from Steve Smith, https://forum.acronis.com/forum/acronis-true-image-2017-forum/cannot-st…, which involved stopping the Acronis services, downloading and running Acronis Schedule Manager and entering 'task zap', but that does not stop the bad task and I still cannot stop or delete it.
Please advise -- I'd really rather NOT reinstall Acronis!


- Log in to post comments

I added the deletion of the Script file step, then rebooted. That caused the backups to NOT run. Interestingly, the bad backup still showed in the list, but I was able to delete it and re-enable the other scripts.
I re-added the 3rd backup and ran it. It ran for a while (20 minutes) and got to "Backing up 70.82GB - 1hr 42m", then just hung there for more than 12 hours. Again, could not stop the backup. I ran through the same procedure and rebooted again. Again, the bad backup task still show up, but didn't start.
Not sure what the problem is. I'm making 1 consolidated backup of two other backups I'm running. The two are two sets of 30 days whereas this new backup is to be 1 set of 7 days (to be copied to offsite backup). Perhaps the problem is that I am trying to back up the C: partition and the F: partition which is on a RAID controller.
- Log in to post comments

I've been playing around with this for several weeks. I managed to apparently solve my initial problem by breaking up the backup that had a Partition backup of C: and a Files backup of F: together into two different backups. That seemed to let the individual backups proceed. But I'm still having problems.
The Files backup of F: is set to create a full version after 6 incrementals and I've set it to keep only one chain. But this is not working. The backup does creates the 6 incrementals, then does create a full, but it is not doing the cleanup.
I've completely removed and reinstalled ATI, including running the Cleanup Tool, and I've reconfigured ALL backups, but it still doesn't work. On this backup, I have several times set "Turn on automatic cleanup" and set it to store no more than 1 version chain" (and clicked OK). But after quitting, then re-running the GUI I find it is set back to "Turn on automatic cleanup" and my settings for this are lost as far as the GUI is concerned. Yet they show set in the script file.
I've attached the tib.tis script for this backup. You will notice that the <volumes_locations> only show the most recent chain, yet on the disk I have:
-rwxr-xr-x 1 root root 33510063104 2019-01-28 01:35 /mnt/tmp/dbserverOffsiteF_full_b2_s1_v1.tib*
-rwxr-xr-x 1 root root 33557864960 2019-02-03 01:35 /mnt/tmp/dbserverOffsiteF_full_b3_s1_v1.tib*
-rwxr-xr-x 1 root root 89716224 2019-01-28 20:00 /mnt/tmp/dbserverOffsiteF_inc_b2_s2_v1.tib*
-rwxr-xr-x 1 root root 220160 2019-01-28 23:44 /mnt/tmp/dbserverOffsiteF_inc_b2_s3_v1.tib*
-rwxr-xr-x 1 root root 87052288 2019-01-29 20:00 /mnt/tmp/dbserverOffsiteF_inc_b2_s4_v1.tib*
-rwxr-xr-x 1 root root 89878528 2019-01-30 20:00 /mnt/tmp/dbserverOffsiteF_inc_b2_s5_v1.tib*
-rwxr-xr-x 1 root root 68551168 2019-01-31 20:00 /mnt/tmp/dbserverOffsiteF_inc_b2_s6_v1.tib*
-rwxr-xr-x 1 root root 49789440 2019-02-01 20:00 /mnt/tmp/dbserverOffsiteF_inc_b2_s7_v1.tib*
-rwxr-xr-x 1 root root 218624 2019-02-03 20:00 /mnt/tmp/dbserverOffsiteF_inc_b3_s2_v1.tib*
-rwxr-xr-x 1 root root 92433408 2019-02-04 20:00 /mnt/tmp/dbserverOffsiteF_inc_b3_s3_v1.tib*
You will also notice that under <common_options> I have: increment_type="incremental" rotation_count="6" rotation_scheme="1". But it is ignoring the rotation_scheme attribute.
Perhaps it should be noted that I have 4 backups configure on this host. Perhaps having a 4th backup is a problem?
Is there something I can do to fix this?
Attachment | Size |
---|---|
488254-163745.txt | 7.92 KB |
- Log in to post comments

Perhaps it should be noted that I have 4 backups configure on this host. Perhaps having a 4th backup is a problem?
I have more than 4 backups configured on my computer without any similar issues!
What does the backup log for the task showing this issue say about the consolidation aspect - does it show if any attempt was made to delete the oldest version chain?
- Log in to post comments

The log for when the 2nd full backup was created is:
ti_demon/ti_demon_560CF4B2-719B-4CC6-9CE3-96BABCE65550_54BE47FD-3751-44BB-AABA-7ABE822E0653_2019-02-02-20-00-01.log
2019-02-02 20:00:02:057 45992 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2019-02-02 20:00:02:057 45992 I00640002: Operation dbserverOffsiteF started by schedule.
2019-02-02 20:00:06:659 45992 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2019-02-02 20:00:06:675 45992 I013C0000: Operation: Backup
2019-02-02 20:00:12:275 45992 I000B03F0: <bold>Create Backup Archive</bold><endl/><tabpoint value=30><indent value=4><textcolor value=0x00ff000
0>Password Protected</textcolor><endl/>From: <indent value=10><textcolor value="navyblue">F:\
</textcolor></indent><indent value=4><endl/>To file: <indent value=10><textcolor value="navyblue">"dbserverOffsiteF_full_b3_s1_v1.tib"</text
color></indent><indent value=4><endl/>Compression: <indent value=10><textcolor value="navyblue">High</textcolor></indent><indent value=4><
endl/>Exclude: <indent value=10><textcolor value="navyblue">System files</textcolor></indent><indent value=4><endl/></indent><endl/>
2019-02-02 20:00:14:693 45980 I00640000: Writing full version to file: dbserverOffsiteF_full_b3_s1_v1.tib
2019-02-03 01:35:50:010 45992 I00640000: The following backups have been successfully created:<endl/>"E:\dbserverOffsiteF_full_b3_s1_v1.tib"
2019-02-03 01:35:51:258 45992 I013C0006: Operation has succeeded.
The log for the next day is:
ti_demon/ti_demon_560CF4B2-719B-4CC6-9CE3-96BABCE65550_15F1C456-843E-46DF-98A0-D997022F405C_2019-02-03-20-00-01.log
2019-02-03 20:00:01:788 48256 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2019-02-03 20:00:01:788 48256 I00640002: Operation dbserverOffsiteF started by schedule.
2019-02-03 20:00:06:343 48256 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2019-02-03 20:00:06:343 48256 I013C0000: Operation: Backup
2019-02-03 20:00:12:177 48256 I000B03F0: <bold>Create Backup Archive</bold><endl/><tabpoint value=30><indent value=4><textcolor value=0x00ff000
0>Password Protected</textcolor><endl/>From: <indent value=10><textcolor value="navyblue">F:\
</textcolor></indent><indent value=4><endl/>To file: <indent value=10><textcolor value="navyblue">"dbserverOffsiteF_inc_b3_s2_v1.tib"</textc
olor></indent><indent value=4><endl/>Compression: <indent value=10><textcolor value="navyblue">High</textcolor></indent><indent value=4><
endl/>Exclude: <indent value=10><textcolor value="navyblue">System files</textcolor></indent><indent value=4><endl/></indent><endl/>
2019-02-03 20:00:17:294 48256 I00640000: Writing incremental version to file: dbserverOffsiteF_inc_b3_s2_v1.tib
2019-02-03 20:00:17:294 48256 I00640000: The following backups have been successfully created:<endl/>"E:\dbserverOffsiteF_inc_b3_s2_v1.tib"
2019-02-03 20:00:18:324 48256 I013C0006: Operation has succeeded.
Neither indicate anything about deleting older chains.
The odd bit is that when I modify the settings on this backup to do the auto cleanup, then go back into the ATI GUI, the cleanup settings are gone. Yet they show in the config script! As mentioned, I completely deleted and reinstalled ATI, and recreated the backups. Didn't make any difference.
- Log in to post comments

The odd bit is that when I modify the settings on this backup to do the auto cleanup, then go back into the ATI GUI, the cleanup settings are gone. Yet they show in the config script! As mentioned, I completely deleted and reinstalled ATI, and recreated the backups. Didn't make any difference
Manually editing the Script .tib.tis files will always be a possible source of strange issues or behaviour. What happens if you create a new test backup task with all the required settings for number of backups, cleanup etc - does that then work as it should? This doesn't have to be more than just a few folders or files for test purposes.
- Log in to post comments

I guess I miscommunicated. I did not edit the .tib.tis file. I made the changes strictly in the GUI. However, to test, I'll set up a 5th backup with only 2 increments and see how that works. I'll know in 3 days.
- Log in to post comments

Back again, after more testing. The 5th backup has the same problem. In Summary, The Files backup of F: is set to create a full version after 6 incrementals and I've set it to keep only one chain. But this is not working. The backup does creates the 6 incrementals, then does create a full, but it is not doing the cleanup on the old chains.
So, the 4th and 5th configured backups on this computer simply DO NOT clean up.
However, I've solved the problem! After comparing the script files from the cleanup-working backup and the non-working one, I found a missing setting. I hand-edited the corresponding script (\ProgramData\Acronis\TrueImageHome\Scripts) and added the following to the <stream_options> section:
<quota chain_count="1" scheme_flags="18" type="8" />
This was entirely missing from the non-cleaning-up backup. I restarted ATI after making the change. That did the trick. I've let this backup run for two cleanup cycles now and it has cleaned up the old chain both times. For whatever reason, I absolutely could not add this setting via the GUI. It would show the cleanup setting at the time I made the edit and saved, but whenever I went back in to look at the config in the GUI, it was back to having no cleanup.
The first three backups had no problem with this. The 4th and 5th both did. Not sure what's up with that, but I did manage to figure out a workaround.
- Log in to post comments

Well done for the investigative work done here in figuring out the cause of this strange issue!
Thanks for sharing your findings!
- Log in to post comments

Tech OHPRS wrote:For whatever reason, I absolutely could not add this setting via the GUI. It would show the cleanup setting at the time I made the edit and saved, but whenever I went back in to look at the config in the GUI, it was back to having no cleanup.
Such odd issues could be caused by the antivirus software blocking certain Acronis components during the check, I'd try whitelisting Acronis components and executables per the instructions from https://kb.acronis.com/content/46430
Thank you for sharing your solution with the community!
- Log in to post comments

Ekaterina: Thanks for you comment. That link may prove useful int the future. We are running Norton Security on all office workstations along with Acronis, EXCEPT the computer discussed in this thread! This Windows 7 computer is a database server and has no email client installed and no user logging in.
- Log in to post comments