Does not delete backup file when you choose delete entire backup
The first release of 2016 worked fine, but with the last 2 releases, when you choose a backup, choose delete, and choose delete file, it does not delete the file. Certainly just a minor annoyance, but it should work.
I can confirm Grover's findings same thing in my tests.
Yes, I have seen the same thing. However, I tried this yesterday and while the task was deleted the backup is still there. In addition, when I try to open ATI 2016 I get 'cannot create base' warning - cannot at the moment remember the solution to problem. Why it is trying to create data base when one already exists is perplexing.
Ian
I am choosing to delete the entire backup, but the file is not deleted.
Very strange, I have never found this to be the case. I recommend reporting this behavior using the feedback feature under the Help selection on the left side of the app GUI. Including a system report with the feedback would be recommended.
This is fixed in Build 5586. The two backups that did not delete yesterday using build 5576 were deleted today.
Ian
PS I managed to sort out the issue with data base creating by un-installing 2016, cleaning up the leftover files, and installing build 5586.
That's good to hear, now if a new cleanup tool would be released.... In good time.
This is fixed in Build 5586. The two backups that did not delete yesterday using build 5576 were deleted today.
Ian
PS I managed to sort out the issue with data base creating by un-installing 2016, cleaning up the leftover files, and installing build 5586.
Definitely needed as soon as possible. Most users would not be able to do the clean-up manually.
Ian
I can confirm that this problem was fixed by uninstalling everything Acronis, using the clean tool for Win 10 as edited in another thread, and reinstalling. Quite an annoyance, though, and this sort of thing should never happen in a well written piece of software. If you cannot upgrade properly, just require an uninstall before installing the new version.
Windows 10, fully patched:
I am having exactly the same problem right now with 2017, been running for about three hours with no result (deleting the entire backup). It has NEVER worked for me in previous versions either. The application hangs, and eventually needs to be terminated by drastic means. The backup files, I delete manually.
Don, as the previous poster noted, this issue was cleared by doing a clean install of the product.
If your ATIH 2017 was an upgrade from an earlier version / earlier versions, i.e. upgraded from 2014 to 2015 to 2016 etc then a clean install is recommended by Acronis themselves in the 2017 FAQ document which states:
If you already have Acronis True Image 2016 or Acronis True Image 2015 installed, there is no need to remove the old version and reinstall the software. Start the installation file of Acronis True Image 2017 and install the product. After upgrade, create a new bootable media.
If you already have Acronis True Image 2014 or older versions, you need to delete these first and then install Acronis True Image 2017.
To do a clean install, uninstall your current application normaly via the Control Panel.
Note: You can save your task configuration by making a copy of the C:\ProgramData\Acronis\TrueImageHome\Scripts folder.
Download the Acronis Cleanup Tool (link below in my signature) - run this as Administrator, then restart to complete.
Download the ATIH 2017 build 5554 full installer from your Acronis account if you don't already have this, then install as Administrator. Copy back the contents of the Scripts folder if saved, omitting any tasks you don't want to keep - you can edit the .TIS files in any standard text editor such as Notepad to check which script relates to which task. Task name is near the top of the XML data in the file.
Hi Steve,
I just wrote an extrensive post, hit "post" and it has disappeared. In it I mentioned that I had lost faith with Acronis and that I would rely on my substantial IT background to get me out of trouble.
PS: I have a new laptop, set up the backup, and ran the first seamlessly. Today, my "Monday" backup (incremental) ran perfectly - except that the first incremental file was created with yesterday's date, time 20:06 .... this is the log from this morning:
1 Acronis True Image 5/12/2016 9:00:01 AM Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2 Acronis True Image 5/12/2016 9:00:01 AM Operation Monday_Acer started by schedule.
3 Acronis True Image 5/12/2016 9:00:13 AM Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
4 Acronis True Image 5/12/2016 9:00:13 AM Operation: Backup
5 Acronis True Image 5/12/2016 9:00:13 AM Priority changed to Low.
6 Acronis True Image 5/12/2016 9:00:21 AM Create Backup Archive From: ESP (1-1), Recovery (1-5), C-Drive (C:) To file: "nas://MYBOOKLIVE/Public/AcronisBackups/LaptopOne/Monday_Acer.tib" Compression: Normal Exclude: Files matching mask Match criterion: hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\donander\AppData\Local\Temp, C:\Users\scheduler\AppData\Local\Temp, C:\Users\robander\AppData\Local\Temp, C:\Users\donander\AppData\Local\Microsoft\Windows\INetCache, C:\Users\scheduler\AppData\Local\Microsoft\Windows\INetCache, C:\Users\robander\AppData\Local\Microsoft\Windows\INetCache, C:\Users\donander\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Users\donander\AppData\Local\Opera Software, C:\Users\donander\AppData\Local\Mozilla\Firefox\Profiles, C:\Users\donander\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Users\donander\AppData\Local\Opera Software, C:\Users\donander\AppDat
a\Local\Mozilla\Firefox\Profiles, C:\Users\donander\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Users\donander\AppData\Local\Opera Software, C:\Users\donander\AppData\Local\Mozilla\Firefox\Profiles, C:\WINDOWS\CSC, c:\software
7 Acronis True Image 5/12/2016 9:00:40 AM Pending operation 172 started: 'Creating partition image'.
8 Acronis True Image 5/12/2016 9:00:41 AM Pending operation 172 started: 'Creating partition image'.
9 Acronis True Image 5/12/2016 9:05:50 AM Writing incremental version to file: Monday_Acer_inc_b1_s2_v1.tib
10 Acronis True Image 5/12/2016 9:20:08 AM Pending operation 172 started: 'Creating partition image'.
11 Acronis True Image 5/12/2016 9:20:09 AM Pending operation 172 started: 'Creating partition image'.
12 Acronis True Image 5/12/2016 9:20:10 AM The following backups have been successfully created: "nas://MYBOOKLIVE/Public/AcronisBackups/LaptopOne/Monday_Acer_inc_b1_s2_v1.tib"
13 Acronis True Image 5/12/2016 9:20:12 AM Operation has succeeded.
There was no file dated today. This aftrnoon, I ran another backup and got a file with a sensible date/time.
Just another abberation (apart from the never deletes an entire backup issue).
I'm a programmer. I understand the complexities of software development & testing, having been with a large corporation but .............. is this good enough?
Why should an end user have to go thru the uninstall / reinstall routine to fix something that should have been covered by the developers? Wny was 5554 still available to download when 5555 was a known fix for a licencing problem?
Convince me ....
Don, thanks for the further information and sorry to hear of further issues. I would be guessing to try to suggest why your backup file had yesterdays date / time stamp when it was created today.
It isn't my role here to try to convince you one way or another with regard to this Acronis product. I am just another user, like yourself, with my own extensive IT background and experiences - I do not work for Acronis and can only offer advice based on my time spent using the products and helping in these forums.
I was never a programmer, so bow to your superior knowledge & experience in that area - my background was in technical support in both hardware and software at IBM for over 30 years before taking my pension. I agree that users shouldn't need to uninstall / reinstall the application to fix something but reality is that this does work in many cases and is often a lot quicker than waiting for a strange or intermittent problem to be analysed, and a software fix produced, assuming that Acronis development can either reproduce the problem or garner sufficient diagnostic information to do so.
With regards to 5555 versus 5554 - 5555 is simply an expedient patch that users can apply for specific problems - 5554 is the latest build version until Acronis release a further build which will then pick up the 5555 patch plus fixes for other issues they are working on.
Fair comments Steve. Appreciate your time and effort.
My software, of course, never had any problems <grin> except when we rolled out a nation-wide application without sufficent server resources. Testing with nominated sites went off without a hitch (of curse course)
We did have a fallback though, rapidly implemented while some new hardware was sourced. A week of embarrassment, lots of aggrieved end users and annoyed upper management. I was sufficently removed from the front line to go unnoticed and have remained that way until today ........
I'll sleep on it.