Syncplify.me Server!: VFS with quotas

Syncplify.me Server! version: 4.0.0+

The Virtual File System (VFS) instroduced in Syncplify.me Server! v4.0, comes with a long-awaited feature: quota management.

The Windows OS features a very powerful yet complicated quota management, but it’s only available in Windows Server editions and requires optional features to be installed, therefore we could not rely on that and we built our own quota management system which is cross-compatible with all Windows systems.

Now, the problem with quota management is that calculating the current size of a folder (along with its sub-folders) can be very time-consuming, if the folder contains millions and millions of files. So if we were to re-evaluate the size to enforce quota restrictions at every operation it could totally kill the performances. Our solution the Quota TTL, which is the Time-To-Live (TTL) of the quota cache, expressed in seconds. Basically, when Syncplify.me Server! calculates the current size of a folder structure, it will consider such result valid for QuotaTTL seconds, without re-evaluating it too often. Continue reading

Parametric home directories

Syncplify.me Server! version: 4.0.26+

Another highly requested feature that we introduced in Syncplify.me Server! v4 is parametric home directories.

Some of our customers, in fact, need to isolate every user in their own directory under a general “container”, the directory name being the same as the user’s username. They also requested that if a particular user’s home dir does not exist, it is automatically created when the user logs in.

A structure like this:
C:\SFTPData
+----------\user_one
+----------\user_two

This is how you do it in Syncplify.me Server! v4. Continue reading

Syncplify.me Server! v4: the Virtual File System (VFS)

Syncplify.me Server! version: 4.0.0+

One of the biggest additions to the upcoming version 4.0 of Syncplify.me Server! is the VFS (Virtual File System) support. But what is it exactly? And what advantages does it bring to our users?

Let’s start by setting the bar with v3. Our version 3.x, in fact – as nearly every competitor – allows you to place users’ “homes” (root directories) on a disk. It can be a local or a network disk, but it’s basically disk-based. The following picture explains the concept in a visual way: Continue reading

Syncplify.me Server! v4: Encrypted File System

Syncplify.me Server! version: 4.0.0+

One of the most anticipated features that Syncplify.me Server! v4 will deliver is the ability to mount virtual directories – even nested ones – as encrypted virtual file systems.

fzfolders

The Encrypted VFS transparently encrypts and decrypts data on-the-fly during uploads and/or downloads, making sure that the files at-rest on the server side are always encrypted. This way you can run your server externally, and still always be sure that who operates the server for you doesn’t have access to your files/backups. This is also a requirement in some cases when your company has to comply to the PCI/DSS or HIPAA regulations. Continue reading

Syncplify.me Server! v4: the all-new VFS

Syncplify.me Server! version: 4.0.0+

One of the biggest changes that version 4 will bring to Syncplify.me Server!’s user base is the all-new Virtual File System. This is such an epic change that it’s actually one of the reasons why the release of v4 is taking longer than expected… but it will be worth the wait.

Check out the following comparison table to appreciate the main advantages of the new VFS over the previous approach (that was based on “virtual directories”):

Virtual Directory Approach (v1, v2, v3)Virtual File System (v4)
Virtual directories can only be placed directly under the user's home directoryIn a VFS, virtual folders can be placed anywhere, even nested within each other
All virtual directories are accessed "as" the user who logged in (single impersonation)In a VFS, each virtual folder can accessed "as" a different user profile (multiple impersonation)
Virtual directories mapped to UNC paths could not be accessed by "normal" user profiles, only by Windows or AD user profilesEach virtual folder has its own impersonation criteria, so even "normal" user profiles can access virtual folders mapped to remote UNC paths

Continue reading