Differences

This shows you the differences between two versions of the page.

--- sysadmin:services:fileserver [2024/05/24 15:01] – created kjohns23
+++ sysadmin:services:fileserver [2024/05/24 15:37] (current) – kjohns23
@@ Line 6: / Line 6: @@
 ===== Configuration =====
+The SoCS primary file server is located at gringotts.socs.uoguelph.ca.
+==== Disk Configuration ====
+The server contains 12 disks. These are configured into a raid 10 zpool - 6 mirrors of two disks each. The configuration can be viewed with the "zpool status" command. These disks are mounted to /export. In general each discrete use case is it's own zfs filesystem. For example each home folder, or each folder backing a web service. This allows zfs attributes to be applied independently to each filesystem.
+==== NFS ====
+Folders that require access from other machines are shared using the "share nfs" attribute in the zfs configuration for each zfs filesystem. share.sec.krb5.rw is allowed from any SoCS IP while share.sec.sys.krb5 is only allowed for the trusted 192.168.100.0/24 back of rack network as sys authentication does not require the user's password for access unlike kerberos.
+==== Samba ====
+Samba sharing is enabled using the samba4 package, and configured in the /etc/samba folder. Samba is now used only for mounting SoCS home folders on Windows or Mac clients.
+==== Snapshots ====
+Snapshots are taking using the standard "zfs snapshot" command. This is done via a cronjob run by the root user to allow hourly, daily, weekly and monthly jobs. A second cronjob runs the /var/backups/clean_snapshots.sh script which will remove old snapshots. These snapshots use zfs copy on write filesystem feature and so are instant and take up no additional disk space.
+==== Backups ====
+Backups are currently manually run using rsync to send data to the SoCS backup file server, Dursley.