Veeam! Give me back my diskspace! (Win11 bugs?)

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


What could possibly go wrong?
Nov 7, 2020
I have been using Veeam personal backup (Veeam Backup & Replication Community Edition) on Win10 for quite a while to back up to my server at home.

Upgrading to Win11 has seen some unknown BSODs that I traced back to my backup schedule - so disabled it. Stability was better with the job not running but still I've been getting BSODs.... :eek:

Cue my headscratching this week when my Surface SSD was looking almost full. My first thought was SpinRite 6.1 test versions as my Surface will not book old-style.... then I got a portable TreeSizeFree running on my machine and found 50Gb of error files in the SQL logging for Veeam.

It's uninstalled and I went back to Macrum Free to perform the same but, in case anyone else is looking, Veeam seems to crash, cause BSOD and it's triggered on the SQL side of things (I thought it was driver issues and throughput on the SSD causing this).

FWIW if anyone is looking at good ways to backup, the approach I have is image to SMB share which then uploads the backup images to OneDrive; Veeam was working well as does Macrum Free
I do not have any experience with Veeam and the issues with Win 11 are surprising. During the beta testing of Win 11 my VPN, previously working on Win 10, would not connect on Win 11. An uninstall and reinstall resolved the issue. You may want to try doing that with Veeam.

There are a few features with the Macrium Reflect paid version that might be of interest to you. The first is Incremental backups. The process is fast and the resulting file size is smaller than a full backup. The second is the Rapid Delta Restore process which reduces the restore time significantly. The built-in scheduler and backup facility for managing the number of backup saved works well.
Thanks :) I actually have a grandfather-father-son template in Free that I am using on a timed basis.

I have no plans to restore! Speed is also not of the essence as I have enough computing power to survive :D

Regarding Veeam, I think it updated since my Win11 update, I would consider that a repair.....the SQL crashes are significant and I thank the absence of disk space for helping me get to what I hope is the root cause of the issue..... (y)
I have no plans to restore!
No one ever does. :)

I have a simple backup plan:
1) Use Windows File History to backup to external 4TB drive (backup every hour, save versions until space is needed).
2) Continual backup to OneDrive using Files on Demand.

I have had to do a full restore several times and because Files on Demand doesn't restore files until they are needed, restoring the placeholder files is very fast. When I need to roll back a file or directory to a point in time, I use File History.