Hello,
every Monday 08:30pm i have a planned schedule. Full backup.
This works fine.
Recently it reports: Verifying failed.
Whats the problem?
If i start the backup manuall there is no problem.

You will have to provide more information if you want help diagnosing your problem.  Perhaps you can start by posting the log from one of the scheduled backups that failed to verify.   Before publicly posting a copy of the log, you will need to remove the license key that is displayed at the bottom of the log, and make any other redactions as necessary to remove information that you may wish to keep private.

                                

+x

 

JK - 3 January 2022 9:14 PM

You will have to provide more information if you want help diagnosing your problem.  Perhaps you can start by posting the log from one of the scheduled backups that failed to verify.   Before publicly posting a copy of the log, you will need to remove the license key that is displayed at the bottom of the log, and make any other redactions as necessary to remove information that you may wish to keep private.

Hello,
where do i find the log ?

Just launch the Reflect app and go to the Log view (the third tab, next to Create Backups and Existing Backups).  Find the log of one of the scheduled backup jobs that failed to verify, then right-click it in the list, and select Save Log.  This will export the log as an HTML file, and it will automatically strip your license code from the file.

                                

+x

 

JK - 4 January 2022 5:55 PM

Just launch the Reflect app and go to the Log view (the third tab, next to Create Backups and Existing Backups).  Find the log of one of the scheduled backup jobs that failed to verify, then right-click it in the list, and select Save Log.  This will export the log as an HTML file, and it will automatically strip your license code from the file.

Hm i see.
Now the error also appears if i start it manual 
I post the log file tomorrow.

You may want to review the following KnowledgeBase Article:
Understanding Image Verification Failures

                                

+x

 

JK - 4 January 2022 7:39 PM

You may want to review the following KnowledgeBase Article:
Understanding Image Verification Failures

Sorry, but i can not upload the HTML File. I have saved it on my Laptop

Yes, I forgot the forum is finicky with what kind of attachments it permits.  You can open the HTML in a browser and just copy and paste the displayed text directly into a post here.  Alternatively, you can change the file extension to .txt and attach.

                                

  Abbild-ID - 1F2855D69B6CAD6F
Imaging Summary
Backup Definition File:    C:\Users\User\Documents\Reflect\My Backup.xml
Auto Verify:    Y
Verify File System:    Y
Maximum File Size:    Automatic
Compression:    Medium
Passwort:    N
Intelligent Copy:    Y
Power Saving:    N
Email On Success:    Y
Recipients:    xxx
Email On Warning:    Y
Recipients:    xxx
Email On Failure:    Y
Recipients:    xxx
Total Selected:    94,50 GB
Current Time:    03.01.2022 20:30:33
Aufbewahrungsregeln
Rules will be applied to all matching backup sets in the destination folder
Full:    Retain 3 full images
Linked incremental and differential images will also be deleted
Backup Sets:    3 sets found
Delete File:    F:\MacriumReflect\A82CC5BAF243062A-00-00.mrimg
Ziel:
Backup Type:    Vollständig
Dateiname:    F:\MacriumReflect\1F2855D69B6CAD6F-00-00.mrimg
Operation 1 of 4
Hard Disk:    1
Laufwerkbuchstabe:    N/A
File System:    Unformatted
Label:
Größe:    128,0 MB
Free:    0 B
Used:    128,0 MB
Operation 2 of 4
Hard Disk:    1
Laufwerkbuchstabe:    N/A
File System:    FAT32 (LBA)
Label:
Größe:    99,2 MB
Free:    72,7 MB
Used:    26,5 MB
Operation 3 of 4
Hard Disk:    1
Laufwerkbuchstabe:    C
File System:    NTFS
CBT:    Y
Label:    Win10-Prof
Größe:    221,22 GB
Free:    156,52 GB
Used:    64,71 GB
Operation 4 of 4
Hard Disk:    1
Laufwerkbuchstabe:    D
File System:    NTFS
CBT:    Y
Label:    Daten
Größe:    732,42 GB
Free:    702,78 GB
Used:    29,64 GB
Starting Image - Montag, 3. Januar 2022 20:30:35
Initialisieren
Write Method:    Using Direct Disk I/O
Destination Drive:    Samsung_T1 (F - Free Space 117,62 GB
Image Guardian:    Protected
Free space threshold:    Delete oldest backup sets when free space is less than 10,00 GB
Creating Volume Snapshot - Please Wait
Volume Snapshots Created
Analyzing file system on volume
Analyzing file system on volume C:
Analyzing file system on volume D:
Saving Partition - <NO NAME>
Reading File System Bitmap
Partition speichern...
Saving Partition - <NO NAME>
Reading File System Bitmap
Partition speichern...
Saving Partition - Win10-Prof (C
Reading File System Bitmap
Partition speichern...
Saving Partition - Daten (D
Reading File System Bitmap
Partition speichern...
Saving Index
New File: 56,93 GB    1F2855D69B6CAD6F-00-00.mrimg
Überprüfen '1F2855D69B6CAD6F-00-00.mrimg'
Index load failed
Retrying...
Index load failed
Retrying...
Index load failed
Retrying...
Index load failed
Retrying...
Index load failed
Retrying...
Überprüfen '1F2855D69B6CAD6F-00-00.mrimg'
Index load error - Sicherung abgebrochen! - F:\MacriumReflect\1F2855D69B6CAD6F-00-00.mrimg Indexverifizierung fehlgeschlagen
Retrying...
Index load error - Sicherung abgebrochen! - F:\MacriumReflect\1F2855D69B6CAD6F-00-00.mrimg Indexverifizierung fehlgeschlagen
Retrying...
Index load error - Sicherung abgebrochen! - F:\MacriumReflect\1F2855D69B6CAD6F-00-00.mrimg Indexverifizierung fehlgeschlagen
Retrying...
Index load error - Sicherung abgebrochen! - F:\MacriumReflect\1F2855D69B6CAD6F-00-00.mrimg Indexverifizierung fehlgeschlagen
Retrying...
Index load error - Sicherung abgebrochen! - F:\MacriumReflect\1F2855D69B6CAD6F-00-00.mrimg Indexverifizierung fehlgeschlagen
Retrying...
Gathering Windows Events - Please Wait
Email Notifications
Recipients:    xxx
Email notification sent
I/O Performance:    Read 35,7 MB/s - Write 187,8 MB/s
    Sicherung abgebrochen! - F:\MacriumReflect\1F2855D69B6CAD6F-00-00.mrimg Indexverifizierung fehlgeschlagen

Macrium Reflect Home Edition v8.0.6392

Is your Samsung_T1 drive connected by USB?  Are you using a USB hub?  

You should review the KnowledgeBase article I had linked above (and follow the troubleshooting advice given there), but frequently, the cause of these types of problem is a bad USB connection.

Alternatively, if the "Index Load Error" message as shown in the log created by your German-language installation is in fact the same thing as the "Index Load Failed" message that is described in this article, then the problem may be caused by antivirus or similar security software.