File Server Hosting allows your UF organization to lease fully managed file server resources (accessible via SMB or NFS) from UFIT's infrastructure. UFIT manages all the elements of purchasing and maintaining hardware resources and overall administration of servers. Your file server will live in UF's private file server cloud which may include NAS appliance failover across multiple physical locations to prevent downtime due to hardware failure or maintenance.
UFIT provides all compute and network hardware and infrastructure for the file server appliance. UFIT provisions your file space and works with your IT staff to assign administrative privileges and permit access via network ACLs and file share permissions.
You will assign one or more of your IT team to fulfill the role of file share administrator. This role will manage snapshot restores, file-system security privileges, drive mappings, and other client-side configurations for users.
File Server Menu
|Features||Basic Tier||Capacity Tier||Performance Tier|
|Min/Max Size (above 10TB may require review and approval)||1TB/100TB||1TB/66PB||250GB/66PB|
|High Availability||Single Site||Single Site||Single Site|
|Snapshots (more info)||Yes||Yes||Yes|
|Access Protocol||File (SMB, NFS)||File (SMB, NFS)||File (SMB, NFS)|
|Encryption at Rest||Yes||No||No|
|Encryption in Transit for Client Access||Available for SMB||No||No|
|Average IOPS Per TB||~5||~15||~100|
|Replication Available (to a second local datacenter)||Yes||Yes||Yes|
|Limited Service failover (site disaster)||Replicated Shares Only: Yes||Replicated Shares Only: Read-only||Replicated Shares Only: Read-only|
|Encryption in Transit for Replication||Yes||No||No|
|Backup Service Available||No||Yes||Yes|
|Archive Service Available||No||Yes||Yes|
For more information about the terms used see Used Terms Definitions below.
|Snapshot Schedule Options|
|Limited: 1D/7D||Once daily retained for 7 days.|
|Multiple||The snapshot options can be combined based on customer requirements.|
|Default: 1D/14D||Once daily, retained for 14 days.|
|1H/24H||Every hour, retained for 24 hours.|
|4H/5D||Every four hours, retained for 5 days.|
|1D/14D||Every day, retained for 14 days.|
|1W/6W||Every week, retained for 6 weeks.|
|1M/6M||Every month, retained for 6 months. [ every 30 days, retained for 200 days ].|
Used Terms Definitions
|Performance Tier||Business/department critical shared files, high throughput and performance with frequent access.|
|Capacity Tier||Default storage tier. Front office fileshares, large datasets, infrequent or occasional access.|
|Basic Tier||Lowest cost durable storage. Limited performance, for files that are rarely accessed but need to be available online.|
|Size||Currently defined in multiples of 250GB for Performance Tier and 1TB for Basic and Capacity Tiers. Larger file share capacities may be available by request and require approval.|
|RAID Protection||Provides industry standard Redundant Array of Independent Disks (RAID) protection via Parity and other redundancy mechanisms.|
|Mirroring||Provides real-time near 0 RPO synchronous mirroring of data to other site (SSRB <--> UFDC), not user configurable.|
|High Availability||Dual site provides controller-level redundancy and data availability cross-site in case of localized site disasters/outages; single site provides controller-level redundancy only.|
|Snapshot||Point in time copy of a storage offering, saved for some time for potential resotration of the storage to the time the snapshot was taken. Snapshots exist on the primary storage system, so failures destroying primary data may affect snapshots too. Contrast with 'backup'.|
|Snapshot Schedules||See "Snapshot Schedule Options" table below.|
|Nested Shares||Ability for a folder/directory within a share to also be shared via another name, usually with different connection permissions.|
|Nested Quotas||Ability to assign a quota to a specific subdirectory within an existing larger quota.|
|Access Protocols||File (SMB, NFS).|
|Encryption at Rest||Industry-standard cryptographic ciphers encrypt your data before writing it to persistent storage. Thus, if a storage drive is lost or stolen, the data stored on it cannot be read. Required by many regulatory standards.|
|Encryption in Transit for Client Access||Provides the ability to encrypt data between file server and client. Currently only available for SMB and requires the client to support SMB3 with encryption. Additional client configuration may be required to enforce this setting. Enabling this feature may prevent unsupported clients from connecting to the share. Create a Service Request (SR) for assistance in enabling this feature.|
|Average IOPS Per TB||A measure of file system performance. Average Input/Output Operations per Second per TB.|
|Cost||Cost per TB per Month.|
|Replication||Copying a share/export from the primary site to a secondary site in the same local region. Available sites are UFDC and SSRB.|
|Limited Service failover (site disaster) for Basic Tier||In the event of a disaster of the primary site, UFIT Storage Team will execute a service failover to the standby site. Only those file shares and exports configured for replication will be available. Non-replicated file shares and exports will remain unavailable. The following conditions and Service Level Expectations (SLEs) apply:
|Limited Service failover (site disaster) for Performance and Capacity Tiers||The following conditions and Service Level Expectations (SLEs) apply:
|Encryption in transit for Replication||This refers to the availability and use of industry standard encryption in the replication of data from the primary site to a secondary site for shares configured for replication.|
|Backup||A data copy stored in a physically independent system. Even catastrophic failure of the primary system does not damage the "backup" copy. (Cold copy, takes time to be restored to production system in event of disaster or outage). Due to performance constraints we cannot offer this service on the Basic Tier.|
|Archive||Data which is intended to be stored for "a long time" in the view of the customer, seldom read, seldom re-written. (vaulted, cold copy, takes longer than backup service to recover, reconstitute and recover to production systems). Due to performance constraints we cannot offer this service on the Basic Tier.|
Snapshot Schedule Options (snapshots are taken between 11:55 PM and 5:00 AM (staggered during this period)).
If users define snapshots for the share, they can perform file-level restores via Windows Previous Versions or Linux equivalent functionality.
Should you require longer-term data protection or independent data backups, UFIT staff can assist you in configuring and maintaining a TSM backup service.
Advanced Client-side Configuration Recommendations
For Performance and Capacity shares: to minimize client disruption during File Services failover in the event of disaster, Windows users may ask the UFIT Microsoft Core Team to create a DFS namespace for the share. Then, they may configure the primary site UNC and secondary site UNC as weighted paths in DFS and access their share in this manner. Similarly, Linux users may configure the Linux automount client to fail-over between the primary site and secondary site paths. Fileshare access remains read-only at the secondary site. To restore read-write access to your share/export at the secondary site, create a service request ticket with the storage team.