Testing was done in Win11 Pro 26H1 Canary (Build 28000.1).
It seems to make a difference if the backup was taken from within Windows or from rescue media.
a) HBS disk backup without filters, backup taken from within Windows:
b) HBS disk backup without filters, backup taken from rescue media:
So this is probably a restriction with VSS and snapshots can't be backed up by VSS itself?
HBS in rescue media probably uses direct I/O instead of VSS. Just a wild guess though.
Sorry for the confusion, the mechanics for this were probably like this for quite some time, but it's sometimes difficult to take every test scenario into account.
It seems to make a difference if the backup was taken from within Windows or from rescue media.
a) HBS disk backup without filters, backup taken from within Windows:
- VSS snapshot files are in the backup.
- If you restore from backup, files are restored as well but snapshots are not available.
- If you take a look inside the backed up VSS files, they're completely empty (600MB filled with \x00 chars):
![[Image: Qi9mUxC.png]](https://i.imgur.com/Qi9mUxC.png)
b) HBS disk backup without filters, backup taken from rescue media:
- VSS snapshot files are in the backup.
- If you restore from backup, files are restored and snapshots are available in Windows.
So this is probably a restriction with VSS and snapshots can't be backed up by VSS itself?
HBS in rescue media probably uses direct I/O instead of VSS. Just a wild guess though.
Sorry for the confusion, the mechanics for this were probably like this for quite some time, but it's sometimes difficult to take every test scenario into account.