From 004687bc982f0648ab09cbfe7777b4246c4e79b5 Mon Sep 17 00:00:00 2001 From: Andrea Mazzoleni Date: Sat, 5 Sep 2015 18:12:39 +0200 Subject: [PATCH] Auto update --- compare.html | 16 ++++++++++++++-- download.html | 3 --- faq.html | 48 ++++++++++++++++++++++++++++++++++++++++++++---- index.html | 2 ++ 4 files changed, 60 insertions(+), 9 deletions(-) diff --git a/compare.html b/compare.html index b8f408c7..59e3b973 100644 --- a/compare.html +++ b/compare.html @@ -92,7 +92,7 @@ and if all your disks are spinning when reading one file - + @@ -141,9 +141,17 @@ is it possible to recover the data in the not failed disks? - + + + + + + @@ -152,6 +160,10 @@ is it possible to recover the data in the not failed disks?
SnapRAIDunRAIDFlexRAIDdisParityZFSBtrfsStorage Spaces
SnapRAIDunRAIDFlexRAIDdisParityZFSBtrfsStorage Spaces
Redundancy model
Real-time computes parity at real-time like RAID, snapshot at request time, like Backup.
Power/Noise
How many disks are spinning when reading a single file?
OneOneOneOneAllAllAll
Filled disk
Can you start with already filled disks?
Filled disks
Can you start with already filled disks?
YesPartial[4]YesYesNoNoNo
Add disks
Can you add disks at later time?
YesYesYesYesNoYesYes
Operating system
Which OS is supported?
Linux
Windows
Mac OS X
OpenIndiana
Solaris
BSD
LinuxWindows
Linux
WindowsLinux [5]
Mac OS X
OpenIndiana
Solaris
BSD
LinuxWindows
License/Price
diff --git a/download.html b/download.html index 829bcb09..e8da37dc 100644 --- a/download.html +++ b/download.html @@ -50,19 +50,16 @@ If you like to use a GUI, you can try E
FileDescription
- snapraid-8.1.tar.gz Sources for Linux, Mac OS X, BSD, Solaris, OpenIndiana and any other Unix
- snapraid-8.1-windows-x64.zip Binaries for Windows x64 (the most recent Windows versions)
- snapraid-8.1-windows-x86.zip Binaries for Windows x86 diff --git a/faq.html b/faq.html index d4f77da1..771633a6 100644 --- a/faq.html +++ b/faq.html @@ -157,9 +157,28 @@ RAIDs are mirroring solutions that propagate changes immediately to the parity d In this sense, RAIDs are not backups, because they don't allow to restore an old state of the array.

-SnapRAID is instead more similar at a backup solution, and you can restore the state of the last backup made. +SnapRAID is instead more similar at a backup solution, and you can restore the state of the last backup. For example, with SnapRAID, if you delete by accident a file, you can easily restore it.

+

+Others advantages over traditional RAID5/6 solutions are: +

    +
  • All your data is hashed to ensure data integrity and to avoid silent corruption.
  • +
  • If the failed disks are too many to allow a recovery, you lose the data only on the failed disks. +All the data in the other disks is safe.
  • +
  • If you accidentally delete some files in a disk, you can recover them.
  • +
  • You can start with already filled disks.
  • +
  • The disks can have different sizes.
  • +
  • You can add disks at any time.
  • +
  • It doesn't lock-in your data. You can stop using SnapRAID at any time +without the need to reformat or move data.
  • +
  • To access a file, a single disk needs to spin, saving power and +producing less noise.
  • +
  • You can have up to six parity levels compared to the one of RAID5 and the two of RAID6.
  • +
+Obviously RAID has other advantages, like having a better speed due data striping. +What is best for you, depends on your specific use case. +

How is it different than ZFS/Btrfs snapshots and NTFS Shadow Copy?

@@ -167,6 +186,23 @@ SnapRAID creates a filesystem snapshot conceptually similar at other snapshot so The difference is that the purpose of SnapRAID is to be able to recover a disk to the saved state after a complete disk failure.

+

+SnapRAID is more similar at the RAID-Z/RAID functionality of ZFS/Btrfs. +Compared to them, SnapRAID has the following advantages: +

    +
  • If the failed disks are too many to allow a recovery, you lose the data only on the failed disks. +All the data in the other disks is safe.
  • +
  • You can start with already filled disks.
  • +
  • You can add disks at any time (not possible with ZFS, but possible with Btrfs).
  • +
  • It doesn't lock-in your data. You can stop using SnapRAID at any time +without the need to reformat or move data.
  • +
  • To access a file, a single disk needs to spin, saving power and +producing less noise.
  • +
  • You can have up to six parity levels compared to the three of ZFS RAID-Z and the two of Btrfs RAID-5/6.
  • +
+Obviously ZFS/Btrfs have other advantages, like being real-time solutions. +What is best for you, depends on your specific use case. +

How is it different than other backup solutions?

@@ -175,15 +211,19 @@ With SnapRAID you need only one additional parity disk to be able to recover the Adding more parity disks, you can recover from more disk failures.

-Note anyway, that only a full backup allows to recover from a complete failure of the disk array and +Note that only a full backup allows to recover from a complete failure of the disk array and it's surely the preferred solution if you can afford it. -SnapRAID is a good option only if a full backup is not a possible solution. +SnapRAID is a good option if a full backup is not a possible solution.

What are the advantages of SnapRAID compared to similar solutions like unRAID/FlexRAID/Windows Storage Spaces?

You can see the Compare page to see it compared to other similar solutions. -In short, SnapRAID is reliable, OpenSource, multi-platform and free. +

+

+A strong advantage of SnapRAID is the integrity and silent error management that is at the same level (if not better) +of the ZFS and Btrfs filesystems. Instead, unRAID and Storage Space have no integrity check at all! +FlexRAID is at least able to report silent errors, but not to fix them.

How much does it cost?

diff --git a/index.html b/index.html index 00270c55..c8c83ba1 100644 --- a/index.html +++ b/index.html @@ -67,6 +67,8 @@ recover them.
  • You can add disks at any time.
  • It doesn't lock-in your data. You can stop using SnapRAID at any time without the need to reformat or move data.
  • +
  • To access a file, a single disk needs to spin, saving power and +producing less noise.