Unable to take backups with Veeam

A

aaiceman

Member
Joined
Oct 8, 2018
Posts
21
Hi all, this started with needing to fix taking backups with Veeam Agent for Windows. We are doing in place upgrades for Windows 7 -> Windows 10 and wanted a good backup of this system prior to doing so. The backups were failing, so we ran Check Disk and it repaired things. It took running it 2 or 3 times and it then started coming back clean. I tried the standard sfc /scannow, it came back with corrupted files unable to fix. I ran SFCFix and it came back with 6 files. I was able to repair 4 of the 6, but the below 2 are not showing as repaired even though I have overwritten them with files from a good (I think) window 7 machine. Please advise if there is any additional information I can provide. Thank you for any help you can provide.


SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-06-18 00:11:13.082
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.




AutoAnalysis::
WARNING: Manifest damage on component "amd64_microsoft-windows-ie-datacontrol_31bf3856ad364e35_11.2.9600.19230_none_f675980cb525e22c". See CBS logfile for more details.


CORRUPT: C:\Windows\winsxs\amd64_wcf-system.servicemodel_b03f5f7f11d50a3a_6.1.7601.24496_none_8ae2108ead3c0440\System.ServiceModel.dll
CORRUPT: C:\Windows\winsxs\x86_wcf-system.servicemodel_b03f5f7f11d50a3a_6.1.7601.24496_none_d28f4765c1b82d46\System.ServiceModel.dll


SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 10
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 2
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2020-06-18 00:12:42.081
----------------------EOF-----------------------
 

Attachments

Thank you. I can confirm that Check Disk and Lenovo diagnostics come back clean now with no issues reported.
 
In that case, let's do some fixing:

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.

Afterwards, run System Update Readiness tool again and attach CheckSUR.log.
 

Attachments

Thank you, I will have access to the PC again tonight (in about 8-12hrs) and follow these steps.
 
Thank you! I've attached the requested information. Apologies for the delays.

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-06-22 19:32:44.036
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\redrock\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\Temp

Successfully created directory tree \\?\C:\Windows\Temp\CheckSur\Servicing\Packages.
Successfully created directory tree \\?\C:\Windows\Temp\CheckSur\WinSxS\Manifests.

Successfully copied file C:\Users\redrock\AppData\Local\niemiro\Archive\Manifests\amd64_microsoft-windows-ie-datacontrol_31bf3856ad364e35_11.2.9600.19230_none_f675980cb525e22c.manifest to C:\Windows\Temp\CheckSur\WinSxS\Manifests\amd64_microsoft-windows-ie-datacontrol_31bf3856ad364e35_11.2.9600.19230_none_f675980cb525e22c.manifest.
Successfully copied file C:\Users\redrock\AppData\Local\niemiro\Archive\Manifests\amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.2.9600.18349_none_f5a6e32e372dd76e.manifest to C:\Windows\Temp\CheckSur\WinSxS\Manifests\amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.2.9600.18349_none_f5a6e32e372dd76e.manifest.

Successfully restored ownership for C:\Windows\Temp
Successfully restored permissions on C:\Windows\Temp
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2020-06-22 19:32:45.120
Script hash: SupcVA9J+eBGvHOvxv2FIS/boCQM+1QaB1Pe0Lhx+Js=
----------------------EOF-----------------------
Code: 
C:\Windows\system32>chkdsk c:
The type of the file system is NTFS.
Volume label is Windows7_OS.

WARNING!  F parameter not specified.
Running CHKDSK in read-only mode.

CHKDSK is verifying files (stage 1 of 3)...
  488192 file records processed.
File verification completed.
  2176 large file records processed.
  0 bad file records processed.
  2 EA records processed.
  177 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
  593726 index entries processed.
Index verification completed.
  0 unindexed files scanned.
  0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
  488192 file SDs/SIDs processed.
Security descriptor verification completed.
  52768 data files processed.
CHKDSK is verifying Usn Journal...
  36979744 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.

 235593727 KB total disk space.
 158480088 KB in 299989 files.
    197576 KB in 52769 indexes.
      1308 KB in bad sectors.
    599479 KB in use by the system.
     65536 KB occupied by the log file.
  76315276 KB available on disk.

      4096 bytes in each allocation unit.
  58898431 total allocation units on disk.
  19078819 allocation units available on disk.

C:\Windows\system32>
 

Attachments

Awesome!

SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 
Hi!

SFCFix Script

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.


  1. Download SFCFix.exe (by niemiro) and save this to your Desktop.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please - put [CODE][/CODE] tags around the log to break up the text.



SFC Scan


  1. Click on the Start button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log "%userprofile%\Desktop\cbs.txt"
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.
 

Attachments

Things show as repaired! I'm going to try to run the backup overnight and see what happens. Thanks!

Code: 
SFCFix version 3.0.2.1 by niemiro.
Start time: 2020-06-24 20:42:30.169
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\redrock\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-s..chrecognizereng.ale_31bf3856ad364e35_6.1.7600.16385_en-gb_e3a447542ad2c5da\lsr2057.lxa

Successfully copied file C:\Users\redrock\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-s..chrecognizereng.ale_31bf3856ad364e35_6.1.7600.16385_en-gb_e3a447542ad2c5da\lsr2057.lxa to C:\Windows\winsxs\amd64_microsoft-windows-s..chrecognizereng.ale_31bf3856ad364e35_6.1.7600.16385_en-gb_e3a447542ad2c5da\lsr2057.lxa.

Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-s..chrecognizereng.ale_31bf3856ad364e35_6.1.7600.16385_en-gb_e3a447542ad2c5da\lsr2057.lxa
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-s..chrecognizereng.ale_31bf3856ad364e35_6.1.7600.16385_en-gb_e3a447542ad2c5da\lsr2057.lxa
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2020-06-24 20:42:30.775
Script hash: SV3TbZoIzKcJvmlKTR7/R6Be4e/a0IT3u5wj02E66Rw=
----------------------EOF-----------------------
 

Attachments

It did fail and I've attached the logs. I'm reviewing as well.

There are two jobs - an active full started at 20:59:39 and failed at 01:40:33 and an incremental scheduled/queued job started at 03:30:02, Failure confirmed at 08:15:22.

I've replaced the IP of the SMB share with IP.IP.IP.IP and the name of the PC with PCNAME.

Edit: I have multiple other PC's backing up to this share without any issues, so I don't believe it's the destination as the issue.
 

Attachments

Let's do a precautionary check:

GSmartControl
Follow the instructions below to check your SMART status with GSmartControl:


  • Download the portable version of GSmartControl and save it on your Desktop;
  • Extract the zip file to your Desktop. Open the folder gsmartcontrol-1.1.3-win64 which should be located on your Desktop and double-click gsmartcontrol.exe to launch the program.
  • Identify your drive in the list (if recognized by the tool), and hover your mouse over it.
  • You should see something called: SMART status. It will either read: Enabled, in which case you should do the following:
  • Double-click on it to bring up its window (usually you'll find your drive by its size or its brand name);
  • Go to the Self-Tests tab, then select Extended Self-test in the Test type drop-down list and click on Execute (this test can take a few hours to complete);
  • Once the test is over, the results will be displayed at the bottom of the window. Please copy and paste these results in your next reply or take a screenshot;
  • Also, go in the Attributes tab and if you have any entries highlighted in red or pink, take a screenshot of the GSmartControl window and attach it in your next reply;
  • Please note: If the SMART Status reads: Unsupported, stop and let me know.
    info_failing.png
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top