Difference between revisions of "User:Djgreen/Research Storage plans"
Jump to navigation
Jump to search
m |
m |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
==Current Status of SAN== | ==Current Status of SAN== | ||
Virtual Servers -- 500GB/500GB | Virtual Servers -- 500GB/500GB | ||
| + | |||
IT infrastructure -- 1TB | IT infrastructure -- 1TB | ||
| + | |||
Research -- 1TB | Research -- 1TB | ||
*massive growth expected | *massive growth expected | ||
| Line 28: | Line 30: | ||
\\wolftech\research\<unit>\<projectID>\ | \\wolftech\research\<unit>\<projectID>\ | ||
| − | *where <unityID> is an identifier for the individual projects. These would need to be readable... perhaps including the sponsor name, and a faculty suggested 'short' project name (which we'd have them enter when requesting the space initially). | + | *where <unityID> is an identifier for the individual projects. These would need to be readable... perhaps including the sponsor name, and a faculty suggested 'short' project name (which we'd have them enter when requesting the space initially). \\wolftech\research\ece\darpa_laserscope\ for example. We'd have to make sure the system kept all sponsorname/descs unique -- though that shouldn't be difficult. |
| − | \\wolftech\research\ece\darpa_laserscope\ for example. | + | |
| + | There is a worry that having a massive list of projects would cause issues, but Pat feels that most people will either create links to their space, or map drives directly to it, rather than following the full path down to the project. | ||
| + | |||
| + | ==TODO== | ||
| + | ? | ||
Latest revision as of 11:13, 5 December 2006
Current Status of SAN
Virtual Servers -- 500GB/500GB
IT infrastructure -- 1TB
Research -- 1TB
- massive growth expected
Backups -- 1TB
- currently loaned to CNR for development
- will replace NBP client for staff
- move AD server backups here as well
Research Path
\\wolftech\research\<unit>\
<unit> -- refers to those hosting the fileserver/storage Initial units would be:
- ece
- bme
- itecs
- cnr
Units will then need to identify the layout underneath the \<unit>\ level. We need to identify two initial breakdowns to start with. Suggestions include:
\\wolftech\research\<unit>\<subunit>\
- where <subunit> is a department
\\wolftech\research\<unit>\<unityID>\
- where <unityID> is the facultyID
\\wolftech\research\<unit>\<projectID>\
- where <unityID> is an identifier for the individual projects. These would need to be readable... perhaps including the sponsor name, and a faculty suggested 'short' project name (which we'd have them enter when requesting the space initially). \\wolftech\research\ece\darpa_laserscope\ for example. We'd have to make sure the system kept all sponsorname/descs unique -- though that shouldn't be difficult.
There is a worry that having a massive list of projects would cause issues, but Pat feels that most people will either create links to their space, or map drives directly to it, rather than following the full path down to the project.
TODO
?