Skip to main content

Why does TI2018 take 2 days to backup 60GB C: drive to a local hard drive in same PC?

Thread needs solution

After all the recent Windows 10 updates TI2018 now takes 2 days to backup a 70gb SSD "C" drive to another local hard drive within the same PC.  Similar "forever" time problems noted in earlier TI versions but nothing relevant in 2018 FAQs nor users forum.  McAfee removed and only Windows Defender remains.  Acronis VSS doctor has been run.  Acronis Disk Director and Acronis UR  also removed and TI2018 has now been completely uninstalled twice and then newly reinstalled to no avail.    There is nothing taking up significant CPU activity. Now, after almost an hour, TI2018 has backed up 1.2GB and is still trying to estimate the amount of time remaining.  TI2018 shows 0% CPU activity with an occasional blip to 3%.  Any help would be appreciated.

0 Users found this helpful

One suggestion for you since you have done all of the above, disconnect the data cables in the computer from the motherboard to each internal drive, one at a time, on both ends of the cable, and reattach them.  Poor cable connections and poor quality cables can have a huge impact on performance.

Regular Poster
Posts: 198
Comments: 120

Frank,

I did a test to make sure my SSD backup was still performing ok.

I created a new backup task system drive (C), used differential (Do not care for incremental), manual (not scheduled) and reset performance to "Normal" because I noticed it defaulted to "Low".

Hardware:  Internal SSD 500GB  approx 220 used, Backup drive: Sata 2, 2 TB also internal in a hot swap tray.

Started the backup and was finished in about 21 minutes.

I have included a snapshot of my log file.

I am sure the very helpful MVP's here can help you analyze your problem and help you fix it.  They have helped me so many times !

Here is my log file:

12/27/2017 9:57:38 AM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
12/27/2017 9:57:38 AM: Operation SSD_500_B started manually.
12/27/2017 9:57:39 AM: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
12/27/2017 9:57:39 AM: Operation: Backup
12/27/2017 9:57:39 AM: Create Backup Archive From: Disk 1 To file: K:\SSD\SSD_500_B\SSD_500_B.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\tech1\AppData\Local\Temp, C:\Users\tech1\AppData\Local\Microsoft\Windows\INetCache, C:\Users\tech1\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\tech1\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\tech1\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\tech1\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\tech1\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\WINDOWS\CSC
12/27/2017 9:57:39 AM: Pending operation 173 started: 'Creating partition image'.
12/27/2017 9:58:13 AM: Writing full version to file: SSD_500_B_full_b1_s1_v1.tib
12/27/2017 10:18:29 AM: Pending operation 173 started: 'Creating partition image'.
12/27/2017 10:18:29 AM: Pending operation 173 started: 'Creating partition image'.
12/27/2017 10:18:29 AM: The following backups have been successfully created: K:\SSD\SSD_500_B\SSD_500_B_full_b1_s1_v1.tib
12/27/2017 10:18:29 AM: Operation has succeeded.

Start: 12/27/2017 9:57:38 AM
Stop: 12/27/2017 10:18:29 AM
Total Time: 00:20:51

I will be watching your thread so I can become aware of the issue you have and its" eventual resolution.

Regards,

Steve F.

 

I changed out the SATA cables to no avail.  TI2018 takes almost 5 minutes to load telling me "applying user data".  Another totally new full backup has been running for hours and tells me there is still another day to go.  Where is this log file within the TI2018 Windows folder?  Thanks again, Frank

The logs can be found at C:\ProgramData\Acronis\TrueImageHome\Logs\ti_demon

Here is the ti_demon log file for a simple, new, backup which took over a day and then failed to validate at which time I cancelled the operation:

2017-12-30T08:47:10:293-05:00 10208 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2017-12-30T08:47:10:295-05:00 10208 I00640002: Operation SSD2SC120GC2DH08T-T started manually.
2017-12-30T08:47:19:647-05:00 10208 I00640000: Backup reserve copy attributes: format tib; need_reserve_backup_copy false;
2017-12-30T08:47:19:662-05:00 10208 I013C0000: Operation: Backup
2017-12-30T08:47:19:678-05:00 10208 I0064000B: Priority changed to High.

2017-12-30T08:47:19:725-05:00 10208 I000B03F0: <bold>Create Backup Archive</bold><endl/><tabpoint value=30><indent value=4>From:    <indent value=10><textcolor value="navyblue">Disk 1</textcolor></indent><indent value=4><endl/>To file:    <indent value=10><textcolor value="navyblue">"E:\Backup\SSD2SC120GC2DH08T-T.tib"</textcolor></indent><indent value=4><endl/>Compression:    <indent value=10><textcolor value="navyblue">Normal</textcolor></indent><indent value=4><endl/>Exclude:    <indent value=10><textcolor value="navyblue">Files matching mask</textcolor></indent><indent value=4><endl/>Match criterion:    <indent value=10><textcolor value="navyblue">hiberfil.sys, pagefile.sys, $Recycle.Bin, swapfile.sys, System Volume Information, *.tib, *.tib.metadata, *.~, *.tmp, C:\Users\Ervin\AppData\Local\Temp, C:\Users\DefaultAppPool\AppData\Local\Temp, C:\Users\Ervin\AppData\Local\Microsoft\Windows\INetCache, C:\Users\DefaultAppPool\AppData\Local\Microsoft\Windows\INetCache, C:\Users\Ervin\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\Ervin\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\Ervin\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\Ervin\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\Ervin\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\Users\DefaultAppPool\AppData\Local\Mozilla\Firefox\Profiles\*\cache2, C:\Users\DefaultAppPool\AppData\Local\Mozilla\Firefox\Profiles\*\OfflineCache, C:\Users\DefaultAppPool\AppData\Local\Opera Software\Opera Stable\Cache, C:\Users\DefaultAppPool\AppData\Local\Opera Software\Opera Stable\Media Cache, C:\Users\DefaultAppPool\AppData\Local\Google\Chrome\User Data\Default\Cache, C:\WINDOWS\CSC</textcolor></indent><indent value=4><endl/></indent><endl/>

2017-12-30T08:47:19:772-05:00 10208 I000101F8: Pending operation 173 started: 'Creating partition image'.
2017-12-30T08:47:20:037-05:00 8560 I00640000: Writing full version to file: SSD2SC120GC2DH08T-T_full_b1_s1_v1-3.tib
2017-12-30T08:47:32:006-05:00 10208 I000101F8: Pending operation 173 started: 'Creating partition image'.
2017-12-31T06:29:04:166-05:00 10208 I000101F8: Pending operation 173 started: 'Creating partition image'.
2017-12-31T06:42:45:801-05:00 10208 I000101F8: Pending operation 173 started: 'Creating partition image'.
2017-12-31T06:42:52:149-05:00 10208 I00640000: The following backups have been successfully created:<endl/>"E:\Backup\SSD2SC120GC2DH08T-T_full_b1_s1_v1-3.tib"
2017-12-31T06:42:54:150-05:00 10208 I000B0402: <bold>Validate Backup Archive</bold><endl/><tabpoint value=30><indent value=4>Location:    <indent value=10><textcolor value="navyblue">"E:\Backup\SSD2SC120GC2DH08T-T_full_b1_s1_v1-3.tib"</textcolor></indent><indent value=4><endl/></indent><endl/>
2017-12-31T06:42:54:172-05:00 10208 I000101F8: Pending operation 4 started: 'Validate Backup Archive'.
2017-12-31T06:57:40:442-05:00 10208 I00040001: Error 0x40001: Error occurred while reading the file.
| trace level: information
| line: 0x1d8eab676a3f695f
| file: c:\bs_hudson\workspace\245\products\imager\archive\impl\operations\archive_message_callback.cpp:822
| function: TrueImage::Archive::ArchiveMsgReadCallbackProcessor::ProcessReadCallback
| line: 0x1d8eab676a3f695f, c:\bs_hudson\workspace\245\products\imager\archive\impl\operations\archive_message_callback.cpp:822, TrueImage::Archive::ArchiveMsgReadCallbackProcessor::ProcessReadCallback
| Path:
| $module: ti_demon_vs_10640
|
| error 0x40001: Error occurred while reading the file.
| line: 0x7ceb2cdc9fb1203c
| file: c:\bs_hudson\workspace\245\core\file\windows\win32_file.cpp:147
| function: win32_file::Read
| line: 0x7ceb2cdc9fb1203c, c:\bs_hudson\workspace\245\core\file\windows\win32_file.cpp:147, win32_file::Read
| function: ReadFile
| $module: ti_demon_vs_10640
|
| error 0xfff0: Data error (cyclic redundancy check)
| line: 0xbd28fdbd64edb8f1
| file: c:\bs_hudson\workspace\245\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\245\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070017
| $module: ti_demon_vs_10640
2017-12-31T16:05:41:943-05:00 10208 I00040001: Error 0x40001: Error occurred while reading the file.
| trace level: information
| line: 0x1d8eab676a3f695f
| file: c:\bs_hudson\workspace\245\products\imager\archive\impl\operations\archive_message_callback.cpp:822
| function: TrueImage::Archive::ArchiveMsgReadCallbackProcessor::ProcessReadCallback
| line: 0x1d8eab676a3f695f, c:\bs_hudson\workspace\245\products\imager\archive\impl\operations\archive_message_callback.cpp:822, TrueImage::Archive::ArchiveMsgReadCallbackProcessor::ProcessReadCallback
| Path:
| $module: ti_demon_vs_10640
|
| error 0x40001: Error occurred while reading the file.
| line: 0x7ceb2cdc9fb1203c
| file: c:\bs_hudson\workspace\245\core\file\windows\win32_file.cpp:147
| function: win32_file::Read
| line: 0x7ceb2cdc9fb1203c, c:\bs_hudson\workspace\245\core\file\windows\win32_file.cpp:147, win32_file::Read
| function: ReadFile
| $module: ti_demon_vs_10640
|
| error 0xfff0: Data error (cyclic redundancy check)
| line: 0xbd28fdbd64edb8f1
| file: c:\bs_hudson\workspace\245\core\common\error.cpp:307
| function: Common::Error::AddWindowsError
| line: 0xbd28fdbd64edb8f1, c:\bs_hudson\workspace\245\core\common\error.cpp:307, Common::Error::AddWindowsError
| code: 0x80070017
| $module: ti_demon_vs_10640
2017-12-31T16:07:02:450-05:00 10208 I013C0006: Operation has succeeded.

 

Again, any advice would be appreciated.  Am I having a destination hard disk failure causing all this?

Frank

I would say looking at your log that you have suffered a failed Windows update installation, presumably a Creators edition update in which the required files were either corrupt or missing or both.  This is evident due to the CRC and 0x80070017 errors listed in the log.

My advice would be first to manually run the Windows update utility to check for updates.  You may find that updates are already listed there for install.  If you find these or if a check shows updates available then download and/or install them.

If these update installs fail then I would recommend that you run chkdsk \f on the C: drive to find and fix any corruption in the file system.  Chkdsk /r in this case should not be necessary. 

Frank, there are several issues indicated in your backup log above.

Writing full version to file: SSD2SC120GC2DH08T-T_full_b1_s1_v1-3.tib where the v1-3 portion of the file name suggests that ATI encountered a file or files with the same name in the backup destination location, hence the additional -3 added to the file name.

Next, after the file is created, Validation is failing due to:

Error 0x40001: Error occurred while reading the file.
error 0xfff0: Data error (cyclic redundancy check)

Both of these errors suggest that the data created by ATI is not being written successfully to your backup drive (E:\Backup) location, which depending on the type of drive and how this is connected?

If this is an external drive, then you may have a failing USB cable or the drive itself may be starting to fail.  I would recommend running CHKDSK E: /R against the backup drive to see if this throws out any errors which can be corrected.  Note: /R will cause a check for bad sectors so may take an extended time if the drive is large.

You may also want to check the drive manufacturers support site for any drive diagnostic utilities they provide.

All is well.  The hard drive was bad.  Chkdsk was taking forever after no problems initially found so used a free HD application from WD for their HD which quickly noted errors and then reported could not be fixed.  TI2018 now runs quickly with new internal HD.  Thanks for help!

Frank

Frank, thanks for the update, glad you have identified the cause of this issue and have replaced the failing drive.

Ditto Frank, glad to see you found the problem.