The Hierarchical File Server (HFS) is a centrally funded service providing backup and long-term archive services to Senior Members, Postgraduates and Staff. Users register online, pick up, install and perform simple configuration of the software on the client computer and then proceed to either back up or archive data to be safeguarded on the HFS.
The HFS uses IBM Tivoli Storage Manager (TSM) client-server software to manage the backup and/or archive data. Data is sent from the client computer, across the University (backbone) network to the HFS server and ultimately is stored on magnetic tape in an automated (robotic) tape library. The HFS servers and tape library are situated in a climate-controlled, secure location. Three copies of the data are made, each to separate tapes: one copy is held in an automated tape library; the second, in a fire-proof safe and the third in a fire-proof safe at an off-site storage facility. Access to the data is private to the owner and is normally available 24 hours a day, seven days a week.
2.1 HFS Systems staff cover is normally available from 09:00 to 17:00 on weekdays. Outside these hours there are no formal arrangements either for periodic monitoring of the HFS or for staff to be called, and no funding is provided to make this contractual.
2.2 If a fault is noted between 09:00 and 17:00 on a working day, IT Services will commence investigation and correction within one hour (provided that no similar fault is also being handled by the same team).
2.5 The HFS infrastructure is resilient to failure of several components. Most hardware failures are to one component: a single disk, tape drive, adaptor, cable or controller might fail and none would result in a loss of service. Additionally, each data storage element is dual-pathed with automatic failover, so an entire path might fail and all hardware resources would remain available. Were several hardware components to fail at the same time, then this may result in a degradation of service, the severity of which would depend on the precise mix of elements needing repair. A fault that rendered an entire SAN disk server inactive would also result in a partially degraded service. A fault that rendered one or both of the automated tape libraries inactive could have significant impact: there may for example be no access to client data already stored with the service (i.e. for restore or retrieve purposes) until it was fixed. Extended outage of the tape libraries would necessitate a total loss of service (i.e. neither backup nor restore facilities would be available).
2.6 No alternative exists to any of these facilities within Oxford. 'Cloud' backup and storage solutions exist (e.g. Amazon's S3) but the location of the storage facilities outside the UK poses problems for University-owned data.
2.7 IT Services has a contract for all HFS hardware maintenance with IBM. Pivotal items in the SAN, such as the tape library, host and disk servers - where failure would or could cause major degradation of service - are covered by 7x24 service call reporting. Other items, such as switches and tapes drives - where failure would not lead to a major degradation of service - are covered by 5x11 service call reporting.
In practice the above means that for a major hardware failure of the tape library, the SAN disk servers or the servers hosting TSM, an engineer would normally attend within 1-4 hours. Parts are not guaranteed to be available in any particular period (some parts are available on the same day, some are sourced from Europe and arrive next day). Problems with tape drives and single disk drives would normally be fixed within 1-2 days.
2.8 Software updates to the IBM equipment are supplied by IBM, and are mounted by the IT Services HFS team. Except in the case of a major system breaking fault, or the risk of a major breach of security, we will aim to give one week's notice of any down-time on any part of the HFS.
Information for Departments and Colleges wishing to register new clients is given at http://www.oucs.ox.ac.uk/hfs/help/registration.xml. Registration for backup service is available online. Requests for archive projects are initiated by completing a web application form which is then processed offline, more details are available at http://www.oucs.ox.ac.uk/hfs/archive/index.xml.
Notification of major faults, outages, TSM server upgrades or downtime is circulated on the mailing list email@example.com and on the IT Services Status web page http://status.it.ox.ac.uk/.
2.12 Initial problems should always be directed to local IT support. Where problems cannot be resolved there, they should be reported to the IT Services Help Centre. First level support is provided via the Help Centre with specialist follow-up diagnostics and advice provided by the HFS team.
2.13 The HFS web pages at http://www.oucs.ox.ac.uk/hfs provide comprehensive advice and guidance on installing, configuring and using the TSM client, as well as a comprehensive FAQ . An introductory course on how to use the TSM backup software is also available once a term.
Additionally, we may insist on local measures being implemented in order that the backup or archival of data does not consume a large amount of (HFS) system resources. These local measures may include, but are not limited to:- excluding files, re-partitioning into smaller filesystem/volume/drive partitions or pre-processing files before backup or archive.
IT Services operates a chargeable service for use of the HFS Archive by a project that exceeds 4TB of storage and/or extends beyond the initial 5 years. The unit cost is per Terabyte (TB) per year and will generally be purchased for five years. The cost takes into account the staff, media and maintenance costs incurred in managing large amounts of data as well as of indirect costs. Staff costs have been calculated as 'directly-allocated'; that is, staff time for the management and support of data is averaged rather than audited.
The current (2013/14) price per TB per year is £360 for the HFS Archive service (above the initial 4TB). The charge applies at the terabyte boundary and is due in advance. To reduce administrative costs, we would appreciate orders for extra archive storage above 4TB to be made in blocks of 2 years or more i.e. not on a yearly basis.