Download napp-it ZFS server.
You have three options, select your use case:
Option1: napp-In-One (napp-it based all in one server)
Download one of the VM appliances, unzip (prefer 7Zip) read the included readme and upload to ESXi - may take some time.
Option 1 for production use, Version 13b, Jan 11 2014:
OmniOS 1008 stable, napp-it 0.9d2/ 0.9e1 with vmware tools 5.5 and vmxnet3 + e1000)
Option 2 for home and lab use: Version 14a, Jan 11 2014:
OmniOS 1008 stable, napp-it 0.9e1 with vmware tools 5.5, vmxnet3, e1000 + all add-ons and services like
Netatalk 3.1, ProFTP, Apache, MySQL, Owncloud, PHPMyadmin, Mediatomb DLNA server, rsync 3.1, tftpd
read how to setup Napp-In-One
Read the article about this solution at www.servethehome.com
appliance 13a: initial release 2013, problem with e1000 on ESXi 5.5
appliance 13b: base napp-it config (install add-ons separately), e1000 with tcp offload disabled
appliance 14a: full napp-it config, first release 2014 with all add-ons and services
Napp-in-One offers the most options and flexibility. Download ESXi 5.0U3, 5.1 or 5.5 free without RAM-Limit from vmware.com (ESXi is a ultra lightweight Hypervisor - think about as a Super Deluxe Bios extension where you can run supported operating systems like BSD, OSX, Linux, Solaris or Windows side by side, each with best performance). You should own a modern mainboard with passthrough support (vt-d) to virtualize your NAS/SAN with similar performance like a barebone setup or you can try a physical RDM (Raw Disk Mapping) setup.
Install the free ESXi 5.5 (or 5.1) edition. enble pass-through support in your mainboard bios and in ESXI. Download the zipped and preconfigured VM, unzip it and upload the VM folder via ESXi filebrowser to a local ESXi datastore. Import the VM with a rightclick on the .vmx file within the folder. Add your SAS controller as a pci device via pass-through to your OmniOS SAN VM and boot it up. It is ready to run with 5.1/5.5 vmware tools, two nics (e1000 and vmxnet3 in dhcp mode) and root pw unset. Run ifconfig at console to get current ip and manage via browser and http://ip:81.
In a larger ESXi environment, you can use several Napp-In-Ones where each ESXi use its own local highspeed ZFS SAN. No single point of failure and no SAN bottleneck. You can use Napp-In-One datastores locally or remotely and you can use combined VMmotion and storagemotion to move to another machine.
Download a ready to use napp-it ZFS server VM based on current OmniOS stable.
For end-users this is free even commercially. Resellers need a bundling license.
Please discuss problems at http://forums.servethehome.com/solaris-nexenta-openindiana-napp/
I found stability problems when using e1000 on a default OmniOS VM under ESXi 5.5
It works either when using the VMXnet3 vnic or when adding the following lines to /kernel/drv/e1000g.conf (reboot required)
#Disable TCP segmentation offload and LSO (napp-it all-in-one)
Maybe similar to this problem:
If vnic problem remains:
Stay at ESXi 5.1 or use a physical nic with pass-through for external transfers in addition to a vnic for internal traffic.
and disable LSO with command:
ndd -set /dev/ip ip_lso_outbound 0
and http://www.vmware.com/pdf/Perf Best Practices vSphere5.5.pdf
Option2: barebone setup
Use this method if you like your own setup, if you only need simple NAS/SAN config without advanced support for other operating systems or if you need a dedicated highspeed NAS or SAN.
Download a bootup ISO of OmniOS, OpenIndiana or Solaris 11.1, burn it and install to a local Sata disk or fast USB stick (min 16GB, prefer 30 GB, best are SSDs). Configure your network and install napp-it via online command
wget -O - www.napp-it.org/nappit | perl
After setup I suggest to clone the bootdisk to an external disk or an SMB/NFS share (can be your desktop) with clonezilla (from USB stick) or with the help of an 3,5" hardware Sata raid 1 enclosure. If you care about uptime, do a ZFS boot mirror on two disks. If you use a hardware raid-1 enclosure, I would use it with its hotplug capability to clone the bootdisk - not for regular raid-use as they are not as good as ZFS mirrors.
In case of problems, use the bootable backup disk or restore from image with clonezilla within minutes.
Option3: napp-it ToGo (napp-it on USB)
- Download ready to use samples
Napp to Go is a preconfigured ready to use installation of OmniOS + napp-it on USB sticks suitable for a special mainboard. You must plugin the stick into the same USB slot that was used during installation.
Napp-it to Go is ideal for distribution, tests or deployment of napp-it. You only need to download the image, clone or backup it with the
included Windows USB imager to a fast 16 GB stick. You can then bootup your NAS. It is ready to use in a dhcp environment or you must set ip manually.
Download von "napp-it to go Sample images". (Ready to use USB images, download, boot, run)
-Build your own USB/ napp-it ToGo setup (suggested as the samples are not always up to date)
- use a 32 GB Stick, best is a 30 GB Sata SSD in an USB enclosure
- do a regular setup
- disable ZFS property atime to reduce writes
- backup/clone the Stick with my USB cloner (or use clonezilla) for easy restore
After initial setup of a base napp-it server, you can install add-ons
AFP-Server with TimeMachine (V. 3.x), this is included in the VM image:
wget -O - www.napp-it.org/afp | perl
I have tried to setup AFP with a new install on OmniOS 1008 and failed with
ld.so.1: afpd: fatal: libsasl2.so.2: open failed: No such file or directoryy.
My other config (OmniOS1006 with AFP installed and the updated to 1008 work)
Mediatomb DLNA mediasrver (included in the VM)
wget -O - www.napp-it.org/mediatomb | sh
wget -O - www.napp-it.org/ampo | perl
wget -O - www.napp-it.org/proftpd | perl
Please read the Manuals:
Like a Desktop environment on OmniOS?
seems possible, see http://pkgsrc-us-east.joyent.com/changes.html#major-changes-in-pkgsrc2013q4