Windows NO LONGER backing up

Let's focus on the VSS problem. Really no other entries related to VSS in eventlog?

egonvdv said:

Kaktussoft said:

egonvdv said:

Sh*t....; problems remain same!

direct backup: can read shadow copy,
wireless back: path not correct

this is getting quite desperate...?

Can you sees relevant information in eventlog at time of failure?

overnight i did a full backup, including system image: (IE DIRECT BACKUP VIA USB)

these are the massages in order of appearance:

1)
The backup was not successful. The error is: Windows Backup failed while trying to read from the shadow copy on one of the volumes being backed up. Please check in the event logs for any relevant errors. (0x81000037).

2)
Fault bucket 1084420110, type 5
Event Name: WindowsBackupFailure
Response: Not available
Cab Id: 0
Problem signature:
P1: Backup
P2: 6.1.7601
P3: 0x81000037
P4: 11
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\WINDOWS\Logs\WindowsBackup\WindowsBackup.1.etl
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_Backup_37c94a3f7f9dc50e1a69c36b71e2cc befec74cf_22ec2ca2
Analysis symbol:
Rechecking for solution: 0
Report Id: 97049d07-db90-11e1-adaa-00217063082d
Report Status: 0

3)
The VSS service is shutting down due to idle timeout.

4)
The Block Level Backup Engine service has stopped.

5)
Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0
Problem signature:
P1: 7.6.7600.256
P2: 80072ee2
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7:
P8:
P9:
P10:
Attached files:
These files may be available here:

Analysis symbol:
Rechecking for solution: 0
Report Id: 01946a6f-db99-11e1-adaa-00217063082d
Report Status: 0

6)
Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0
Problem signature:
P1: 7.6.7600.256
P2: 80072ee2
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7:
P8:
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_d657698cc2203130accf771c18 dbe77b92e59fa7_cab_1daf4744
Analysis symbol:
Rechecking for solution: 0
Report Id: 01946a6f-db99-11e1-adaa-00217063082d
Report Status: 4

7)
Fault bucket , type 0
Event Name: WindowsUpdateFailure
Response: Not available
Cab Id: 0
Problem signature:
P1: 7.6.7600.256
P2: 80072ee2
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 101
P6: Unmanaged
P7:
P8:
P9:
P10:
Attached files:
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_7.6.7600.256_d657698cc2203130accf771c18 dbe77b92e59fa7_cab_1daf4744
Analysis symbol:
Rechecking for solution: 0
Report Id: 01946a6f-db99-11e1-adaa-00217063082d
Report Status: 0

8)

I didn't read your post right, sorry. So directly attached to USB also fails?! use another disk and usb port

egonvdv said:

""I didn't read your post right, sorry. So directly attached to USB also fails?! use another disk and usb port ""


to clarify: i test:

- with 2 different discs
- both discs i try in 2 different formats NTFS & FAT32
- i use random USB ports
- i try to backup only system image
- i try to backup only files
- i try to backup both

its seems to just randomly fail or succeed...

and i don't get why i have 2 different problems which seem unrelated, yet started at the same time
(meaning: 1) can't read shadow copy & 2) path not correct

You tried all kind of disks and usb ports... good work. A shadow copy is just a snapshot of the situation as it is now! So you can backup as it is now. No problem with open files. The shadow copy is just a fake C drive at some moment in time. "path not correct" means path to shadow copy not accessible (i assume). It doens't say something like "network path" and you can always access it on air as you told before. And if attach it directly it isn't even a network path.

I think:
-usb's are fine
-disk where you put backup on is fine
-shadowsets have been deleted and recreated so must be fine

Unless... C drive has bad sectors.

in elevated command prompt

Code:

chkdsk/f c:

It takes about 10 minuten to complete. Post errors
What disk is C? Any other partitions on that disk (give drive letter).

please post screenshot of disk management

egonvdv said:

). It doens't say something like "network path" and you can always access it on air as you told before. And if attach it directly it isn't even a network path.

sorry i do mean NETWORK path

HD directly connected = can't access some files on shadow copy

HD via wireless = network path not correct

Let's concentrate on the VSS error first. Maybe "NETWORK path" is a wrong error message form backup(?)

Post screenshot of disk management please