Skip to main content

ATI2020 SSD died, replaced with a larger SSD (only partition on drive) and my 'troubles' started.

Thread needs solution

Wife's PC (W10 Pro V1903 with the latest update as of 11/11) had the C: SSD (single partition and the boot drive) die. So I go out locally and she had a 240GB SSD but all I could get was a 500GB SSD. Installed is, disconnected ALL drives and used Windows Media Creation tool to set the drive as a boot drive and install W10. Made sure it worked. Then my troubles started...

First problem:

I loaded the Rescue DVD and attached the external backup drive (left to other internal drives disconnected so to be sure not to overwrite them). Clicked on RESTORE and had no problem finding the C: partition in the BACKUP location I wanted. Now the fun started... next screen (I am going by memory from yesterday) showed the install location not selected? I clicked on it an all I heard be computer beeps? Thinking I did something wrong and on every possible link or X I'd gotten a beep, I rebooted and wound up in the same place? So I went to my PC to open the Manual and I was doing it right. That took a few minutes. When I got back to her PC the link for location was now blue and I could set it. Also set it as bootable. Why it took so long to recognize, beyond me. Last time (ATI2016 I think) this was immediate where I could select the target?

So it start RESTORING, at least it said that and computing time. We're talking about a 70GB's worth of data backup, by the way. After about 15 minutes it actually start to move the bar, and it was about 20 minutes to restore.

OK, system restore and I connected all the other drives. Everything worked fine. Ran Windows and Norton Update to make sure no updates were lost in the 5 days since the backup.

So today's problem....

Normal day to backup and if failed, said it couldn't find the C:, D:, or E: drives (the 3 normally backed up). Figured out it didn't know about the new C:. Edited the backup job and clicked on C: and the boot sector.

Manually restarted the job... It took some time but eventually stated a 996GB back-up with over 8 hours to do it? Normally it was only 770GB's that were backed up to about 550GB's. Well, it seems when the PC goes to SLEEP, ATI must stop. Right now, 1 1/2 hours to go, only 465GB's backed up, so that might be the same approximate size as the others when done, bar is about 80% done.

We both think it used to take about 3 hours before?

I know her PC is setup like mine and supposed to not let it go to sleep and speed is 'normal' without verification.

Shouldn't the change of SSD be basically transparent and not cause a problem once identified to the backup job?

I guess I can look at the LOG when done, but was wondering why the RESTORE process took so long to recognize the only drive other than the External drive that was connected and the long pause before the actual recovery started as well as why is this now an 8 hour backup job? If need be I can start another job and take screenshots if needed?

0 Users found this helpful

Irv,

TI 2020 is decidedly a different cat than previous versions.  Frankly, your descriptions of events are expected behavior with 2020.  It may seem that this behavior is a step backwards but that really is not the case at all.  The new behavior is actually due to behind the scenes scans and checks run to insure reliability.  

  So I went to my PC to open the Manual and I was doing it right. That took a few minutes. When I got back to her PC the link for location was now blue and I could set it. Also set it as bootable. Why it took so long to recognize, beyond me. Last time (ATI2016 I think) this was immediate where I could select the target?

Once you choose to Recover the app begins by scanning attached disks for errors.  This can take the few minutes you spent at your computer checking on the documentation.

Normal day to backup and if failed, said it couldn't find the C:, D:, or E: drives (the 3 normally backed up). Figured out it didn't know about the new C:. Edited the backup job and clicked on C: and the boot sector.

Manually restarted the job... It took some time but eventually stated a 996GB back-up with over 8 hours to do it? Normally it was only 770GB's that were backed up to about 550GB's.

True images time remaining and total data numbers will be inaccurate at times and should only be considered as an indication the app is working on the requested process.  As the process moves along reflected number accuracy will improve.

Shouldn't the change of SSD be basically transparent and not cause a problem once identified to the backup job?

Yes it should.  When you chose to use the existing backup task for the new drive however, that brings in all new everything so the app must now make corrections to the task to remove old information that no longer applies and replace that with what does apply now.  A doubling of processing if you will.  Now that you have the new information stored in the app database times should improve.  Having said that, there will be periods where times do increase dependent on your task configuration.

 

OK, thanks for the reply and I now understand. The part that seemed the throw me the most was the DVD boot Restore when I had links (in black, not blue) showing and I couldn't click on anything, not even the X to close it? All I got was beeps. Might have been nice to see a 'Processing' or 'Reading drives' with a sliding or circling bar along with it.

This is the e-mail log she got:

=================

> On 11/13/2019 9:07:37 PM, lsp@c.com wrote:
> > 2019-11-13T11:30:14:758-05:00 916 I00000000: -----
> 2019-11-13T11:30:14:758-05:00 916 I00000000: ATI Demon started. Version: 24.4.1.21400.
> 2019-11-13T11:30:14:804-05:00 916 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
> 2019-11-13T11:30:14:820-05:00 916 I00640002: Operation LARAINE-C, D, and E started manually.
> 2019-11-13T11:30:14:989-05:00 916 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
> 2019-11-13T11:30:14:989-05:00 916 I013C0000: Operation: Backup
> 2019-11-13T21:07:34:323-05:00 916 I013C0006: Operation has succeeded.
>
===============

As you can see, 9 1/2 hours that used to take about 3 hours. File size when done, only 1GB more than the last ones which were all around the 555GB size +/- a GB. Log isn't really showing much. From looking at it it took less than a second to actually start the backup, yet the screen took a real long time before the bar started to move and even longer to show the time.

I went to her PC and found this file, a tnd log file for yesterday. Has some errors in it repeated:

----------------

[20191113-004710-220][tnd][T] build: 2440, process: 15112, 'C:\Program Files (x86)\Acronis\TrueImageHome\TrueImageMonitor.exe'
[20191113-004710-220][tnd][T] 2019.11.13 00:47:10 UTC
[20191113-004710-220][tnd][T] 2019.11.12 19:47:10 LOCAL
[20191113-004710-220][tnd][T] Initialize Tnd API
[20191113-004710-220][tnd][E] Failed to open control device '\\.\Global\TndControl2440': status 2
[20191113-004710-220][tnd][E] Failed to initialize: error 0x2
[20191113-004715-234][tnd][T] Initialize Tnd API
[20191113-004715-234][tnd][E] Failed to open control device '\\.\Global\TndControl2440': status 2

----------------

Many of these same files since the install it seems daily with the same data? Is this a problem? May not be, my PC has the same?

Did use the LogViewer. Here is the total log for the backup:

------------------------

11/13/2019 11:26:56 AM: -05:00 16696 I00000000: -----
11/13/2019 11:26:56 AM: -05:00 16696 I00000000: Application started. Version: 24.4.1.21400.
11/13/2019 11:26:56 AM: -05:00 16696 I00000000: Console start: starting...
11/13/2019 11:26:56 AM: -05:00 16696 I00000000: GetDisplayInfo succeeded: DPI: 96, scaling: 100%. Monitors: Resolution: 1920x1200, work area: 1920x1160, physical DPI: 76.
11/13/2019 11:26:56 AM: -05:00 16696 I00000000: EnableHiDpiScaling - use system scaling.
11/13/2019 11:26:56 AM: -05:00 16696 I00000000: Stored GA client (application: ATI2020 module: console session: E2DBABE7-CBDE-426E-B416-A4E8BF033893
11/13/2019 11:26:58 AM: -05:00 18636 I00000000: >> TrueImage::UI::ConsoleManager::InitializeExplorer ID=1 Console start: InitializeExplorer
11/13/2019 11:26:58 AM: -05:00 18636 I01530001: Using default upnp detection algorithm.
11/13/2019 11:26:58 AM: -05:00 16696 I00000000: Console start: OnInitializationComplete
11/13/2019 11:26:58 AM: -05:00 16696 I00000000: >> TrueImage::UI::ConsoleManager::CreateUi ID=2 Console start: ConsoleManager::CreateUi
11/13/2019 11:26:58 AM: -05:00 18636 I00000000: << TrueImage::UI::ConsoleManager::InitializeExplorer ID=1 took 0.055 seconds.
11/13/2019 11:26:58 AM: -05:00 16696 I00000000: MandatoryLoginController::Show( Scenario::AUTOLOGIN )
11/13/2019 11:27:06 AM: -05:00 16696 I00000000: >> TrueImage::UI::AtihConsoleDialog::CreatePages ID=3 Console start: CreatePages
11/13/2019 11:27:06 AM: -05:00 16696 I00000000: >> `anonymous-namespace'::ManagerImpl::ManagerImpl ID=4 MediaBuilder::ManagerImpl
11/13/2019 11:27:08 AM: -05:00 16696 I00000000: << `anonymous-namespace'::ManagerImpl::ManagerImpl ID=4 took 1.837 seconds.
11/13/2019 11:27:08 AM: -05:00 16696 I00000000: >> `anonymous-namespace'::ManagerImpl::SelectSurvivalKitMode ID=5 SelectSurvivalKitMode
11/13/2019 11:27:08 AM: -05:00 16696 I00000000: << `anonymous-namespace'::ManagerImpl::SelectSurvivalKitMode ID=5 took 0.000 seconds.
11/13/2019 11:27:09 AM: -05:00 18636 I00000000: CompleteInAppUrl: https://www.acronis.com/redirector/products/atih2020/ap/rss?build=21400…
11/13/2019 11:27:11 AM: -05:00 16696 I00000000: << TrueImage::UI::AtihConsoleDialog::CreatePages ID=3 took 5.205 seconds.
11/13/2019 11:27:11 AM: -05:00 16696 I00000000: Mandatory login will not be shown because user has persistent account
11/13/2019 11:27:11 AM: -05:00 16696 I00000000: << TrueImage::UI::ConsoleManager::CreateUi ID=2 took 12.948 seconds.
11/13/2019 11:27:11 AM: -05:00 16696 I00000000: Console start: started
11/13/2019 11:27:11 AM: -05:00 18772 W00000000: IsSerialRegistered failed with error: Error 0x40011: The specified file does not exist.
| line: 0xa8b6270651f740a3
| file: c:\bs_hudson\workspace\1168\home\common\property_storage_utility.h:56
| function: Home::GetPropertyValue
| line: 0xa8b6270651f740a3, c:\bs_hudson\workspace\1168\home\common\property_storage_utility.h:56, Home::GetPropertyValue
| $module: ti_managers_vs_21400
11/13/2019 11:27:11 AM: -05:00 12660 I00000000: ConnectSchedulerManagerOperation: Scheduler is connected - operation finished
11/13/2019 11:27:11 AM: -05:00 18500 I00000000: License activator. License activated
11/13/2019 5:20:13 PM: -05:00 16696 I00000000: Active protection. Service connected
11/13/2019 9:11:28 PM: -05:00 16696 E0192000D: Error 0x192000d: Callback is not registered.
| trace level: error
| line: 0xcaf802b9a1d59e94
| file: e:\bs_hudson\workspace\mod-imager-syncagent\3400\product\products\imager\home\sync_agent\impl\api\sync_agent_api_man.cpp:756
| function: SyncAgentApi::SyncAgentApiMan::UnSubscribe
| line: 0xcaf802b9a1d59e94, e:\bs_hudson\workspace\mod-imager-syncagent\3400\product\products\imager\home\sync_agent\impl\api\sync_agent_api_man.cpp:756, SyncAgentApi::SyncAgentApiMan::UnSubscribe
| $module: sync_agent_api_vs_3400

--------------------------

The timestamp at start of the log doesn't match the e-mail log? About a 4 minute difference? Also the '\bs_hudson' folder on both C: and E:? I'll assume that this is a temporary work file, but E: on both of our PC's is a USB port that is used for the removable media (not sure which type, as we have Dell's that have different ones on the top). Is that connected to the 'Callback' that isn't registered? Similar E: entries on my PC as well?

 

Irv,

The logs you are looking at are something that only have meaning to Acronis Software Engineers which I am not.  I am an advanced enthusiast user of the product, nothing more.

The usable logs for your backup task would be found in the ti_demon log.  Below is a screenshot of a clean backup I just ran on a laptop.

 

 

 

 

 

That is the same as I posted at the top of my reply, just a little different from the e-mailed copy:

 

-------------

11/13/2019 11:30:14 AM: -05:00 916 I00000000: -----
11/13/2019 11:30:14 AM: -05:00 916 I00000000: ATI Demon started. Version: 24.4.1.21400.
11/13/2019 11:30:14 AM: -05:00 916 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
11/13/2019 11:30:14 AM: -05:00 916 I00640002: Operation LARAINE-C, D, and E started manually.
11/13/2019 11:30:14 AM: -05:00 916 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
11/13/2019 11:30:14 AM: -05:00 916 I013C0000: Operation: Backup
11/13/2019 9:07:34 PM: -05:00 916 I013C0006: Operation has succeeded.

Start: 11/13/2019 11:30:14 AM
Stop: 11/13/2019 9:07:34 PM
Total Time: 09:37:20

-----------------

Basically the same as yours is as the backup did complete OK.