So I run Ubuntu at home and figured that I'd post my experiences with the ix4-200d and some of my configurations to help anyone else out there through the process of configuring the NAS with my setup.  (I'm also posting this so that in the event I lose my ubuntu box or have to build a new one, I'll have it online )

 

Configuration setup information by topic:

 

1) Rsync copy job

     a) I followed the rsync setup and configuration at: https://help.ubuntu.com/community/rsync

          - This page shows you how to setup and configure rsync, the rsync daemon and the files necessary to make it all play nice.

               - You MUST install the rsync, xinetd, and ssh packages for your distro to make this work

               - I have attached copies of my /etc/default/rsync, /etc/xinetd.d/rsync/, /etc/rsyncd.conf and /etc/rsyncd.secrets for your                       reference on how these files should look.

               - In the attachments I've changed my specifics and indicated items you need to change in ALL CAPS.

     b) After configuring the above and using the files as shown, you can then successfully use the rsync copy job command to backup your ubuntu system.

     c) NOTE: If you use NFS and have mapped NFS drives inside of your /home user area, it will back these up too.  This is good and bad depending on what you want on your NAS.  I have scripts that unmount my NAS drives BEFORE copy job and Mount AFTER it's completed.

 

---UPDATED to use rsync daemon excludes, to prevent issues with item c) above.  See updated code below! I added exclude from in the rscyncd.conf and a new excludes file in my home directory.  I also included the test commands to run to show what your rsync daemon will present to your Iomega ---

 

/etc/default/rsync

  1. defaults file for rsync daemon mode

 

  1. start rsync in daemon mode from init.d script?

  2. only allowed values are "true", "false", and "inetd"

  3. Use "inetd" if you want to start the rsyncd from inetd,

  4. all this does is prevent the init.d script from printing a message

  5. about not starting rsyncd (you still need to modify inetd's config yourself).

RSYNC_ENABLE=inetd

 

  1. which file should be used as the configuration file for rsync.

  2. This file is used instead of the default /etc/rsyncd.conf

  3. Warning: This option has no effect if the daemon is accessed

  4.          using a remote shell. When using a different file for

  5.          rsync you might want to symlink /etc/rsyncd.conf to

  6.          that file.

  7. RSYNC_CONFIG_FILE=

 

  1. what extra options to give rsync --daemon?

  2. that excludes the --daemon; that's always done in the init.d script

  3. Possibilities are:

  4.   --address=123.45.67.89          (bind to a specific IP address)

  5.   --port=8730                    (bind to specified port; default 873)

RSYNC_OPTS=''

 

  1. run rsyncd at a nice level?

  2. the rsync daemon can impact performance due to much I/O and CPU usage,

  3. so you may want to run it at a nicer priority than the default priority.

  4. Allowed values are 0 - 19 inclusive; 10 is a reasonable value.

RSYNC_NICE=''

 

  1. Don't forget to create an appropriate config file,

  2. else the daemon will not start.

/code

 

/etc/rysncd.conf

max connections = 2

  log file = /var/log/rsync.log

  timeout = 300

 

 

  comment = Home

  path = /home/USERAREA

  read only = yes

  list = yes

  uid = YOURUSERID

  gid = YOURGROUPID

  auth users = YOURUSERID

  secrets file = /etc/rsyncd.secrets

  exclude from = /home/ecrossley/rsync.excludes

  /code

 

/etc/xinetd.d/rsync

service rsync

    {

        disable         = no

        socket_type     = stream

        wait            = no

        user            = root

        server          = /usr/bin/rsync

        server_args     = --daemon

        log_on_failure  += USERID

    }

/code

 

/etc/rsyncd.secrets

USERNAME:PASSWORD

(Example:  NOBODY:cr@zy)

/code

 

/home/ecrossley/rsync.excludes (these are examples of directories that I do NOT want the rsync copy job to include in the backups, edit as you feel fit.  Anything with a trailing slash is a root level direcotry in my /home location.  Anything with a * will exclude any patterns written immediately after.  I exclude trash because no sense backing that up.)

 

- Music/

- Pictures/

- public/

- Videos/

- *Xauthority

- EMCSohoClient/

- .juniper_networks/

- .cache/

- .config/

- .mozilla/

- .local/share/Trash/

/code

 

Testing command:

 

In terminal type: 

sudo rsync USERNAME@HOSTNAME::share

 

My example:  sudo rsync ecrossley@Quad64::share

 

Replace USERNAME with the username identified above in the secrets file and hostname with the hostname of your Ubuntu system (Quad64 in my case)

 

The resulting list in the terminal window shows what files your Iomega drive can see and backup using the Copy Job feature in your Iomega control panel.

 

/code

 

2) Printing

     a) After moving my printer over (HP DeskJet 5550) to the NAS, I was unable to get my Ubuntu system to print to it properly.  As a result, I used the Windows SAMBA share option in your printer configuration (System, Administration, Printing).  This allowed me to print to my printer.

          - When configuring using this option, I found that I HAD to set authentication to allow printing to work.  I created a printer "user"                  via security in the StorCenter control panel and used that account for "authentication".  I've been able to print perfectly ever                  since.

 

3) NFS

     a) It took me a bit to get NFS to function properly; however, it's really not that complicated (I was just being a moron).

          - Make sure to set NFS options in the StorCenter settings section.

          - When you edit an existing share that has security, you will be presented with an option for a host and what host access rights you                  want.

          - Use the following commands to mount the NFS shares in your system:  sudo mount IPADDRESSOFNAS:/nfs/SHAREDLOCATION  /LOCALUBUNTUFILESYSTEM/LOCALDIRECTORY  (Example in my case:  sudo mount 192.168.xxx.xxx:/nfs/public/Media/xxxxxxx /home/ecrossley/Media/xxxxxx)

          - REMEMBER:  If you mount NFS under your home directory and execute a copy job, Ubuntu treats the NFS share as a local drive and will include it in your copy job.  This essentially duplicates all data you have on your NAS under your backup file location.  I personally didn't want this so I unmount the shares before the copy job rsync and remount them after.  This is until I move the shares to a different location in my filesystem (once I get around to it).

 

4) FTP

     a) DO NOT OVERLOOK USING FTP TO MAKE YOUR LIFE MUCH SIMPLER!!!!!!!!!

     b) Copy something to your NAS only to find out if you have to change it's location you have to do it through your client? - FTP is your answer

     c) After logging into FTP, you can drag and drop files using the FTP client (I use FileZilla) and not have to transfer data across your network or through the shares on your system.  You can literally move things from backup locations to public locations, public directories to private, between private to private, etc.

     d) This is possible because when you move something with the FTP client, it will use a RENAME feature in the FTP server and the server will just change the location of the existing files on the NAS, without it having to transfer across your network, etc.

 

 

Ok that's it for now, hope this helps someone.