Network Attached Storage: Difference between revisions

From Iskomunidad
Line 11: Line 11:
<br /><br />
<br /><br />
==Deployment==
==Deployment==
* Remote Site A: initial rollout: 4TB contiguous space, using 2x2TB commodity hard drives (expandable to 6x2TB; there appears to be a limit to hd size - 2TB - before getting errors).
* Remote Site B: initial rollout: 4TB contiguous space, using 2x2TB commodity hard drives (expandable to 6x2TB; there appears to be a limit to hd size - 2TB - before getting errors). This is meant to cope with backup requirements that now exceed the capacity of Remote Site A:<br />
[[Image:Df_sh_of_remote_site_A.png]]
 
<br /><br />
<br /><br />



Revision as of 12:49, 21 April 2013

For its backup needs, DILC is initiating a network-attached storage (NAS) project. The goal of the project is to deploy inexpensive, reliable, robust, scalable backup system for DILC's use.

Specs

The system

  • uses NAS4free.org
  • embedded installation (USB)
  • protocols deployed SFTP, NFS, Samba, AFP, RSYNC
  • intranet only
  • ZFS



Deployment

  • Remote Site B: initial rollout: 4TB contiguous space, using 2x2TB commodity hard drives (expandable to 6x2TB; there appears to be a limit to hd size - 2TB - before getting errors). This is meant to cope with backup requirements that now exceed the capacity of Remote Site A:



Development Team

  • Ma. Cristina Dalupan - Team Leader
  • Raff Alimbuyuguen
  • Don Cadavona
  • Thaniel Jay Duldulao
  • Nick Tunac



To Dos

  • Webdav integration
  • throughput optimization
  • persistent automount
  • peer-to-peer syncing of files via direct private torrent