Acronis 2017 backup successful using boot usb but not using Acronis within windows 7

Bernie, if you are getting disk errors when backing up then this is an issue that needs to be addressed.

The log files for the failed backup operations should help show the extent of any disk errors and which disk drive is involved?

Download a copy of the MVP Assistant log viewer tool and use this to look at the logs to see if they show any issues during the operation process?

The latest version of the new log viewer tool is at the link below. 
MVP Assistant - New 2.0 with Rescue Media Builder (New Version 2.1.1)

If you have Disks & Partitions backups created on ATI 2020 or later using .tibx files, then look in the Backup Worker logs.

If you have Files & Folders backups using .tib files (or Disk backups from earlier versions using .tib files) or using Cloning then look in the Demon logs.

Other logs are shown by the MVP Assistant under the 'Active Logs' heading of the Log Viewer page of the Assistant.

The Schedule2 log contains information related to scheduled task but is one of the more difficult logs to read / work through.

The log files should be zipped to preserve their original file names if sharing in the forums and would need to be less than 3MB in size, otherwise you would need to share the zip file via a Cloud share service such as OneDrive, Dropbox etc.

Steve, thanks for the reply. Do you have any idea as to why my backup was noted as successful using the USB Rescue Builder, whereas within Windows 7, I get errors??

When I looked at the chkdsk /f /r log file, it says there were 52 bad sectors noted - however I don't know if the chkdsk managed to move the data to good sectors, or in fact if the bad sectors were simply unused or have no data in them. Thanks for any info you can give.

Also on this Windows 7 system, for some reason, since a month or so, I do not see ANY restore points created or visible.

Here's a copy of the last chkdsk /f /r log file (Also uploaded as an attachment here)::

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

Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows.

A disk check has been scheduled.
Windows will now check the disk.                         

CHKDSK is verifying files (stage 1 of 5)...
  300544 file records processed.                                          File verification completed.
  1389 large file records processed.                                      0 bad file records processed.                                        2 EA records processed.                                              152 reparse records processed.                                       CHKDSK is verifying indexes (stage 2 of 5)...
  365594 index entries processed.                                         Index verification completed.
  0 unindexed files scanned.                                           0 unindexed files recovered.                                       CHKDSK is verifying security descriptors (stage 3 of 5)...
  300544 file SDs/SIDs processed.                                         Cleaning up 270 unused index entries from index $SII of file 0x9.
Cleaning up 270 unused index entries from index $SDH of file 0x9.
Cleaning up 270 unused security descriptors.
Security descriptor verification completed.
  32526 data files processed.                                            CHKDSK is verifying Usn Journal...
  37263008 USN bytes processed.                                             Usn Journal verification completed.
CHKDSK is verifying file data (stage 4 of 5)...
  300528 files processed.                                                 File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
  50986701 free clusters processed.                                         Free space verification is complete.
Windows has checked the file system and found no problems.

 300126204 KB total disk space.
  95628304 KB in 156675 files.
    135860 KB in 32527 indexes.
        52 KB in bad sectors.
    415184 KB in use by the system.
     65536 KB occupied by the log file.
 203946804 KB available on disk.

      4096 bytes in each allocation unit.
  75031551 total allocation units on disk.
  50986701 allocation units available on disk.

Internal Info:
00 96 04 00 1d e3 02 00 49 1f 05 00 00 00 00 00  ........I.......
0d 63 00 00 98 00 00 00 00 00 00 00 00 00 00 00  .c..............
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................

Windows has finished checking your disk.
Please wait while your computer restarts.

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

+ System 

  - Provider 

   [ Name]  Microsoft-Windows-Wininit 
   [ Guid]  {206f6dea-d3c5-4d10-bc72-989f03c8b84b} 
   [ EventSourceName]  Wininit 
 
  - EventID 1001 

   [ Qualifiers]  16384 
 
   Version 0 
 
   Level 4 
 
   Task 0 
 
   Opcode 0 
 
   Keywords 0x80000000000000 
 
  - TimeCreated 

   [ SystemTime]  2022-08-05T04:04:54.000000000Z 
 
   EventRecordID 171676 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  0 
   [ ThreadID]  0 
 
   Channel Application 
 
   Computer Irina-PC 
 
   Security 
 

- EventData 

   Checking file system on C: The type of the file system is NTFS. Volume label is Windows. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 300544 file records processed. File verification completed. 1389 large file records processed. 0 bad file records processed. 2 EA records processed. 152 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 365594 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 300544 file SDs/SIDs processed. Cleaning up 270 unused index entries from index $SII of file 0x9. Cleaning up 270 unused index entries from index $SDH of file 0x9. Cleaning up 270 unused security descriptors. Security descriptor verification completed. 32526 data files processed. CHKDSK is verifying Usn Journal... 37263008 USN bytes processed. Usn Journal verification completed. CHKDSK is verifying file data (stage 4 of 5)... 300528 files processed. File data verification completed. CHKDSK is verifying free space (stage 5 of 5)... 50986701 free clusters processed. Free space verification is complete. Windows has checked the file system and found no problems. 300126204 KB total disk space. 95628304 KB in 156675 files. 135860 KB in 32527 indexes. 52 KB in bad sectors. 415184 KB in use by the system. 65536 KB occupied by the log file. 203946804 KB available on disk. 4096 bytes in each allocation unit. 75031551 total allocation units on disk. 50986701 allocation units available on disk. Internal Info: 00 96 04 00 1d e3 02 00 49 1f 05 00 00 00 00 00 ........I....... 0d 63 00 00 98 00 00 00 00 00 00 00 00 00 00 00 .c.............. 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ Windows has finished checking your disk. Please wait while your computer restarts.  

Bernie, the log files for the backup tasks are the best place to see why Acronis has had any issues during the backup process.

For backups performed in Windows, then the MVP Assistant tool is the best way to review the logs.

For backups performed using bootable media, then the Logs have to be saved while still in the rescue environment as are lost when restarting the computer.  Click on Logs in the offline Acronis application, then right-click on the top log entry (showing the date / time of the action) and this will offer a drop-down menu with a Save option for the log.

Beyond the above logs, another option is to create an Acronis System Report zip file then extract the disk report text file from it (disks.txt) and look for any entries with an 'E' (error indicator) in the B or C columns at the right side in the information shown at the top of the file.

Hi Steve, thanks for your help here. I have one other query...I can definitely do a backup using Rescue media Builder via USB with the 32 bit version, but if I try to do the same thing except using the 64 bit version (also using USB  boot), I get backup errors. Can you explain why this is so...when I do a validate for the successful backup, it IS valid.

Thanks for any help aain.

Bernie

Bernie, if all looks to be OK when booting 32-bit rescue media but not with 64-bit media, then it suggests (to me) that you may have a memory module issue at play here as the 64-bit OS environment can use much more memory than the older 32-bit OS can.