rt/snapraid
1
0
Fork 0
mirror of https://github.com/amadvance/snapraid.git synced 2026-10-26 19:01:57 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add Windows VirtualShadowCopy support for snapshots

Browse source
This commit is contained in:
Andrea Mazzoleni 2026-05-07 17:23:48 +02:00
parent 33af95b359
commit deb800cb57
8 changed files with 468 additions and 54 deletions
Download patch file Download diff file Expand all files Collapse all files

8
doc/snapraid.1
View file

@ -1435,8 +1435,9 @@ start of a \'sync\'. This ensures a consistent, point\-in\-time view of your
files, preventing errors caused by concurrent file modifications.
.PP
This option applies exclusively to data disks formatted with the
Btrfs, Bcachefs or ZFS filesystems. Parity disks, or data disks using
other filesystems, will always use the live version of the filesystem.
Btrfs, Bcachefs or ZFS filesystems in Linux and NTFS in Windows.
Parity disks, or data disks using other filesystems, will always use
the live version of the filesystem.
.PP
This significantly improves recovery: if a file is deleted from the live
filesystem, it remains preserved in the snapshot. This prevents the parity
@ -1831,7 +1832,8 @@ Snapshots are created only for data disks and only if the underlying
filesystem supports this functionality. Parity disks always use
the live filesystem.
.PP
At present, this is supported exclusively on Btrfs, Bcachefs, and ZFS.
At present, this is supported on Btrfs, Bcachefs, and ZFS in Linux
and on NTFS in Windows.
.PP
You can mix data disks with different filesystems. Only those that
support snapshots will utilize them, while other disks will continue

8
doc/snapraid.d
View file

@ -1155,8 +1155,9 @@ Configuration
files, preventing errors caused by concurrent file modifications.
This option applies exclusively to data disks formatted with the
Btrfs, Bcachefs or ZFS filesystems. Parity disks, or data disks using
other filesystems, will always use the live version of the filesystem.
Btrfs, Bcachefs or ZFS filesystems in Linux and NTFS in Windows.
Parity disks, or data disks using other filesystems, will always use
the live version of the filesystem.
This significantly improves recovery: if a file is deleted from the live
filesystem, it remains preserved in the snapshot. This prevents the parity
@ -1443,7 +1444,8 @@ Snapshots
filesystem supports this functionality. Parity disks always use
the live filesystem.
At present, this is supported exclusively on Btrfs, Bcachefs, and ZFS.
At present, this is supported on Btrfs, Bcachefs, and ZFS in Linux
and on NTFS in Windows.
You can mix data disks with different filesystems. Only those that
support snapshots will utilize them, while other disks will continue

8
doc/snapraid.txt
View file

@ -1233,8 +1233,9 @@ start of a 'sync'. This ensures a consistent, point-in-time view of your
files, preventing errors caused by concurrent file modifications.
This option applies exclusively to data disks formatted with the
Btrfs, Bcachefs or ZFS filesystems. Parity disks, or data disks using
other filesystems, will always use the live version of the filesystem.
Btrfs, Bcachefs or ZFS filesystems in Linux and NTFS in Windows.
Parity disks, or data disks using other filesystems, will always use
the live version of the filesystem.
This significantly improves recovery: if a file is deleted from the live
filesystem, it remains preserved in the snapshot. This prevents the parity
@ -1548,7 +1549,8 @@ Snapshots are created only for data disks and only if the underlying
filesystem supports this functionality. Parity disks always use
the live filesystem.
At present, this is supported exclusively on Btrfs, Bcachefs, and ZFS.
At present, this is supported on Btrfs, Bcachefs, and ZFS in Linux
and on NTFS in Windows.
You can mix data disks with different filesystems. Only those that
support snapshots will utilize them, while other disks will continue