By treptowers - 3 January 2022 8:29 PM
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.
|
By 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.
|
By treptowers - 4 January 2022 4:46 PM
+xYou 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 ?
|
By 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.
|
By treptowers - 4 January 2022 6:12 PM
+xJust 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.
|
By JK - 4 January 2022 7:39 PM
You may want to review the following KnowledgeBase Article:
Understanding Image Verification Failures
|
By treptowers - 5 January 2022 5:18 PM
+x
Sorry, but i can not upload the HTML File. I have saved it on my Laptop
|
By JK - 5 January 2022 5:33 PM
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.
|
By treptowers - 5 January 2022 9:32 PM
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
|
By JK - 5 January 2022 9:53 PM
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.
|
By treptowers - 5 January 2022 10:58 PM
+xIs 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.
Yes. I chance nothing. T1 connected by USB Hub. Security Software is Kaspersky. It worked fine. Since to weeks its the problem i posted.
|
By JK - 5 January 2022 11:29 PM
Even if your configuration has not changed, hardware failures can occur over time. If the culprit is third-party software, a bad software update can cause problems suddenly.
Does the error now happen consistently every time you attempt to backup, or is it intermittent? If the error is reasonably consistent, then you can do some troubleshooting to find the source of the error.
Do you have access to another computer? If so, you could try attaching the Samsung_T1 to the other computer, and performing a manual verification of the 1F2855D69B6CAD6F-00-00.mrimg file; if the other computer does not have Reflect, then you can install the free version of Reflect, or try booting from USB Rescue Media. Having another computer will also allow you to do some additional testing, as recommended in the KnowledgeBase article on verification failures.
|
By JK - 6 January 2022 1:06 AM
One more thing... If you're creating new images for testing/troubleshooting purposes, I recommend creating a new destination folder, or (temporarily) modifying your retention rules. According to your log, your current destination folder (F:\MacriumReflect\) already contains 3 full backups, and your retention policy specifies deletion rules that will delete the oldest of the 3 backup sets each time that you create a new full. Since the Full Backups you that you have been creating recently are not verified (and thus presumably corrupt), you will be deleting any older non-corrupted backups if you keep backing up to the same destination folder. It may already be too late (i.e., because this problem has been occurring for 2 weeks, you may have already deleted all of your useable backup images from that folder). If you do not have any good backup images (i.e., images that can be successfully verified) stored in other locations, you should make it a high priority to create at least one good backup before continuing to troubleshoot the issue. For best chance of success, use a different destination drive (not the Samsung_T1), connected directly to the computer (not via a USB hub), and create the image from the Reflect Rescue Environment.
|
By treptowers - 10 January 2022 8:26 PM
Well, i check the backups and Macrium says everything is ok.
Then i started the planned xml file manual. Everything works fine. The Backup is complete and the verification is ok.
Today the problem again with the planned backup. Verification failed.
I have also checked the T1 SSD with chkdsk. No error.
I use Kaspersky Internet Security on all mine laptops. And i use there planned schedule with Macrium. No errors.
Do you have other solutions ? Thx.
|
By jphughan - 10 January 2022 8:32 PM
If you have a specific backup file that passed verification successfully when it was first created, then try manually verifying it later on, which you can do from the Existing Backups tab in Reflect. See if the exact same file delivers different verification results on different test runs. If you see inconsistent verification results, then you'll need to start isolating variables. For example, try another USB cable. Try connecting that disk to another PC that has Reflect (even Reflect Free is fine) and verify that same backup file on another PC to see if you get consistent results. If you find that the same file reliably verifies the same way on a different PC but goes back and forth on your PC even after changing the USB cable, then the most likely culprit is probably a RAM module in your system. One user here found that their CPU was the problem. He had a system and two CPUs, and he consistently found that verification failed with one CPU and passed with another CPU, even though nothing else about the test was changing.
|
By JK - 11 January 2022 2:02 PM
Do you have other solutions ?
The solution is to go through a systematic process of elimination to narrow down the source of the problem. In an earlier response, I pointed you to a KnowledgeBase article about verification errors, which contains recommended troubleshooting steps that eliminate or confirm possible sources of the error. JP's post above also proposes a process that you could follow to identify the source of the issue. It doesn't seem that you have attempted to follow the recommended troubleshooting steps yet, so that might be the best thing to do next.
|
|