Upgrading from 2014: What data is held in the cloud and what issues should I be aware of?
I've been a long term user of version 2014. When using with windows 10 (which I realise is not supported) I'm now starting to get "An error occured while working with Extended Capacity disk driver." error, and I've also not tested restoring for some time.
Perhaps time to upgrade...
So, I am trialing the 2018 version on another windows 10 PC and, being someone who does not like the thought of anything stored in the cloud (I would buy the one off purchase and not the subscription and back up to local NAS), I logged in, as it asks to during the setup, and I can now see a 'Cloud Dashboard' which has a record of the backups I am setting up, even though I am not backing up to the cloud.
Whilst I don't think its sending any backup data beyond the local LAN (at least I hope not), I don't actually even want the names of my computers or backup jobs in the cloud.
1) Can this information be deleted/disabled?
2) On the Cloud Dashboard it says "Backup Now" next to he PC name. I've not subscribed to the cloud, what happens when I click it?
(I realise now that you don't _have_ to log in to use the software, which is misleading, but it still has left traces of my backups on the cloud that I cannot delete, and I'm not sure if it continues to do so even when not logged in)
Also, are there any other current issues I should be aware of before I make the switch from version 2014? I notice it appears that verion 2018 can now restore 2014 archives which is a bonus.
Thanks in advance for any helpful replies.


- Log in to post comments

Thanks Steve. Does that mean I can still keep my .tib files from ATI 2014 on the NAS and recover them when I want to?
I have been very happy with ATI 2014 and am upgrading reluctantly.
I'm testing the product within the bootcamp partition of a mac (i.e. using the windows version within Windows 10). Unfortunately, I've not been able to carry out a single backup yet due to the following error:
error 0x70021: Unable to create volume snapshot
line: 0xdf81da2c74ec50d5
file: c:\bs_hudson\workspace\431\core\resizer\backup\output_stream.cpp:275
function: `anonymous-namespace'::OutputStreamImpl::SetBitmap
line: 0xdf81da2c74ec50d5, c:\bs_hudson\workspace\431\core\resizer\backup\output_stream.cpp:275, `anonymous-namespace'::OutputStreamImpl::SetBitmap
$module: ti_demon_vs_12510
I can see many references to this issue, but few solutions. There is no corruption on the disk and the VSS Doctor points out no issues.
- Log in to post comments

Please see KB 1689: Backup archive compatibility across different product versions for confirmation of the ability of ATI 2018 to deal with archives from older versions of the product.
For the 'Unable to create volume snapshot' issue, I have no experience with running ATI on a Mac so cannot advise on what this may mean in this context.
See KB 59440: Acronis True Image 2017: 'Snapshot for backup' option overview which shows how to change the settings to revert to the older ATI own snapshot method instead of using MS VSS for this, or not using a snapshot at all.
- Log in to post comments

Thanks Steve. Just to clarify, I'm not running this on MacOS. I'm running the Windows ATI 2018 build in Windows 10.
I've tried all configurations of VSS, including not making a snapshot at all....yet it still fails with the same error:
Error 0x101f6: Unable to create volume snapshot
| trace level: error
| line: 0x65b5eb7011094700
| file: c:\bs_hudson\workspace\431\processor\diskadm\da_commit.cpp:345
| function: DaProcessor::CommitImpl::OnDaError
| line: 0x65b5eb7011094700, c:\bs_hudson\workspace\431\processor\diskadm\da_commit.cpp:345, DaProcessor::CommitImpl::OnDaError
| $module: ti_demon_vs_12510
|
| error 0x70021: Unable to create volume snapshot
| line: 0xdf81da2c74ec50d5
| file: c:\bs_hudson\workspace\431\core\resizer\backup\output_stream.cpp:275
| function: `anonymous-namespace'::OutputStreamImpl::SetBitmap
| line: 0xdf81da2c74ec50d5, c:\bs_hudson\workspace\431\core\resizer\backup\output_stream.cpp:275, `anonymous-namespace'::OutputStreamImpl::SetBitmap
| $module: ti_demon_vs_12510
|
| error 0x10c44e: Failed to set snapshot bitmap.
| line: 0x3fec04e376b89f2d
| file: c:\bs_hudson\workspace\431\core\fdisk\win_snapshot.cpp:567
| function: win_snapshot_volume::SetBitmap
| line: 0x3fec04e376b89f2d, c:\bs_hudson\workspace\431\core\fdisk\win_snapshot.cpp:567, win_snapshot_volume::SetBitmap
| blocks: 0x0
| $module: ti_demon_vs_12510
|
| error 0x9: Unknown status.
| line: 0x2aacb7b2ab852ac
| file: c:\bs_hudson\workspace\431\core\fdisk\ver2\arch\windows\win_errors.cpp:40
| function: Fdisk::AddKstatusError
| line: 0x2aacb7b2ab852ac, c:\bs_hudson\workspace\431\core\fdisk\ver2\arch\windows\win_errors.cpp:40, Fdisk::AddKstatusError
| code: 0x57
| $module: ti_demon_vs_12510
|
| error 0xfff0: The parameter is incorrect
| line: 0xbd28fdbd64edb8f1
| file: c:\bs_hudson\workspace\431\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\431\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070057
| $module: ti_demon_vs_12510
Error 0x13c0005: Operation has completed with errors.
| trace level: error
| line: 0x9f2c53c72e8bce5f
| file: c:\bs_hudson\workspace\431\products\imager\demon\main.cpp:617
| function: main
| line: 0x9f2c53c72e8bce5f, c:\bs_hudson\workspace\431\products\imager\demon\main.cpp:617, main
| $module: ti_demon_vs_12510
I was about to paste in what build of ATi I' using...but the about box does not have anything relating to the version. Having a few issues with the minimal layout, hope I get used to it.
- Log in to post comments

I'm testing the product within the bootcamp partition of a mac (i.e. using the windows version within Windows 10).
Understand that you are running ATI on Windows 10 but this is still hosted by Mac via bootcamp, for which I have no experience, hence my comment, as I do not know what differences bootcamp brings to the party here?
Perhaps the other question not asked here would be: what exactly are you trying to backup when this error is given?
- Log in to post comments

I am backing up anything as a test. I've tried the entire windows drive, and I've also tried a single file, both to a local NAS and to the same local drive (in the case of the file). As mentioned I've also tried switching off VSS/Snapshots altogether in the backup options.
But the error remains.
Regarding running on Mac hardware - I don't believe this is the cause as I've also tested other backup products utilisiing VSS on this windows 10 installation without any issues. I've no reason to believe it would make any difference.
- Log in to post comments

Sorry but not sure how to help further here other than to recommend that you open a Support Case direct with Acronis and let them investigate this issue with you.
- Log in to post comments

Thanks Steve for your help. I think at the moment I'm a little concerned. I've been reading a lot of criticism of Acronis over the years - some quite vocal users on this forum. I've not had any issues myself, but there again only used the 2014 version.
To have a very basic issue on a basic install of Windows 10 is worrying.
I have to ask, and forgive me if I am wrong, but is this one of the developers account names in the error messages?
c:\bs_hudson\workspace\
- Log in to post comments

Good question about the name in the detailed error messages but have no answer to it. That name appears in all of the recent logs going back quiite some time, so your guess is as good as any.
- Log in to post comments

Well here's a thing.
I removed Acronis and went to install Paragon as a trial, but decided against it as it does not have backup encryption (sorry if I'm not allowed to mention other software)
So I decided to try Acronis again so re-installed, this time downloading it again, realising a new build had been released on 20th (I think I downloaded a few days before).
I also disabled my anti-virus momentarily whilst it did its first test back up of a folder. As that worked, I've now re-enabled it and it doesn't appear to be the original cause.
At the moment it appears to be backing up ok.The only thing I did differently, is I did not sign in on install.
I still get the same error if I try to back up the entire computer, but if I select the windows drive specifically, it seems to working (so far).
So fingers crossed....
One annoying thing is that it keeps presenting me with the log in screen whenever I start the app. Hopefully that won't hinder automatic backups.
- Log in to post comments

Just wanted to repeat an earlier criticism in my thread here, despite the fact that I continue to use both Acronis 2014 (a better product in my oppinion) and 2018 more due to the fact its what I'm used to.
I find it quite unprofessional that the apparent developers name and his/her file heirachy is shown in the backup logs:
e.g. c:\bs_hudson\workspace\431
This is something that gives me a good idea of the quality of the code behind the scenes - not impressed at all.
- Log in to post comments

Please submit Feedback on this issue to the developers via the tool provided in the GUI. I am not sure that hudson is a developer name and haven't come across anyone with that name in my own interactions with them, but who knows?
- Log in to post comments

Hi Steve,
Whether its the developer's name or not, it gives away information about the code that could be used maliciously. Its not normal, and definately not good practice to have error codes being pushed out with such information about the machine used to compile the software, as I'm sure you're aware.
It is making me hesitate and look for other products. Think I might open a new thread here deciated to the issue, in the hope someone at Acronis takes note.
- Log in to post comments