Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

DRAFT



SmartSite's Storage Solution Requirements

See Jira: Sak-1978, sak-868 

  1. High availability, 24/7 service no downtime if at all possible
  2. Disaster recovery, replication to secondary site
  3. Optimized for fast read/write access
    1. WebDAV
  4. Needs to handle large amounts of files that greatly vary in size
  5. handles distributed access
  6. Archiving solution (snapshot feature)
  7. Backup solution
  8. Flexible file structure
    1. Compatible with JSR 170
  9. DC goal is to get off of afs for r/w volumes
  10. migration strategy from AFS to SAN - possibly using symlinks on app servers
  11. need to be in a place to move off of AFS if we have a crisis
    1. continuous rsync needed
    2. some sort of sync match with the database
    3.  

Three uses of afs for smartsite

  1.     software distribution
  2.     communication to My and Registrar
  3.     sakai content store with r/w locking mechanisms

Needed pieces

  •     san switch must have hba ports for each of app servers
  •     hba switches for each of app servers
  •     alternate is iscusi as link into SAN - scusi over IP
  • No labels