10 Reasons why SharePoint is not a File Server

sharepoint file server

Many companies are migrating to Office 365.   SharePoint Online is included with most subscriptions for free. Often, IT professionals are asked to evaluate moving their company file servers to SharePoint Online.  While SharePoint is great for collaborating on documents with teams inside or outside of the company, can it completely replace an on-premise file server for larger firms?

Here’s the list of the top 10 reasons we compiled on why SharePoint is not a file file server:

 

  1. Speed – Nothing can beat the speed of local network file server access. While Internet speeds are measured in Megabits, local network speeds are measured in Megabytes.  A local network connection is at least 10 times faster than any Internet connection.  For example, a fast 100 Mbp/s home Internet connection only equates to 12.2 MB/S.   In the office, networks are typically 1GB – a whopping 125 MB/s!!  For large files access, nothing beats a local area network connection.

 

  1. Simplicity – Users are trained to easily grab their files from a mapped drive. With SharePoint, files are stored in libraries that are accessed using a web-based interface. The interface looks nothing like Windows File Explorer.  Alternatively user can access file using the OneDrive for Business client which requires user training and  intervention to sync and to locate the shares they need.

 

  1. Storage Capacities – Even the smallest companies have easily terabytes of data. SharePoint Online has a 1TB limit on each library, a  5000 item display limit, a 15GB file size limit and a maximum 100,000 file sync limit.   Even if you did store this much data, or files this large, accessing them over the Internet may be unworkable (see Reason #1).

Microsoft Azure File Share Sync – seamlessly extend file services across servers and cloud storage

Microsoft announced the public preview of Azure File Share Sync at it’s 2017 Ignite Conference.  This technology extends file services from on-premise to Cloud Storage on Azure File Shares and across windows servers in multi locations.   Microsoft engineers interviewed customers and confirmed that Windows File Shares are still in use for a multitude of reasons.    The customer pain points identified include speed of access, control of data and large storage capacities.   Azure File Share Sync addresses these concerns.

Watch the Microsoft Ignite Session Herecloud storage

Some of the key features and include:

  • Bi-Directional Sync – from Windows Server to Azure Cloud Storage with write back capabilities
  • Multi-Site Sync – Sync a share across multiple Windows Servers through Azure File Shares to Cloud Storage with the ability to cache and edit data in real time at each site.
  • Backup of Azure File Shares to Azure Backup
  • Tiering of data – set the maximum data storage capacities for each Windows server and only replicate the most recent data to each server with the balance stored in Azure File Shares in the cloud.

The MyWorkDrive team is very excited about this announcement as it will give our customers the ability to setup a MyWorkDrive server in Azure, sync files to it and use it access file shares remotely or during a disaster.   Using MyWorkDrive, windows file shares can be accessed from any location worldwide over https (Azure File Sharing  only supports access over smb port 445 which is typically blocked from most remote locations).

This technology also provides a seamless way for MyWorkDrive customers to migrate their servers completely to Azure Cloud Storage and remove them from on-premise entirely utilizing MyWorkDrive to map drives or access them using our Web File Manager.