Regional Storage

---

Files.com has servers across the globe and provides the option to configure the geographic region (and by extension, political jurisdiction) where your files will be stored. Once the geographic region is changed, new files will be immediately stored in the newly selected region. Files that were stored prior to the region change will be migrated automatically to the new region in a background process.

There are a number of reasons, you might choose to enable Files.com multi-region storage feature for your site. You can use the feature for keeping or restricting files to a specific geographical region in order to comply with legal restrictions like GDPR, HIPAA, company policies, etc. You could enable regional storage for minimizing network latency for heavily used or large files frequently accessed by users residing in a region distant from the default region. You might use multi-region storage for conserving bandwidth in heavy traffic regions by leveraging the presence of servers in the same or nearby geographical region rather than transferring large files across multiple continents

Regardless of your plan level, site administrators can set your entire site, at the root level, to store all files in any single region.

If you are on a Power plan, your site can have more than one region active at the same time, and site administrators and users with admin rights to a folder can set your region choice on any folder.

The following regions are currently available: USA, Virginia; Australia, Sydney; Canada, Toronto; UK, London; EU - Germany, Frankfurt; Japan, Tokyo; and Singapore.

Multi-region storage settings are available only at the folder level. Individual files cannot be configured to be served from a different region. When you change a folder's storage region, the server storage will cascade down through all subfolders, provided they were created with the default setting of Inherit from Parent Folder.

Since region changes cascade through all nested subfolders and files, care should be taken when designing the folder hierarchy to avoid undesired region changes.

If you use Files.com's Regional Storage features in conjunction with its Sync or Mount features that enable direct connections to 3rd party platforms such as Azure, S3, Box, Dropbox, etc., please be aware that, by default, network traffic will travel through Files.com's servers in the USA when transiting to and from these platforms, even if the data in your Files.com folder is ultimately stored in another region.

This default setting is because performance, throughput and efficiency is superior in our USA based cloud. Refer to the Changing the Geographic Region of Data Routing section for details about how to configure this setting to use a different geographic region.

Site administrators or users with admin access to a folder can change the storage region of a folder using the web interface using the regional storage button immediately to the left of the Folder settings button at the top of that folder's listing.

The geographic region of a folder can also be configured programmatically using the Storage Region Behaviors API.

Another option is to use the Command Line Interface (CLI) app to configure the geographic region of a folder. You can use a command simlar to the one below, replacing VALUE with the appropriate value for the desired storage region and path/to/folder with the full path to the folder you're configuring.

files-cli behaviors create --path "path/to/folder" --behavior="storage_region" --value="VALUE"

Custom Domains and Regional Storage

If your site uses a custom domain name, migrating your root folder storage location will also move the SSL certificate, and this may cause a brief interruption to your service while the DNS change propagates. Your users may lose access to the site for approximately 15 minutes, so you should consider initiating the change at an opportune time.

If you are using a custom domain and change the primary region where files are hosted on your Files.com site, we will issue you new IP addresses in the new region and release your old IP addresses.

Data routing refers how data is transferred to or from remote servers. The settings for restricting the flows through non-USA regions are only available when your top-level, or root, folder is set to a non-USA geographic region.

There are two options for restricting data routing to a geographic region. You can apply a global restriction to your site so that all data routing is restricted to a geographic region, or you can apply individual restrictions to each remote server, allowing you to configure individual remote servers to use either the default USA geographic region or the geographic region of your top-level, or root, folder.

A site administrator can enforce the geographic region of your data routing for all remote servers in your site. Type "Data routing" in the search box at the top of every page and click on the matching result. Click the slider toggle for Remote servers data regional routing.

To enforce geographic region for the data routing of a specific remote server, edit the Remote Server configuration and update the Data Regional Routing setting for the connection.

The first use case listed at the top of this article is self-explanatory. The remaining cases are concerns for organizations with users based across multiple continents. Organizations with such an international presence are typically on a Premier plan.

Let's examine how to configure data routing when the goal is minimizing network latency for heavily used or large files frequently accessed by users residing in a region distant from the default region. If a company headquartered in Australia has offices in Singapore, Japan, France, and the UK but hardly any presence in the US, then the multi-region storage feature with proper configuration of the folder structure can really improve the performance of their Files.com site.

This example can be performed with a Premier account which provides access to all regions, or with a Power account using only two regions.

The first step should be to identify which content is specific to each region, especially those files that are either frequently accessed or those that are extremely large, like videos or architectural drawings. Once the high-impact content has been identified, a redesign of their folder structure may be needed.

All files targeted at a specific region should be contained in the same set of folders which will need to have their geographic region changed to the one closest to the primary users of this content.

Imagine we have a Training folder as a top-level folder for some training videos which are being produced in different languages for each country where they have offices. The easiest approach is to organize the videos by language and country into their respective folders (faor example, "Videos-en-AU" for English language videos used by Australian employees, "Videos-en-UK" for English language videos used by our British employees "Videos-fr-FR" for French language videos in France, "Videos-fr-BE" for French language videos in Belgium, "Videos-es-ES" for Spanish language videos). This allows trainers to easily identify the language and region for videos specific to their locale.

If that Training folder's region was changed to Australia, Sydney, all of the subfolders ("Videos-en-AU","Videos-fr-BE","Videos-fr-FR" and "Videos-es-ES" for our example) are now also stored in the Australia, Sydney region. The next task is to change the geographic storage region of the remaining five video folders to their respective regions.

"Videos-en-AU" is already set to Australia, Sydney, because the parent folder "Videos" is set to Australia, Sydney. France and Germany share a long border, so EU - Germany, Frankfurt would be the logical choice for the "Videos-fr-FR" folder. Similarly, we could assign the "Videos-fr-BE" and "Videos-sp-ES" to EU - Germany, Frankfurt. Finally, we'd set the "Videos-en-UK" folder to the UK, London region.

A simple design like this with some minor configuration changes like this could noticeably enhance performance and reduce costs, even when your users are widely scattered geographically.

The Global acceleration features configuration option affects the file transfer routes between your users and your selected storage region. Files.com recommends letting us connect users to their closest server. This feature attempts to optimize the network connection between users and File.com storage.

For example, if your storage is in Europe, and your users are in Singapore, then the users will connect to our Singapore region which will then forward those connections to Europe over our accelerated network.

To maintain performance, we strongly recommend not using a Custom Domain as it will circumvent these acceleration features. If you must use a Custom Domain then make sure that your Custom Domain is implemented in the same region as your storage.

If you have compliance conditions that require your data never be stored (even temporarily) outside of the closest server to your selected storage region, site administrators should change this option to use your specified file storage geographic region only. In that case, you must connect using your custom subdomain, or custom domain if you have one configured, instead of app.files.com (example: mySitename.files.com or files.MyCompany.com). See the Custom Domain article for additional information.

To locate the setting, type "Global acceleration features" in the search bar at the top of every page and select the matching result. The setting can only be accessed by a site administrator.

Files.com provides a number of configuration options that allow you to control where your data is stored, where data can be accessed from, and where data will be routed through during transmission. This allows you to configure Files.com to use a single region in order to meet data sovereignty and geographical data boundary requirements.

There are four steps to ensure that your data is stored, accessed, and transmitted in a specific region. First, configure your top-level Root Folder to be stored in your desired region. This region will be inherited by all other folders, unless specifically overridden. Overridden folders that are configured for other data regions will use those regions for data storage only. Data transmission and data access for overridden folders will still be routed through the region specified for the Root Folder (provided the following configurations are also applied).

With your top-level root folder set to your desired region, configure the Remote Servers settings to restrict the routing of data to your desired region. To ensure that traffic from your end-users will be restricted to the correct region, configure the Global Acceleration setting to use your desired region. Prevent any users from connecting from other regions by configuring the Allowed Countries to specify only countries within your region.

Due to the need to support co-editing, the Files.com Editor environment uses temporary storage and processing in our USA region regardless of the region in which files are stored permanently. This temporary storage is managed automatically by Files.com and files are not retained in the USA beyond an editing session.

In order to be comprehensively restricted to a region, you should ensure that all other connected remote systems also reside in your chosen region. This includes identity providers, remote storage solutions, notification services, any connected iPaaS.

Depending on your region, the ability to restrict the above third party services may, or may not, be available to you. Please contact your third-party vendors to find out what regional configurations are available to you.

Each new Files.com site comes pre-configured with default settings. You may need to change some or all of these settings. The top-level Root Folder is stored in the USA. Connections with Remote Servers will route data via the USA. Connections with Remote Servers will route data via the USA. Global Acceleration is enabled to route users' requests to the servers closest to them. Allowed Countries is un-configured, allowing all countries to connect.

Implementing a Custom Domain, along with the associated Dedicated IPs, can have performance implications on the transmission speed of international file transfers.

The global acceleration features of regional storage are circumvented when a Custom Domain is implemented in a different region than your storage region, meaning that file transfer durations will take longer than usual. To maintain performance, we strongly recommend that your Custom Domain is implemented in the same region as your storage.

For global customers, note that all global users will be routed through the region of your Custom Domain and its Dedicated IPs. For example, if your Custom Domain is in Europe then all file transfers will be routed through Europe on their way to their final destination. This also applies to transfers to your Regional Storage. For example, if your Custom Domain is in Europe, and you have a folder that is stored in Singapore, then all file transfers to the Singapore folder will travel through Europe, even if they originate from Singapore itself.

A Custom Domain should not be used in conjunction with regional storage if global transmission performance is your priority.