Install urBackup 2 on TrueNAS 12

This is an update to EDLver for TrueNas 12 core. It is an attempt to move my personal urBackup server from Windows 2012 server VM on ESXi to a jail on TrueNAS core server. Mostly it is an academic test, but might lead to actual production changes

Why install urBackup on TrueNAS - Some good reasons

Usage of ZFS
Usage of a true NAS System as storage-backend
- You can present a urBackup RAW Images over iScsi (if basic Iscsi is configured, it takes only a minute!)
- You can share Urbackup File Backups over SMB or NFS
- Perfect documentation for TrueNAS
- Enable easer backup of data to cloud because currently W2012 is sitting on iSCSI volume in TrueNAS and that cannot be backed up to BackBlaze B2

Important Note - Keep your path as short as possible

FreeBSD can only mount a path with a length of 88 characters! (Further reading https://forums.freebsd.org/threads/hack-against-88-character-mount-path-limitation-what-is-it.63816/) For this reason i kept the zfs names very short. Because urBackup is installed in a jail, each path is prepended with the path of the jail itself.

BAD Example: The ZFS-pool is named "FAST-DISKS" and the ZFS Datasets, where the jails are placed, is called "JAILS". Your JAIL name is urbackup01. Then your path /mnt/FAST-DISKS/JAILS/urbackup01 is already 33 characters long.

But in the Jail urbackup01 also zfs mount points exists for Urbackup. The name of ZFS-Dataset for imagebackup is: FAST-DISKS/URBACKUP/VOL01/IMAGE In your Jail this ZFS Dataset is mounted in /mnt/FAST-DISKS/URBACKUP/VOL01/IMAGE The complete path relevant for the mount, because the Jail path is also added, is now /mnt/FAST-DISKS/JAILS/urbackup01/mnt/FAST-DISKS/URBACKUP/VOL01/IMAGE with 69 characters.

If Urbackup now trys to backup the server testserver01 it will fail. Because Urbackup creates another ZFS Dataset with the name of the Server (FAST-DISKS/URBACKUP/VOL01/IMAGE/testserver01) and a ZFS Dataset for the current Backup (FAST-DISKS/URBACKUP/VOL01/IMAGE/testserver01/180530-1939_Image_C).

The complete path for the backup is now /mnt/FAST-DISKS/JAILS/urbackup01/mnt/FAST-DISKS/URBACKUP/VOL01/IMAGE/testserver01/180530-1939_Image_C with 102 characters.

If urBackup try to mount this path it gets "file name too long" and the backup will fail.

Create a ZFS-Dataset for Jails

Use a ZFS-Pool with a short name (e.g. ZFS-Pool s01) - vdisk01
Create a ZFS-Dataset with name j (Jails) - jails
Goto Jails -> Configuration and choose the ZFS-Dataset j as "Jail Root" (complete path /mnt/s01/j)

Create Jail for Urbackup

Goto Jails -> Add Jail
Activate Advanced Mode
Name: ub01 (Short name! See Important notice) -u1
Choose your IP-Address
Set the following "Sysctls" under Jail Properties: (reference for Parameters https://www.freebsd.org/cgi/man.cgi?query=jail&sektion=&n=1)

allow.mount
allow.mount.zfs
allow.raw_sockets

Click "OK" to create the Jail (takes a while)

Basic Jail config

Connect with ssh to your FreeNAS Server
Connect to your Jail by using the shell icon
Enable ssh in Jail:
- pkg install nano sudo
- sysrc sshd_enable
- sysrc sshd_enable=YES
- service sshd start
Add User jail_adm pw user add -n jail_adm -c 'Jail Admin' -d /home/jail_adm -G wheel -m -s /bin/tcsh
Set password for jail_adm passwd jail_adm
Edit sudoers file visudo
- Look for comment on wheel group and remove it, use command r, save with :w, save with :q

Open your SSH Client and test if you can connect to your Jail u1.

Present ZFS-Datasets for backup storage

In this Step three ZFS-Datasets are created. One for the Urbackup Image backups, the second for the Urbackup File backups and the third for the "Backup storage path".

Use a ZFS-Pool with a short name (e.g. ZFS-Pool b01 - For Backup Pool 01)
- Create a ZFS-Dataset b01\u1 (Dataset for urBackup - (Jail u1))
- Create a ZFS-Dataset b01\u1\b (Dataset for urBackup - Basic for Webinterface -> Settings -> "Backup storage path:" )
- Create a ZFS-Dataset b01\u1\i (Dataset for urBackup - Images)
- Create a ZFS-Dataset b01\u1\f (Dataset for urBackup - Files)

All ZFS-Datasets has to be created on the same ZFS-Pool (in this example b01)! If you don't place all ZFS-Datasets on the same ZFS-Pool, the free space calculation is wrong.

Some basic informations about Jails and ZFS: In FreeBSD a Jail cannot access ZFS-Datasets until it's allowed. The first step is to set Sysctl's as already done above. The second step is to run some commands after the startup of the Jail on the FreeNAS server to "present" the ZFS-Datasets to the Urbackup Jail and mount the ZFS-Datasets.

Login with SSH on your FreeNAS Server
Goto you Jail ZFS-Dataset Folder (as configured at the beginning): cd /mnt/vdisk01/j
Goto to you ub01 Jail config: cd .ub01.meta
Add post start commands (at the end of the file): vi jail-post-start

zfs jail u1 b01\u\01
zfs set jailed=on b01\u\01
jexec ub01 zfs mount -a

Restart the Jail (Webinterface: Jails -> View Jails -> Red stop button and then green start button)
Connect with SSH to ub01
Execute zfs list: You should see your ZFS-Datasets presented to the Jail ub01
Execute df -h: The ZFS-Datasets (and the child datasets) should be mounted in /mnt/b01/u/01