FreeNAS-11.2-U3 Datasets replication

#1

I am running 2 FreeNASes both on the same version and both have the same datasets configured over the same mount mount “/mnt/nas-pool”

root@freenas1[/mnt/nas-pool]# ls -la

total 19

drwxr-xr-x 7 root wheel 7 May 14 16:53 .

drwxr-xr-x 4 root wheel 192 May 14 17:08 …

drwxr-xr-x 2 root wheel 2 May 4 08:12 DataScience

drwxr-xr-x 9 root wheel 9 May 14 16:53 iocage

drwxr-xr-x 2 root wheel 2 May 3 17:01 Lab_Infra

drwxr-xr-x 2 root wheel 2 May 3 17:02 Threat_Intel_Exchange

drwxr-xr-x 2 root wheel 2 May 3 17:01 Workshops

root@freenas1[/mnt/nas-pool]#


root@freenas2[/mnt/nas-pool]# ls -la

total 20

drwxr-xr-x 8 root wheel 8 May 14 18:29 .

drwxr-xr-x 4 root wheel 192 May 14 17:08 …

drwxr-xr-x 2 root wheel 2 May 4 08:30 Backups

drwxr-xr-x 3 root wheel 3 May 14 02:00 DataScience

drwxr-xr-x 9 root wheel 9 May 14 18:29 iocage

drwxr-xr-x 3 root wheel 3 May 10 02:15 Lab_Infra

drwxr-xr-x 3 root wheel 3 May 10 03:00 Threat_Intel_Exchange

drwxr-xr-x 2 root wheel 2 May 10 04:00 Workshops

root@freenas2[/mnt/nas-pool]#


The directories were created once i have configured the datasets.

Up until now all is good, I have configured the NFS share and was able to map it from ESXIs.

From the ESXIs i started to migrate the VMs to the specific folders, and after all the copy was done i went to see if the files were present. To my surprise none of the files were listed, even though i can access them from the NFS share from the ESXi.

root@freenas1[/mnt/nas-pool/DataScience]# ls -la

total 9

drwxr-xr-x 2 root wheel 2 May 4 08:12 .

drwxr-xr-x 7 root wheel 7 May 14 16:53 …

root@freenas1[/mnt/nas-pool/DataScience]#


From freenas2 i have a NFS mount called “/mnt/remote-nas” that indeed shows the files :


root@freenas2[/mnt/remote-nas/DataScience]# ls -la

total 85

drwxr-xr-x 10 root wheel 10 May 4 23:01 .

drwxr-xr-x 7 root wheel 7 May 14 16:53 …

drwxr-xr-x 2 root wheel 21 May 16 01:00 Atlantis

drwxr-xr-x 2 root wheel 21 May 16 01:00 DataLake

drwxr-xr-x 2 root wheel 22 May 14 16:32 hive-dev

drwxr-xr-x 2 root wheel 22 May 16 01:00 Jupyterhub

drwxr-xr-x 2 root wheel 21 May 16 01:00 neo4j

drwxr-xr-x 2 root wheel 18 May 14 01:00 postgresql

drwxr-xr-x 2 root wheel 18 May 14 19:05 redis

drwxr-xr-x 2 root wheel 18 May 14 19:00 tiems

root@freenas2[/mnt/remote-nas/DataScience]#

Question number 1: Is that the default behaviour ? Shouldn’t i be seeing these files when doing a ls on freenas1 ?


I have also configured the system do VMware Snapshots, DataSets snapshots as well as replication between them.

Replication seems to be working from the GUI as I have an “up-to-date” status on under Tasks -> Replication -> Status column. And indeed if i go to Freenas2 and issue a “zfs list -t snapshots” both on FreeNAS1 & 2 i see this :


root@freenas1[~]# zfs list -t snapshot

NAME USED AVAIL REFER MOUNTPOINT

freenas-boot/ROOT/default@2019-04-29-18:55:53 1.93M - 755M -

nas-pool/DataScience@auto-20190511.0100-2m 0 - 88K -

nas-pool/DataScience@auto-20190514.0100-2m 0 - 88K -

nas-pool/DataScience@auto-20190515.0100-2m 0 - 88K -

nas-pool/DataScience@auto-20190516.0100-2m 0 - 88K -

nas-pool/Lab_Infra@auto-20190510.0145-2m 0 - 88K -

nas-pool/Lab_Infra@auto-20190514.0145-2m 0 - 88K -

nas-pool/Lab_Infra@auto-20190515.0145-2m 0 - 88K -

nas-pool/Lab_Infra@auto-20190516.0145-2m 0 - 88K -

nas-pool/Threat_Intel_Exchange@auto-20190510.0230-2m 0 - 88K -

nas-pool/Threat_Intel_Exchange@auto-20190514.0230-2m 0 - 88K -

nas-pool/Threat_Intel_Exchange@auto-20190515.0230-2m 0 - 88K -

nas-pool/Threat_Intel_Exchange@auto-20190516.0230-2m 0 - 88K -

nas-pool/Workshops@auto-20190510.0245-2m 0 - 88K -

nas-pool/Workshops@auto-20190515.0245-2m 0 - 88K -

nas-pool/Workshops@auto-20190516.0245-2m 0 - 88K -

root@freenas1[~]#


root@freenas2# zfs list -t snapshot

NAME USED AVAIL REFER MOUNTPOINT

freenas-boot/ROOT/default@2019-04-29-19:20:01 1.91M - 755M -

nas-pool/DataScience/DataScience@auto-20190511.0100-2m 0 - 88K -

nas-pool/DataScience/DataScience@auto-20190514.0100-2m 0 - 88K -

nas-pool/DataScience/DataScience@auto-20190515.0100-2m 0 - 88K -

nas-pool/DataScience/DataScience@auto-20190516.0100-2m 0 - 88K -

nas-pool/Lab_Infra/Lab_Infra@auto-20190510.0145-2m 0 - 88K -

nas-pool/Lab_Infra/Lab_Infra@auto-20190514.0145-2m 0 - 88K -

nas-pool/Lab_Infra/Lab_Infra@auto-20190515.0145-2m 0 - 88K -

nas-pool/Lab_Infra/Lab_Infra@auto-20190516.0145-2m 0 - 88K -

nas-pool/Threat_Intel_Exchange/Threat_Intel_Exchange@auto-20190510.0230-2m 0 - 88K -

nas-pool/Threat_Intel_Exchange/Threat_Intel_Exchange@auto-20190514.0230-2m 0 - 88K -

nas-pool/Threat_Intel_Exchange/Threat_Intel_Exchange@auto-20190515.0230-2m 0 - 88K -

nas-pool/Threat_Intel_Exchange/Threat_Intel_Exchange@auto-20190516.0230-2m 0 - 88K -

nas-pool/Workshops/Workshops@auto-20190510.0245-2m 0 - 88K -

nas-pool/Workshops/Workshops@auto-20190515.0245-2m 0 - 88K -

nas-pool/Workshops/Workshops@auto-20190516.0245-2m 0 - 88K -

root@freenas2[/mnt/remote-nas/DataScience]#


Question 2: Shouldn’t these files be showing on FreeNAS2 as well ? from the looks of it if freenas1 melts i would only have the snapshots and not the full VMs ?

Question 3: Regarding VMware-Snapshots, they seem not to be working AT ALL, is there a way that i can check this process ?

If I understood correctly from all the reading that i’ve done VMWare-Snaphots should run first, (preferably with something to make sure that the VMs state are in a better than crash-consistent state with something called Quiescence (which needs vm-tools) and then Freenas once the VMware-Snapshots process is done, starts the dataset snapshots and ends with the replication task.

I am trying to wrap my head around this but it seems that FreeNAS documentation does only provide the bare minimum and the forum.freenas.org did not help me at all (not a single answer).

Any help is appreciated i can even pay for someone with experience to help me nail this down.

Thanks