BR16 backup fails at 98% VSS:Cannot read volume data
Six months ago I built a new system using ADATA PCIe 128GB NVMe Gen3x4 M.2 2280 SSD. Windows 10 Pro. No problems at all, use the PC to record cable tv (separate drive).
Use BR16 to backup C drive weekly. Been working fine for 20+ weeks. It is now failing. Tried running new manual job and it failed also. Creates backup folder, writes backup files, gets to 98% complete then quits and gives these errors:
"Source: This job references the volume that doesn't exist or is not accessible!"
"VSS:Cannot read volume data"
"Error code: 0x12016"
Tried all of these, rebooting between each step, repeating some of them several times:
-uninstall/reinstall BR16
-chkdsk c /f /r - no errors
-C drive properties > Tools > Error check - found/repaired errors
-repeat C drive properties > Tools > Error check - no errors
-disk manufacturer software tool - 100% good
-crystal disk info - 100% good
-hard disk sentinel pro disk info - 100% good
-hard disk sentinel pro disk surface scan - found/repaired errors
-DISM.exe /Online /Cleanup-image /Restorehealth + sfc /scannow - found/repaired errors
Re: BR16 backup fails at 98% VSS:Cannot read volume data
how much space is used on the c: drive?
how much space is available on the external backup drive?
did you try setting up a brand new backup job, just to test?
Re: BR16 backup fails at 98% VSS:Cannot read volume data
Backup finally ran after several chkdsk & "Disk Check" from properties, and reboots.
But 3rd party software still says the disk has bad sectors.
Purchased new identical drive, installed OS, back up works fine.
Ran secure wipe on "defective" disk, now reports no bad sectors. Just keep it for emergency, I guess.
Re: BR16 backup fails at 98% VSS:Cannot read volume data
adopt a mode of "distrust" of all your drives, and you will be protected !
I have multiple USB external drives for backup, I rotate them when creating bakups from the main drive, and i do not leave them plugged in when not using.
I also make sure that I do the "check integrity" option, after doing IMAGE BACKUP with paragon (this is a separate step, that reads the backup, to make shre there are not errors in its structure)
this way, if a drive does blow up, you have something to go back to.