Migrating from FreeNAS to Open Media Vault while also importing FreeNAS ZFS to ZFS on Linux - Roadmap Advice sought please

OK there are two possibilities from here. (The second is pretty much guaranteed to fix this.)

First:

Do you have OMV-Extras installed? If not, the easiest way to install it is on the CLI.

SSH in as root:

wget -O - https://github.com/OpenMediaVault-Plugin-Developers/packages/raw/master/install | bash

When this is complete, you'll see System, OMV-Extras in the GUI. Click on OMV-Extras, and the Settings Tab and enable the Testing and Extras Repos.
______________________________________________

In the GUI, look under System, Plugins. Scroll down and look for openmediavault-resetperms.
Install it.

This will add a third tab to Access Rights Mangement, Shared Folders named Reset Permissions.

Click on the Tab.

Shared Folder: Use the drop down to select backups.

Permissions : Set to Everyone Read/Write

Clear ACL: ON (green)

Then click Reset Permissions.

(I would set the shared folder back to None and save it. This sets the default condition of the tab.)

See if that fixes it.

Some closing notes:

1. Those command lines that I posted earlier set the pool and datasets to a very close approximation of posix permissions and ACL's, but those ZFS attributes are "inherited". (I think they should be defaults for ZOL, and they may now be the defaults, but I don't know for sure. I haven't checked the features of the latest ZOL versions.)

However, note that the attributes of the existing files and folders in the pool and child filesystems may not have these attributes. That means you may have mixed attributes in the files and folders in the pool and filesystems, going forward. (I don't know how to change them recursively.) This may have no effect on you at all. If that's the case, great.

If there's some weird permission issue in the future, with the old data, the only way to recursively change file and folder attributes is to copy the old data into a new filesystem (like Backups2), then copy it back into the original Backups filesystem. When the copy out is done, the new attributes will be inherited when the now "new" files are copies back. Keep that in mind if you have weird permissions issues with the old files and folders.

2. You might give thought to installing the Proxmox Kernel. The reason is, ZFS modules are preinstalled in the Proxmox kernel which might save you from some issues in the future when upgrading.

3. With or without the Proxmox Kernel, do not update the kernel or ZFS packages without first backing up your boot drive. (Trust me on that.)

4. Here's some more attributes to consider:
Sub in your pool name for ZFS1

zfs set compression=lz4 ZFS1

Saves space on uncompressed files. Near zero CPU impact.

zpool set autoreplace=on ZFS1

If you have a dead or dying drive in a zmirror, RAIDZ1, etc., and it's physically replaced, the above will auto integrate the new drive into the pool.

5. If you're interesting in automating local snapshots, take a look at this doc.

Zitat von adeelleo

Never used snapshots on FreeNAS either. I replicate the data on this NAS to another NAS periodically to have an offline backup of things.

An off line backup is good, but it gives you only one choice when restoring files. That is the exact state files were in, as of the last backup. If they're corrupted or contain a virus, and get backed up, it's over. They're permanently lost.

Snapshots give you versioned backup. If you read the beginning of the ZFS auto-snap document it gives a little abstract on what snapshots do. Basically, if you change a file, the original is still maintained, in it's original state, in the prior snapshot. That gives you "version" protection in that you can return to any previous state the file was in for a configurable time. After the time period lapses, older versions of a file or folder are "purged", on rotation - first in, first out.

Since I have some turnover in my Video folder, I only save 1 month of snapshots. When it comes to pictures and music files, which are relatively static, I maintain snapshots up to one year. Snapshots give you the option to return to a prior state, say, before a virus infection or before ransomware encrypted your files. Snapshots provide complete immunity from malware.

Zitat von adeelleo

issued the command "zfs set compression=lz4 ZFS1" on the pools that contained Data. Would there be any use issuing this command on the pool that contains only multimedia files, like movies and songs etc. Since i don't think they would be compressed.

There won't be an issue but, if they're already compressed (most media files are) a second compression of an already compressed file won't save much space. In any case, it won't hurt anything and might save a bit of space with new uncompressed files.

Zitat von adeelleo

I might even consider getting rid of ZFS all together. Since I don't use ZFS RAID anyway. I just use rsync to copy important files on another disk based on a daily schedule.

I use ZFS in a zmirror (the equivalent of RAID 1) for bitrot protection which I think is important. With a single disk, say on a backup device, I might consider EXT4 or XFS. (But again; snapshots for versioned files/backup, even if they're on the same disk, would make it worth running ZFS on a single volume. Complete malware immunity, especially if it's accidently/ backed up in an automated process is worth considering.)

I'm not sure how you're using rsync to backup, but there's a method of creating a backup server that doesn't require getting on the CLI. Remote Mount.

Zitat von adeelleo

Was looking at the below video to backup the OS USB Drive. Lets me know what you think about this process:

This subject is covered in the User Guide -> OS Backup, with enough detail so that beginners can stay on track and understand the reasons "why" they should backup. There's no easier way to maintain OS backup than booting from a USB thumbdrive. (And there's the added bonus of saving a SATA port for an additional hard drive if needed.) Cloning thumbdrives is dirt simple. It doesn't require knowledge of 3rd party app's or CLI operations.

Zitat von adeelleo

I want to use rSync for one of these sub folders not the main folder for each pool. Is that possible in any way?

Yep. You can run an rsync command line as a scheduled task, with no shared folder required if the copy is local. An example of how to do that is -> here. That documents a local drive-to-drive copy. All you have to do is drill farther down to the sub-dir of your choice.

As an example:
rsync -av --delete /ZFS1/ /srv/dev-disk-by-label-DATA1/ (This is in use and it copies a ZFS pool to an external drive.)

The above could be:
rsync -av --delete /ZFS1/pictures/ /srv/dev-disk-by-label-DATA1/pictures/ (This would copy a child filesystem in the pool to another drive/folder.)

A piece of advice: Leave the --delete switch out of the your command line until two copies are confirmed.

Zitat von adeelleo

Do i need to install the zfs-auto-autosnapshot for automated scheduled snapshots to make auto snapshots work or can this also be done through a scheduled task?

No. zfs-auto-snapshot is something you'll have to install on the command line. If you haven't used it yet, you'll need to install PuTTY.

The installation itself does nothing more than set up a series of scripts and cron jobs that utilize. This is both the up side and downside of auto-snapshot. It's simple and has no software dependencies, with next to nothing to break or go wrong and there's no software packages to be upgraded, ever. (And it will be this way into the foreseeable future.) On the other hand, zfs-auto-snapshot lacks the features of a more sophisticated package like ZnapZend. As raulfg3 suggested, ZnapZend can utilize the commands zfs send and zfs receive.)

(BTW: I gave thought to writing up a How-To for ZnapZend but it has package dependencies and there were dependency issues with Debian 10, around the time that OMV5 came out. Sometimes, simple is better than sophisticated, especially where new users AND the command line are involved.)

Once set up, zfs-auto-snapshot runs in the background. There's a doc for it -> here. Read through it and try to get an understanding of it first. Otherwise, the document walks through the setup, and it's pretty straight forward. The document goes to great lengths to make it understandable and easy to configure.