The problem with ZFS snapshots

[NAS]

Better make sure you only restore if you know your data exists in that snapshot otherwise proof it's gone.

Unlike traditional approaches that have incremental vs. differential backups you with ZFS can't restore snapshots anywhere on the timeline arbitrarily.

Consider the following scenario.

1. You're on vacation

2. Your home network experiences ransom malware. Hypothetically you're not quite sure what day it happened.

3. You restore in the beginning the week and it works as expected but wait all your photos photos from vacation are not there! The photos are backed up near at the end of the week just before ransom malware got to your network,

4. Oh no all your snapshots are now invalid (because of first restore) and you can't restore the data from later in the week.

Your vacations pictures are now lost forever! Does this seem confusing?

How is hexos going to help protect users from this kind of scenario?

Replication doesn't fully solve this issue either if the user doesn't know exactly what snapshot their data exists.

[Magnus]

Hi there! While I don't have an answer for you now, this is good point we need to consider when developing snapshots, thank you!

[joshdev]

Hey,

the issue you are describing is not really present. Take a look at this explanation, all the information you are asking for is already present and accessible in the filesystem. Making it accessible to the user in a nice way is the only challenge here. Could be implemented in a similar way to Apple‘s time machine historic view. If you have more questions feel free to ask!

Hope this helps a little 🙂