N°04758541BACKUP FAILING SHOW BAD BLOCKS

[astoinemicro]

CASE : °04758541

HI ,Errors when i try to backup server , it says :

- SQL VSS Writer is missing: databases will be backed up in crash---consistent state and transaction log processing will be skipped
- One or more bad blocks were detected and skipped and skipped in the source disk

I changed the destination from NAS to local and same error pop up

[PetrM]

Hi Morad,

I would check the state of all VSS writers by "vssadmin list writers" command, you may also take a look at this KB which provides the instruction for shadow copy creation using diskshadow tool. However, I strongly recommend to perform all troubleshooting steps under the guidance of our support team.

I'm not sure that the second error about bad blocks is related to the backup repository but perhaps there are some issues on source. Anyway, our support engineers will be able to determine the root cause.

Thanks!

[astoinemicro]

Hi @petrm
Thanks for reply .
I checked the VSS writers they're showing 'stable' state , i follwed the link you provided me all's good , i did a deep scan on the repository ( 0 bad sectors ) but still i can't do a backup ,same errors .
I opened a case from 16/04 and till now i didnt get veeam support :/ .

[Mildur]

This KB article is specific for SQL VSS Issues with Veeam.
It helped me every time:

https://www.veeam.com/kb2095

Mostly it was a false logonaccount on the SQL VSS Writer Service.

the account under which SQL VSS Writer service is running doesn't have sysadmin role on a SQL server

[PetrM]

Hello,

@astoinemicro As far as I see the case is under investigation but is in pending status since our engineers wait for your reply and debug logs. The best action plan is to keep working with our support team because our possibility to troubleshoot technical issues over forum posts is quite limited.

Thanks!

[Alungr]

Having a similar problem. Did you get any joy from Tech Support on resolving the issue?

[Dima P.]

Hello Alun,

The original case was closed without any updates provided. Have you tried the suggested KB article? Any chance you have an open case and can share the case ID with us? Thank you!

[Alungr]

Hi,
Did try the original KB article but not particularly relevant and didn’t help.
Did try to open a case but as a user of the Freeware App (Veeam for MS Windows) got a reply that there was only limited technical support available…try the forum!
Was hoping that the recent Veeam programme upgrade might resolve the issue, but again no luck in resolving my “bad blocks” warning/error.
If you have any recommendations on Information or KB article to resolve this issue, please let me know.
Thanks for the follow up.

[Gostev]

Updating a software cannot fix a hardware issue. To resolve it, you should just replace your failing hard drive with a new one.

[Alungr]

But when I do a chkdsk (with full range of options (/f /r /x)) no bad sectors are identified!
Hence my concern that it’s a software fault.

[Gostev]

If you Google this, you will see it's not an uncommon problem when Windows is unable to read certain blocks but chkdsk is unable to identify any issues on disk.

Also, keep in mind that no backup software interacts with the disk hardware directly. We fully depend on the operating system being able to read the entire disk content, as we retrieve all data from VSS snapshots through WinAPI. And this error above is logged by Veeam in response to the WinAPI function failing with the specific error indicating unreadable block. Thus, it cannot possibly be a backup software fault when the OS itself is unable to read some data from disk.

[Alungr]

Thanks so much for clarifying the core nature of the error and the excellent advice. Swapped out the hard disk for a spare one and it resolved the problems. Now error free.