Locked volume snapshot errors

[babblo]

Hi,

I have a certain volume with sensitive information witch most of the time is locked and unlocked as needed, also has periodic snapshot enabled. The problem i'm having with this setup is about FreeNAS sending me a lot of emails saying he can't make the snapshot because the volume does not exist.

Code:

Hello,
   Snapshot sdata@auto-20171201.1803-3m failed with the following error: cannot open 'sdata': dataset does not exist
usage:
		snapshot|snap [-r] [-o property=value] ... <filesystem|volume>@<snap> ...

For the property list, run: zfs set|get

For the delegated permission list, run: zfs allow|unallow

Is there a way of suppress these notifications or prevent the snapshot mechanism to start if the volume is locked?

Thanks in advance.

 

[Ericloewe]

No, but with native encryption, you'll be able to snapshot encrypted data while it is locked.

 

[babblo]

Hi, trank for your reply. Can you elaborate a little more about "native encryption" and the ability to snapshot data when is locked?

Thanks in advance.

 

[toadman]

No, but with native encryption, you'll be able to snapshot encrypted data while it is locked.

Do we have an updated timetable on this? From some previous threads I remember a while back, I'm gonna guess late 2018 maybe?

 

[Ericloewe]

Do we have an updated timetable on this?

No, I'm not sure what the status of the FreeBSD port of the encryption work is, but I'd imagine first half of 2018.

Can you elaborate a little more about "native encryption" and the ability to snapshot data when is locked?

https://www.youtube.com/watch?v=frnLiXclAMo&feature=youtu.be

 

[babblo]

https://www.youtube.com/watch?v=frnLiXclAMo&feature=youtu.be

Thanks for the link, very interesting news, hope the come to FreeBSD/FreeNAS.

In the meantime, I will try to add an option in the lock/unlock dialogs to disable/enable the related periodic snapshots tasks.