As some readers may know I currently work in Higher Education and while all of the business data is trivial to backup providing any level of backup service to students and academics is significantly harder. The challenges faced include the myriad of Operating Systems in use (Windows/OSX/Linux), the fact that the devices being backed up are inherently ‘untrusted’ (i.e. owned by the individual) and that they are often on networks (be it eduroam/public/home) that have no direct connectivity back to the internal trusted network.
Most enterprise class backup systems just aren’t suited to this kind of environment in that they cannot be securely published through a firewall or have exorbitant licencing costs for the number of devices to be protected (a few file servers vs 500+ student owned laptops).
One solution to this issue cropped up at a recent trade show where Synology were demonstrating their Synology DiskStation Manager NAS software which set itself apart from the traditional enterprise backup solutions with…
- Support up to 16,000 users on high end models (and 2048 on the kind of model that we would consider using) with no extra licencing costs, users can have storage quotas set either by group or per user
- Secure remote access (simply publish a single port which can be protected by HTTPS for encryption in transit)
- Home grown backup clients for modern versions of Windows, OSX/macOS and Linux
- On the point of OSX/macOS the backup client for Synology does not rely on Time Machine and so overcomes the issues associated with having to be on the same network as your backup device
- Home grown Btrfs file system which auto detects (and fixes) corrupted files through metadata along with extensive snapshot support
- Up to 32 recovery points and real-time file protection (when connected to the DiskStation)
So time for some screenshots! Below we have the initial setup of the Disk Station Manager and the installation of the client on a Windows PC.
- A business needs to provide backup to remote workers
- Those remote workers do not connect to the trusted network often
- Perhaps they don’t like VPNs/DirectAccess (and so rules out using Offline Files)
- and those remote workers do not use a commercial ‘cloud’ service to protect their data with
- Perhaps trusting a 3rd party to host the data is not an option
- The remote workers use OSX/macOS
- Those remote workers do not connect to the trusted network often
…then using a Synology DiskStation should be a serious consideration for that business.
So you now have your WebDAV server setup and its time to get this out to your users. To help you along you feel free to edit the guides below to your particular requirements.
Using Cloud - iOS (225.4 KiB, 1,148 hits)
Using Cloud - Windows Phone (196.8 KiB, 911 hits)
Using Cloud - Windows XP (157.4 KiB, 889 hits)
Using Cloud - OSX (193.4 KiB, 947 hits)
Using Cloud - Windows 7 (149.3 KiB, 1,113 hits)
Using Cloud - Windows Vista (166.2 KiB, 840 hits)
Using Cloud - Windows 8 (327.6 KiB, 955 hits)
Using Cloud with iWorks - iOS (5.1 MiB, 925 hits)
For further reading take a look at the links below-
- Basic setup of a WebDAV site on IIS.net – http://www.iis.net/learn/install/installing-publishing-technologies/installing-and-configuring-webdav-on-iis
- Basic setup of WebDAV on seanashton.net – http://seanashton.net/webdav/iis/ (some interesting reading on here about download folder and large file support)
- Using Windows authentication (instead of Basic Authentication) – http://blogs.msdn.com/b/benjaminperkins/archive/2013/08/01/setting-up-webdav-on-iis-using-windows-authentication-and-a-unc-mapped-drive-or-file-share.aspx I gave this a go when I was first setting up WebDAV but couldn’t seem to make it work all the same well worth a look.
In the previous article in this series we looked at the topology needed to setup a WebDAV infrastructure.
I’ll assume that
- You have a public DNS record which points to a IP address on your firewall which is in turn port forwarding 443 (HTTPS) to your IIS server (this also works through Web Application Proxys like the ones built into Smoothwall firewalls)
- You have a internal DNS record which points to the network adapter on your IIS server
- Your IIS server has your paid (and signed) SSL certificate imported
You will also need a few server roles installed on your IIS server (you can do this through Server Manager), these are
- Web Server (IIS)
- WebDAV Publishing
- Basic Authentication
- Request Filtering
- HTTP Logging and Logging Tools
- IIS Management Console (unless you feel like doing everything remotely)
So now to the fun bit! Which is all in the screen shot sequence below…
So you now have your server setup with the basics…so its time to do some testing. The screen shot sequence below shows how to connect to the WebDAV share on a Windows 8 PC.
Things you really need to test include
- Users only have permissions to access the folders you want them to
- You can upload/download files up to the maxium size you defined earlier
- That you can access the share from both inside and outside your network
In the next part you can get some example user guides that I have made for my own implementation as well as some links to further reading.
Every once in a while a magical bit of software comes along that makes life so very good; today that software is WebDAV and its been around so long that some people might have forgotten how good it is.
The premise goes
- You have one or more internal Windows Server(s) which hosts users personal documents and shared drives
- You would like your users to access these files on any device ranging from their home PC (running say Windows 7) to their personal mobile devices (iPad)
- You would like your users to access these files both inside and outside the firewall
- You would like your users to access these files natively (like a mapped drive) so they don’t have to muck around with web based applications
- You would like your users to be able to use this service with as little configuration on their part as possible
- All while maintaining a secure and auditable system
To accomplish this you will need a few things
- A valid paid for SSL certificate (don’t ever think you can get away with a self signed one) – personally I use a GoDaddy wildcard certificate
- A spare Internet Information Services (IIS) Server to host the WebDAV service on
- Depending on how things go 20 minutes
The basic topology is your clients point their WebDAV client at a DNS address which is mapped against a IP address which is port forwarded through your firewall to your IIS server which then serves requests to your file servers (clients don’t get to talk to the file servers direct). Don’t forget to setup your internal DNS to point to the internal network adapter of your IIS server as well.
In the next article I’ll run through the setup of a WebDAV server.
Since discovering it Munki has made my life looking after Apple Macs measurably easier. In short it allows the centralised deployment of Apple OSX updates as well as the deployment (and updating) of 3rd party software.
In the short screen shot guide below I show how to deploy the OSX Impero Client using Munki.