Network Filestore

Policy

1. All source data and documents representing your intellectual and business contribution to the University should be stored on corporate network file servers.
2. The School provides a dependable filestore with adequate backup and recovery procedures.
3. No "master" data or code development should be kept on local desktop hard-disk storage.
4. Temporary or "scratch" space, eg full un-summarised simulation results should by written to local hard disk, with definitive summaries transfered to the network filestore within hours of completion.

The School filestore, aka `N:' or `.n'

The School uses Network Attached Storage systems to provide the required data storage. Feature of the implementation are:

• Servers are purchased in pairs and set up as replicas of one another located in separate buildings.
• Each server has an array of RAID-5 disks, so in the event of a drive failure the server will continue to operate seamlessly without loss of data.
• On a given one of a pair, half provides live space to users in the vicinity of the location, and the other half holds a replica of the live portion of its matched pair. The replication is done each night. Thus in the event of server destruction, the data from before midnight is still available on-line.
• Storage is quota'd merely to reduce the risk of a single user with uncontrolled processes consuming all available disk space.
• If you hit quota limits, contact the IT helpline for more.

View information on your file storage and quotas.

For information on how the TLC Filestore operates, please visit the TLC Filestore page.

The logical appearance of the network filestore on your desktop depends on the client operating system you are using.

Changing file access permissions is also dependent upon the desktop client windowing system.

Accessing SEE filestore from the UoE Microlabs

Unison: File Synchronisation for Laptops